BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
216.231.32.0/19
Announced exactly
- 216.231.32.0/19AS3257GTT Communications Inc.RPKI Not found216.231.32.0
- Registry
- ARIN · United States · Jun 18, 1999
- Delegated block
- 216.231.32.0 – 216.231.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 216.231.33.0/24AS5065Bunny CommunicationsRPKI Valid216.231.33.0
- 216.231.34.0/24AS5065Bunny CommunicationsRPKI Valid216.231.34.0
- 216.231.35.0/24AS5065Bunny CommunicationsRPKI Valid216.231.35.0
- 216.231.36.0/24AS7346Springtide CommunicationsRPKI Valid216.231.36.0
- 216.231.37.0/24AS5065Bunny CommunicationsRPKI Valid216.231.37.0
- 216.231.38.0/24AS5065Bunny CommunicationsRPKI Valid216.231.38.0
- 216.231.39.0/24AS5065Bunny CommunicationsRPKI Valid216.231.39.0
- 216.231.40.0/24AS5065Bunny CommunicationsRPKI Valid216.231.40.0
- 216.231.41.0/24AS11696Fusion, LLCRPKI Not found216.231.41.0
- 216.231.42.0/24AS5065Bunny CommunicationsRPKI Valid216.231.42.0
- 216.231.43.0/24AS5065Bunny CommunicationsRPKI Valid216.231.43.0
- 216.231.44.0/24AS5065Bunny CommunicationsRPKI Valid216.231.44.0
- 216.231.45.0/24AS5065Bunny CommunicationsRPKI Valid216.231.45.0
- 216.231.46.0/24AS5065Bunny CommunicationsRPKI Valid216.231.46.0
- 216.231.48.0/24AS5065Bunny CommunicationsRPKI Valid216.231.48.0
- 216.231.49.0/24AS7346Springtide CommunicationsRPKI Valid216.231.49.0
- 216.231.50.0/24AS5065Bunny CommunicationsRPKI Valid216.231.50.0
- 216.231.51.0/24AS62610Zenlayer IncRPKI Valid216.231.51.0
- 216.231.52.0/24AS5065Bunny CommunicationsRPKI Valid216.231.52.0
- 216.231.53.0/24AS5065Bunny CommunicationsRPKI Valid216.231.53.0
- 216.231.54.0/24AS5065Bunny CommunicationsRPKI Valid216.231.54.0
- 216.231.55.0/24AS5065Bunny CommunicationsRPKI Valid216.231.55.0
- 216.231.56.0/24AS5065Bunny CommunicationsRPKI Valid216.231.56.0
- 216.231.57.0/24AS5065Bunny CommunicationsRPKI Valid216.231.57.0
- 216.231.58.0/24AS5065Bunny CommunicationsRPKI Valid216.231.58.0
- 216.231.59.0/24AS5065Bunny CommunicationsRPKI Valid216.231.59.0
- 216.231.60.0/24AS5065Bunny CommunicationsRPKI Valid216.231.60.0
- 216.231.61.0/24AS5065Bunny CommunicationsRPKI Valid216.231.61.0
- 216.231.62.0/24AS62610Zenlayer IncRPKI Valid216.231.62.0
- 216.231.63.0/24AS5065Bunny CommunicationsRPKI Valid216.231.63.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.