BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
206.136.0.0/14
Announced exactly
- 206.136.0.0/14AS701Verizon BusinessRPKI Not found206.136.0.0
- Registry
- ARIN · United States · Sep 28, 1995
- Delegated block
- 206.136.0.0 – 206.139.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 206.136.84.0/24AS11086Pitney Bowes IncorporatedRPKI Not found206.136.84.0
- 206.136.86.0/24AS11086Pitney Bowes IncorporatedRPKI Not found206.136.86.0
- 206.136.87.0/24AS11086Pitney Bowes IncorporatedRPKI Not found206.136.87.0
- 206.136.114.0/24AS16224Verizon UK LimitedRPKI Valid206.136.114.0
- 206.136.115.0/24AS16224Verizon UK LimitedRPKI Valid206.136.115.0
- 206.136.116.0/24AS16224Verizon UK LimitedRPKI Valid206.136.116.0
- 206.136.117.0/24AS16224Verizon UK LimitedRPKI Valid206.136.117.0
- 206.136.119.0/24AS16224Verizon UK LimitedRPKI Valid206.136.119.0
- 206.136.121.0/24AS16224Verizon UK LimitedRPKI Valid206.136.121.0
- 206.136.125.0/24AS16224Verizon UK LimitedRPKI Valid206.136.125.0
- 206.136.127.0/24AS16224Verizon UK LimitedRPKI Valid206.136.127.0
- 206.136.172.0/24AS16224Verizon UK LimitedRPKI Valid206.136.172.0
- 206.136.175.0/24AS16224Verizon UK LimitedRPKI Valid206.136.175.0
- 206.136.227.0/24AS36336Natixis Advisors, LLCRPKI Not found206.136.227.0
- 206.137.113.0/24AS16937Penske Vehicle Services, Inc.RPKI Not found206.137.113.0
- 206.137.144.0/20AS394453Ensono LPRPKI Not found206.137.144.0
- 206.137.235.0/24AS33354PORT AUTHORITY OF New York and New JerseyRPKI Not found206.137.235.0
- 206.138.16.0/20AS15146Cable BahamasRPKI Not found206.138.16.0
- 206.138.168.0/21AS8075Microsoft CorporationRPKI Not found206.138.168.0
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.