BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
69.63.0.0/19
Announced exactly
- 69.63.0.0/19AS5056Aureon Network ServicesRPKI Not found69.63.0.0
- Registry
- ARIN · United States · Jul 18, 2003
- Delegated block
- 69.63.0.0 – 69.63.31.255
Covering routes
No less-specific route covers it.
More-specific routes
- 69.63.0.0/24AS396878Spencer Municipal UtilitiesRPKI Not found69.63.0.0
- 69.63.3.0/24AS30325South Slope Cooperative Telephone CompanyRPKI Not found69.63.3.0
- 69.63.4.0/23AS30325South Slope Cooperative Telephone CompanyRPKI Not found69.63.4.0
- 69.63.4.0/24AS30325South Slope Cooperative Telephone CompanyRPKI Not found69.63.4.0
- 69.63.5.0/24AS30325South Slope Cooperative Telephone CompanyRPKI Not found69.63.5.0
- 69.63.6.0/23AS5056Aureon Network ServicesRPKI Not found69.63.6.0
- 69.63.10.0/23AS5056Aureon Network ServicesRPKI Not found69.63.10.0
- 69.63.12.0/24AS20273WCCTARPKI Not found69.63.12.0
- 69.63.13.0/24AS62825Walnut CommunicationsRPKI Not found69.63.13.0
- 69.63.14.0/23AS17137Hawkeye Switching LLC.RPKI Not found69.63.14.0
- 69.63.16.0/24AS30325South Slope Cooperative Telephone CompanyRPKI Not found69.63.16.0
- 69.63.17.0/24AS54374WMTelRPKI Not found69.63.17.0
- 69.63.18.0/23AS399559Alpine Communications L.C.RPKI Not found69.63.18.0
- 69.63.20.0/23AS5056Aureon Network ServicesRPKI Not found69.63.20.0
- 69.63.23.0/24AS396443Western Iowa NetworksRPKI Valid69.63.23.0
- 69.63.24.0/24AS13356Panora TelcoRPKI Not found69.63.24.0
- 69.63.25.0/24AS397475F&B Communications, Inc.RPKI Not found69.63.25.0
- 69.63.26.0/24AS5056Aureon Network ServicesRPKI Not found69.63.26.0
- 69.63.31.0/24AS62825Walnut CommunicationsRPKI Not found69.63.31.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.