BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
216.119.0.0/18
Announced exactly
- 216.119.0.0/18AS6461Zayo BandwidthRPKI Valid216.119.0.0
- Registry
- ARIN · United States · Jul 19, 2006
- Delegated block
- 216.119.0.0 – 216.119.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 216.119.18.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.18.0
- 216.119.19.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.19.0
- 216.119.20.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.20.0
- 216.119.21.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.21.0
- 216.119.22.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.22.0
- 216.119.27.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.27.0
- 216.119.28.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.28.0
- 216.119.29.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.29.0
- 216.119.32.0/24AS53294Fox News ChannelRPKI Valid216.119.32.0
- 216.119.34.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.34.0
- 216.119.35.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.35.0
- 216.119.36.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.36.0
- 216.119.37.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.37.0
- 216.119.38.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.38.0
- 216.119.40.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.40.0
- 216.119.41.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.41.0
- 216.119.48.0/24AS62844The Seimitsu CorporationRPKI Valid216.119.48.0
- 216.119.49.0/24AS62844The Seimitsu CorporationRPKI Valid216.119.49.0
- 216.119.54.0/24AS62844The Seimitsu CorporationRPKI Valid216.119.54.0
- 216.119.55.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.55.0
- 216.119.58.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.58.0
- 216.119.59.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.59.0
- 216.119.60.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.60.0
- 216.119.61.0/24AS19955Pineland Telephone Cooperative, Inc.RPKI Valid216.119.61.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.