BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
206.169.0.0/16
Announced exactly
- 206.169.0.0/16AS3549Level 3 Parent, LLCRPKI Not found206.169.0.0
- Registry
- ARIN · United States · Oct 19, 1995
- Delegated block
- 206.169.0.0 – 206.169.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 206.169.6.0/24AS40075Radiology LTDRPKI Not found206.169.6.0
- 206.169.38.0/23AS19881Valley Telecommunications CompanyRPKI Not found206.169.38.0
- 206.169.46.0/23AS19881Valley Telecommunications CompanyRPKI Not found206.169.46.0
- 206.169.63.0/24AS398929Loma Linda Connected Community ProgramRPKI Not found206.169.63.0
- 206.169.64.0/24AS19881Valley Telecommunications CompanyRPKI Not found206.169.64.0
- 206.169.67.0/24AS203Level 3 Parent, LLCRPKI Not found206.169.67.0
- 206.169.74.0/24AS22702RingSquaredRPKI Not found206.169.74.0
- 206.169.77.0/24AS398929Loma Linda Connected Community ProgramRPKI Not found206.169.77.0
- 206.169.82.0/24AS3356Level 3 Parent, LLCRPKI Not found206.169.82.0
- 206.169.89.0/24AS19881Valley Telecommunications CompanyRPKI Not found206.169.89.0
- 206.169.101.0/24AS3356Level 3 Parent, LLCRPKI Not found206.169.101.0
- 206.169.114.0/24AS393510St Francis Healthcare System of HawaiiRPKI Not found206.169.114.0
- 206.169.120.0/23AS398929Loma Linda Connected Community ProgramRPKI Not found206.169.120.0
- 206.169.133.0/24AS55092UNASSIGNEDRPKI Not found206.169.133.0
- 206.169.134.0/23AS3356Level 3 Parent, LLCRPKI Not found206.169.134.0
- 206.169.140.0/22AS25649AYERA TECHNOLOGIES, INC.RPKI Not found206.169.140.0
- 206.169.150.0/23AS3356Level 3 Parent, LLCRPKI Not found206.169.150.0
- 206.169.152.0/24AS395396Alert Alarm HawaiiRPKI Not found206.169.152.0
- 206.169.160.0/24AS18669Bal Seal Engineering Co. Inc.RPKI Not found206.169.160.0
- 206.169.162.0/23AS25649AYERA TECHNOLOGIES, INC.RPKI Not found206.169.162.0
- 206.169.171.0/24AS3356Level 3 Parent, LLCRPKI Not found206.169.171.0
- 206.169.190.0/24AS3356Level 3 Parent, LLCRPKI Not found206.169.190.0
- 206.169.206.0/24AS19881Valley Telecommunications CompanyRPKI Not found206.169.206.0
- 206.169.211.0/24AS29824Appfolio, Inc.RPKI Not found206.169.211.0
- 206.169.212.0/24AS62621UNASSIGNEDRPKI Not found206.169.212.0
- 206.169.217.0/24AS26421Ponderosa CablevisionRPKI Valid206.169.217.0
- 206.169.218.0/23AS26421Ponderosa CablevisionRPKI Valid206.169.218.0
- 206.169.233.0/24AS20168Precor IncorporatedRPKI Not found206.169.233.0
- 206.169.242.0/24AS10753Level 3 Parent, LLCRPKI Not found206.169.242.0
- 206.169.252.0/23AS26729Midwest Internet, Inc.RPKI Not found206.169.252.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.