BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2605:1900::/32
Announced exactly
- 2605:1900::/32AS12208TruVista CommunicationsRPKI Not found2605:1900::
- Registry
- ARIN · United States · Jun 6, 2011
- Delegated block
- 2605:1900:: – 2605:1900:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2605:1900:1::/48AS12208TruVista CommunicationsRPKI Not found2605:1900:1::
- 2605:1900:8040::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8040::
- 2605:1900:8080::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8080::
- 2605:1900:80c0::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:80c0::
- 2605:1900:8100::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8100::
- 2605:1900:8140::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8140::
- 2605:1900:8180::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8180::
- 2605:1900:81c0::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:81c0::
- 2605:1900:8200::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8200::
- 2605:1900:8240::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8240::
- 2605:1900:8280::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8280::
- 2605:1900:82c0::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:82c0::
- 2605:1900:8340::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8340::
- 2605:1900:83c0::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:83c0::
- 2605:1900:8400::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8400::
- 2605:1900:8440::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8440::
- 2605:1900:8480::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:8480::
- 2605:1900:84c0::/42AS12208TruVista CommunicationsRPKI Not found2605:1900:84c0::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.