BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2605:f500::/32
Announced exactly
- 2605:f500::/32AS1828Unitas GlobalRPKI Valid2605:f500::
- Registry
- ARIN · United States · Sep 15, 2011
- Delegated block
- 2605:f500:: – 2605:f500:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2605:f500:101::/48AS1828Unitas GlobalRPKI Invalid2605:f500:101::
- 2605:f500:102::/48AS1828Unitas GlobalRPKI Invalid2605:f500:102::
- 2605:f500:103::/48AS1828Unitas GlobalRPKI Invalid2605:f500:103::
- 2605:f500:104::/48AS1828Unitas GlobalRPKI Invalid2605:f500:104::
- 2605:f500:105::/48AS1828Unitas GlobalRPKI Invalid2605:f500:105::
- 2605:f500:106::/48AS1828Unitas GlobalRPKI Valid2605:f500:106::
- 2605:f500:107::/48AS1828Unitas GlobalRPKI Invalid2605:f500:107::
- 2605:f500:108::/48AS1828Unitas GlobalRPKI Invalid2605:f500:108::
- 2605:f500:109::/48AS1828Unitas GlobalRPKI Invalid2605:f500:109::
- 2605:f500:110::/48AS1828Unitas GlobalRPKI Invalid2605:f500:110::
- 2605:f500:111::/48AS1828Unitas GlobalRPKI Invalid2605:f500:111::
- 2605:f500:112::/48AS1828Unitas GlobalRPKI Invalid2605:f500:112::
- 2605:f500:113::/48AS1828Unitas GlobalRPKI Invalid2605:f500:113::
- 2605:f500:118::/48AS1828Unitas GlobalRPKI Invalid2605:f500:118::
- 2605:f500:119::/48AS1828Unitas GlobalRPKI Invalid2605:f500:119::
- 2605:f500:120::/48AS1828Unitas GlobalRPKI Invalid2605:f500:120::
- 2605:f500:121::/48AS1828Unitas GlobalRPKI Valid2605:f500:121::
- 2605:f500:122::/48AS1828Unitas GlobalRPKI Invalid2605:f500:122::
- 2605:f500:123::/48AS1828Unitas GlobalRPKI Invalid2605:f500:123::
- 2605:f500:301::/48AS1828Unitas GlobalRPKI Invalid2605:f500:301::
- 2605:f500:303::/48AS1828Unitas GlobalRPKI Invalid2605:f500:303::
- 2605:f500:305::/48AS1828Unitas GlobalRPKI Invalid2605:f500:305::
- 2605:f500:306::/48AS1828Unitas GlobalRPKI Invalid2605:f500:306::
- 2605:f500:401::/48AS1828Unitas GlobalRPKI Invalid2605:f500:401::
- 2605:f500:402::/48AS1828Unitas GlobalRPKI Invalid2605:f500:402::
- 2605:f500:8106::/48AS1828Unitas GlobalRPKI Valid2605:f500:8106::
- 2605:f500:8110::/48AS1828Unitas GlobalRPKI Invalid2605:f500:8110::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.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.