BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2600:4000::/24
Announced exactly
- 2600:4000::/24AS701Verizon BusinessRPKI Not found2600:4000::
- Registry
- ARIN · United States · Mar 15, 2011
- Delegated block
- 2600:4000:: – 2600:40ff:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2600:4040:1000::/36AS701Verizon BusinessRPKI Valid2600:4040:1000::
- 2600:4040:2000::/36AS701Verizon BusinessRPKI Valid2600:4040:2000::
- 2600:4040:3000::/36AS701Verizon BusinessRPKI Valid2600:4040:3000::
- 2600:4040:4000::/36AS701Verizon BusinessRPKI Valid2600:4040:4000::
- 2600:4040:5000::/36AS701Verizon BusinessRPKI Valid2600:4040:5000::
- 2600:4040:6000::/36AS701Verizon BusinessRPKI Valid2600:4040:6000::
- 2600:4040:7000::/36AS701Verizon BusinessRPKI Valid2600:4040:7000::
- 2600:4040:9000::/36AS701Verizon BusinessRPKI Valid2600:4040:9000::
- 2600:4040:a000::/36AS701Verizon BusinessRPKI Valid2600:4040:a000::
- 2600:4040:b000::/36AS701Verizon BusinessRPKI Valid2600:4040:b000::
- 2600:4040:c000::/36AS701Verizon BusinessRPKI Valid2600:4040:c000::
- 2600:4040:d000::/36AS701Verizon BusinessRPKI Valid2600:4040:d000::
- 2600:4040:e000::/36AS701Verizon BusinessRPKI Valid2600:4040:e000::
- 2600:4040:f000::/36AS701Verizon BusinessRPKI Not found2600:4040:f000::
- 2600:4041::/36AS701Verizon BusinessRPKI Valid2600:4041::
- 2600:4041:2000::/36AS701Verizon BusinessRPKI Not found2600:4041:2000::
- 2600:4041:3000::/36AS701Verizon BusinessRPKI Not found2600:4041:3000::
- 2600:4041:4000::/36AS701Verizon BusinessRPKI Not found2600:4041:4000::
- 2600:4041:5000::/36AS701Verizon BusinessRPKI Not found2600:4041:5000::
- 2600:4041:6000::/36AS701Verizon BusinessRPKI Not found2600:4041:6000::
- 2600:4041:7000::/36AS701Verizon BusinessRPKI Not found2600:4041:7000::
- 2600:40c0::/44AS701Verizon BusinessRPKI Not found2600:40c0::
- 2600:40f0:e::/48AS701Verizon BusinessRPKI Valid2600:40f0:e::
- 2600:40f0:100::/44AS3369Verizon BusinessRPKI Not found2600:40f0:100::
- 2600:40f0:140::/44AS3369Verizon BusinessRPKI Not found2600:40f0:140::
- 2600:40f0:1621::/48AS7046Verizon BusinessRPKI Not found2600:40f0:1621::
- 2600:40f0:1630::/44AS7046Verizon BusinessRPKI Not found2600:40f0:1630::
- 2600:40f0:1650::/44AS7046Verizon BusinessRPKI Not found2600:40f0:1650::
- 2600:40f2::/32AS3371Verizon BusinessRPKI Not found2600:40f2::
- 2600:40f3::/32AS3372Verizon BusinessRPKI Not found2600:40f3::
- 2600:40fc:1013::/48AS14210Edgecast Inc.RPKI Not found2600:40fc:1013::
- 2600:40fc:1014::/48AS14210Edgecast Inc.RPKI Not found2600:40fc:1014::
- 2600:40fd::/48AS7046Verizon BusinessRPKI Not found2600:40fd::
- 2600:40fd:2::/48AS7046Verizon BusinessRPKI Not found2600:40fd:2::
- 2600:40ff:fc00::/48AS1339Verizon BusinessRPKI Not found2600:40ff:fc00::
- 2600:40ff:fc04::/48AS1321Verizon BusinessRPKI Not found2600:40ff:fc04::
- 2600:40ff:fc20::/48AS1321Verizon BusinessRPKI Not found2600:40ff:fc20::
- 2600:40ff:fc21::/48AS1321Verizon BusinessRPKI Not found2600:40ff:fc21::
- 2600:40ff:fc22::/48AS1321Verizon BusinessRPKI Not found2600:40ff:fc22::
- 2600:40ff:fc23::/48AS1321Verizon BusinessRPKI Not found2600:40ff:fc23::
- 2600:40ff:fc24::/48AS1321Verizon BusinessRPKI Not found2600:40ff:fc24::
- 2600:40ff:fcb0::/48AS1387Verizon BusinessRPKI Not found2600:40ff:fcb0::
- 2600:40ff:fcf9::/48AS7046Verizon BusinessRPKI Not found2600:40ff:fcf9::
- 2600:40ff:fcfc::/47AS7046Verizon BusinessRPKI Not found2600:40ff:fcfc::
- 2600:40ff:fcfc::/48AS1339Verizon BusinessRPKI Not found2600:40ff:fcfc::
- 2600:40ff:ff12::/48AS1321Verizon BusinessRPKI Not found2600:40ff:ff12::
- 2600:40ff:ff13::/48AS1321Verizon BusinessRPKI Not found2600:40ff:ff13::
- 2600:40ff:ff92::/48AS1321Verizon BusinessRPKI Not found2600:40ff:ff92::
- 2600:40ff:ff93::/48AS1321Verizon BusinessRPKI Not found2600:40ff:ff93::
- 2600:40ff:fff1::/48AS3371Verizon BusinessRPKI Not found2600:40ff:fff1::
- 2600:40ff:fffb::/48AS701Verizon BusinessRPKI Valid2600:40ff:fffb::
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.