BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
62.192.96.0/19
Announced exactly
- 62.192.96.0/19AS3257GTT Communications Inc.RPKI Not found62.192.96.0
- Registry
- RIPE NCC · United States · Sep 25, 2001
- Delegated block
- 62.192.96.0 – 62.192.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 62.192.96.0/23AS59711HZ Hosting LtdRPKI Valid62.192.96.0
- 62.192.98.0/23AS30058FDCservers.netRPKI Valid62.192.98.0
- 62.192.100.0/23AS3320Deutsche Telekom AGRPKI Valid62.192.100.0
- 62.192.102.0/23AS9009M247 Europe SRLRPKI Valid62.192.102.0
- 62.192.104.0/23AS30058FDCservers.netRPKI Valid62.192.104.0
- 62.192.106.0/23AS3320Deutsche Telekom AGRPKI Valid62.192.106.0
- 62.192.108.0/23AS35758Rachamim Aviel TwitoRPKI Valid62.192.108.0
- 62.192.110.0/24AS5065Bunny CommunicationsRPKI Valid62.192.110.0
- 62.192.113.0/24AS9009M247 Europe SRLRPKI Valid62.192.113.0
- 62.192.114.0/23AS9009M247 Europe SRLRPKI Valid62.192.114.0
- 62.192.116.0/23AS30058FDCservers.netRPKI Valid62.192.116.0
- 62.192.118.0/23AS30058FDCservers.netRPKI Valid62.192.118.0
- 62.192.120.0/23AS10753Level 3 Parent, LLCRPKI Valid62.192.120.0
- 62.192.122.0/23AS10753Level 3 Parent, LLCRPKI Valid62.192.122.0
- 62.192.124.0/23AS2856British Telecommunications LimitedRPKI Valid62.192.124.0
- 62.192.126.0/23AS9009M247 Europe SRLRPKI Valid62.192.126.0
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.