BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2803:6ce0::/32
Announced exactly
- 2803:6ce0::/32AS269909COMTEC S. A.RPKI Valid2803:6ce0::
- Registry
- LACNIC · Argentina · Jan 17, 2020
- Delegated block
- 2803:6ce0:: – 2803:6ce0:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2803:6ce0::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0::
- 2803:6ce0:1000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:1000::
- 2803:6ce0:2000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:2000::
- 2803:6ce0:2000::/44AS269909COMTEC S. A.RPKI Valid2803:6ce0:2000::
- 2803:6ce0:2010::/44AS269909COMTEC S. A.RPKI Valid2803:6ce0:2010::
- 2803:6ce0:3000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:3000::
- 2803:6ce0:4000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:4000::
- 2803:6ce0:5000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:5000::
- 2803:6ce0:6000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:6000::
- 2803:6ce0:7000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:7000::
- 2803:6ce0:8000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:8000::
- 2803:6ce0:9000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:9000::
- 2803:6ce0:a000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:a000::
- 2803:6ce0:b000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:b000::
- 2803:6ce0:c000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:c000::
- 2803:6ce0:d000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:d000::
- 2803:6ce0:e000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:e000::
- 2803:6ce0:f000::/36AS269909COMTEC S. A.RPKI Valid2803:6ce0:f000::
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.