BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:e48::/32
Announced exactly
- 2001:e48::/32AS9583Sify LimitedRPKI Not found2001:e48::
- Registry
- APNIC · India · Feb 11, 2004
- Delegated block
- 2001:e48:: – 2001:e48:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:e48:11::/48AS9583Sify LimitedRPKI Valid2001:e48:11::
- 2001:e48:12::/48AS9583Sify LimitedRPKI Not found2001:e48:12::
- 2001:e48:22::/48AS9583Sify LimitedRPKI Valid2001:e48:22::
- 2001:e48:33::/48AS9583Sify LimitedRPKI Valid2001:e48:33::
- 2001:e48:40::/48AS9583Sify LimitedRPKI Valid2001:e48:40::
- 2001:e48:41::/48AS9583Sify LimitedRPKI Valid2001:e48:41::
- 2001:e48:44::/48AS9583Sify LimitedRPKI Valid2001:e48:44::
- 2001:e48:45::/48AS9583Sify LimitedRPKI Valid2001:e48:45::
- 2001:e48:46::/48AS9583Sify LimitedRPKI Valid2001:e48:46::
- 2001:e48:47::/48AS9583Sify LimitedRPKI Not found2001:e48:47::
- 2001:e48:62::/48AS9583Sify LimitedRPKI Not found2001:e48:62::
- 2001:e48:80::/48AS9583Sify LimitedRPKI Valid2001:e48:80::
- 2001:e48:81::/48AS9583Sify LimitedRPKI Not found2001:e48:81::
- 2001:e48:82::/48AS9583Sify LimitedRPKI Not found2001:e48:82::
- 2001:e48:111::/48AS9583Sify LimitedRPKI Not found2001:e48:111::
- 2001:e48:122::/48AS9583Sify LimitedRPKI Not found2001:e48:122::
- 2001:e48:144::/48AS9583Sify LimitedRPKI Not found2001:e48:144::
- 2001:e48:180::/48AS9583Sify LimitedRPKI Not found2001:e48:180::
- 2001:e48:222::/48AS9583Sify LimitedRPKI Not found2001:e48:222::
- 2001:e48:1122::/48AS9583Sify LimitedRPKI Not found2001:e48:1122::
- 2001:e48:1180::/48AS9583Sify LimitedRPKI Not found2001:e48:1180::
- 2001:e48:1222::/48AS9583Sify LimitedRPKI Not found2001:e48:1222::
- 2001:e48:2122::/48AS9583Sify LimitedRPKI Not found2001:e48:2122::
- 2001:e48:2144::/48AS9583Sify LimitedRPKI Not found2001:e48:2144::
- 2001:e48:2180::/48AS9583Sify LimitedRPKI Not found2001:e48:2180::
- 2001:e48:2200::/48AS9583Sify LimitedRPKI Valid2001:e48:2200::
- 2001:e48:2222::/48AS9583Sify LimitedRPKI Not found2001:e48:2222::
- 2001:e48:3122::/48AS9583Sify LimitedRPKI Not found2001:e48:3122::
- 2001:e48:3180::/48AS9583Sify LimitedRPKI Not found2001:e48:3180::
- 2001:e48:3300::/48AS9583Sify LimitedRPKI Valid2001:e48:3300::
- 2001:e48:4000::/48AS9583Sify LimitedRPKI Valid2001:e48:4000::
- 2001:e48:4400::/48AS9583Sify LimitedRPKI Valid2001:e48:4400::
- 2001:e48:8000::/48AS9583Sify LimitedRPKI Valid2001:e48:8000::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.0.0/14. This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Frequently asked questions
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.