BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
209.116.0.0/14
Announced exactly
- 209.116.0.0/14AS2828Verizon BusinessRPKI Not found209.116.0.0
- Registry
- ARIN · United States · Jan 2, 2001
- Delegated block
- 209.116.0.0 – 209.119.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 209.116.0.0/21AS10355Digital Service ConsultantsRPKI Not found209.116.0.0
- 209.116.149.0/24AS17035NBCUniversalRPKI Not found209.116.149.0
- 209.116.152.0/24AS701Verizon BusinessRPKI Valid209.116.152.0
- 209.117.12.0/23AS3257GTT-BACKBONE GTTRPKI Not found209.117.12.0
- 209.117.63.0/24AS701Verizon BusinessRPKI Not found209.117.63.0
- 209.117.66.0/23AS393827BJS WHOLESALE CLUBRPKI Not found209.117.66.0
- 209.117.232.0/22AS3257GTT-BACKBONE GTTRPKI Not found209.117.232.0
- 209.117.238.0/24AS3257GTT-BACKBONE GTTRPKI Not found209.117.238.0
- 209.117.241.0/24AS53675Hancock Whitney BankRPKI Not found209.117.241.0
- 209.118.39.0/24AS701Verizon BusinessRPKI Valid209.118.39.0
- 209.118.61.0/24AS394389Gaming and Leisure Properties IncRPKI Not found209.118.61.0
- 209.118.83.0/24AS17119Kampung CommunicationsRPKI Valid209.118.83.0
- 209.118.211.0/24AS26669Headland CommunicationsRPKI Not found209.118.211.0
- 209.118.251.0/24AS701Verizon BusinessRPKI Not found209.118.251.0
- 209.119.1.0/24AS701Verizon BusinessRPKI Valid209.119.1.0
- 209.119.20.0/24AS701Verizon BusinessRPKI Valid209.119.20.0
- 209.119.33.0/24AS36776Five9 Inc.RPKI Valid209.119.33.0
- 209.119.42.0/24AS36776Five9 Inc.RPKI Valid209.119.42.0
- 209.119.51.0/24AS22530Dialink CorporationRPKI Not found209.119.51.0
- 209.119.77.0/24AS30202Level IVRPKI Not found209.119.77.0
- 209.119.78.0/24AS30202Level IVRPKI Not found209.119.78.0
- 209.119.79.0/24AS30202Level IVRPKI Not found209.119.79.0
- 209.119.80.0/23AS41264GOOGLE-IT-RO-ISPRPKI Not found209.119.80.0
- 209.119.98.0/24AS26669Headland CommunicationsRPKI Not found209.119.98.0
- 209.119.120.0/22AS46746NTT Managed Services Americas, LLCRPKI Not found209.119.120.0
- 209.119.120.0/24AS46746NTT Managed Services Americas, LLCRPKI Not found209.119.120.0
- 209.119.121.0/24AS46746NTT Managed Services Americas, LLCRPKI Not found209.119.121.0
- 209.119.140.0/24AS31890Rocket Limited PartnershipRPKI Not found209.119.140.0
- 209.119.148.0/22AS3257GTT-BACKBONE GTTRPKI Not found209.119.148.0
- 209.119.151.0/24AS3257GTT-BACKBONE GTTRPKI Not found209.119.151.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.