BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
70.33.0.0/18
Announced exactly
- 70.33.0.0/18AS8057Vision Net, Inc.RPKI Not found70.33.0.0
- Registry
- ARIN · United States · Jan 7, 2009
- Delegated block
- 70.33.0.0 – 70.33.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 70.33.0.0/24AS40933Triangle CommunicationsRPKI Valid70.33.0.0
- 70.33.5.0/24AS33339NemontRPKI Not found70.33.5.0
- 70.33.6.0/24AS40933Triangle CommunicationsRPKI Valid70.33.6.0
- 70.33.7.0/24AS33339NemontRPKI Not found70.33.7.0
- 70.33.8.0/22AS33339NemontRPKI Not found70.33.8.0
- 70.33.11.0/24AS33339NemontRPKI Not found70.33.11.0
- 70.33.12.0/22AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found70.33.12.0
- 70.33.16.0/22AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found70.33.16.0
- 70.33.20.0/24AS40933Triangle CommunicationsRPKI Valid70.33.20.0
- 70.33.21.0/24AS8057Vision Net, Inc.RPKI Not found70.33.21.0
- 70.33.22.0/23AS40933Triangle CommunicationsRPKI Valid70.33.22.0
- 70.33.22.0/24AS40933Triangle CommunicationsRPKI Valid70.33.22.0
- 70.33.23.0/24AS40933Triangle CommunicationsRPKI Valid70.33.23.0
- 70.33.24.0/24AS33339NemontRPKI Not found70.33.24.0
- 70.33.25.0/24AS40933Triangle CommunicationsRPKI Valid70.33.25.0
- 70.33.26.0/24AS40933Triangle CommunicationsRPKI Valid70.33.26.0
- 70.33.27.0/24AS399079Linctel Communications Inc.RPKI Not found70.33.27.0
- 70.33.28.0/24AS8057Vision Net, Inc.RPKI Not found70.33.28.0
- 70.33.29.0/24AS33339NemontRPKI Not found70.33.29.0
- 70.33.30.0/23AS40933Triangle CommunicationsRPKI Valid70.33.30.0
- 70.33.30.0/24AS40933Triangle CommunicationsRPKI Valid70.33.30.0
- 70.33.31.0/24AS40933Triangle CommunicationsRPKI Valid70.33.31.0
- 70.33.32.0/23AS40933Triangle CommunicationsRPKI Valid70.33.32.0
- 70.33.32.0/24AS40933Triangle CommunicationsRPKI Valid70.33.32.0
- 70.33.33.0/24AS40933Triangle CommunicationsRPKI Valid70.33.33.0
- 70.33.34.0/24AS40933Triangle CommunicationsRPKI Valid70.33.34.0
- 70.33.35.0/24AS33339NemontRPKI Not found70.33.35.0
- 70.33.36.0/23AS33339NemontRPKI Not found70.33.36.0
- 70.33.36.0/24AS33339NemontRPKI Not found70.33.36.0
- 70.33.37.0/24AS33339NemontRPKI Not found70.33.37.0
- 70.33.38.0/24AS399079Linctel Communications Inc.RPKI Not found70.33.38.0
- 70.33.39.0/24AS399079Linctel Communications Inc.RPKI Not found70.33.39.0
- 70.33.42.0/23AS33339NemontRPKI Not found70.33.42.0
- 70.33.42.0/24AS33339NemontRPKI Not found70.33.42.0
- 70.33.44.0/22AS33339NemontRPKI Not found70.33.44.0
- 70.33.46.0/24AS33339NemontRPKI Not found70.33.46.0
- 70.33.47.0/24AS33339NemontRPKI Not found70.33.47.0
- 70.33.48.0/23AS33339NemontRPKI Not found70.33.48.0
- 70.33.49.0/24AS33339NemontRPKI Not found70.33.49.0
- 70.33.50.0/24AS33339NemontRPKI Not found70.33.50.0
- 70.33.52.0/23AS40933Triangle CommunicationsRPKI Valid70.33.52.0
- 70.33.52.0/24AS40933Triangle CommunicationsRPKI Valid70.33.52.0
- 70.33.53.0/24AS40933Triangle CommunicationsRPKI Valid70.33.53.0
- 70.33.54.0/24AS40933Triangle CommunicationsRPKI Valid70.33.54.0
- 70.33.55.0/24AS8057Vision Net, Inc.RPKI Not found70.33.55.0
- 70.33.57.0/24AS8057Vision Net, Inc.RPKI Not found70.33.57.0
- 70.33.59.0/24AS40933Triangle CommunicationsRPKI Valid70.33.59.0
- 70.33.60.0/24AS40933Triangle CommunicationsRPKI Valid70.33.60.0
- 70.33.61.0/24AS33339NemontRPKI Not found70.33.61.0
- 70.33.62.0/24AS40933Triangle CommunicationsRPKI Valid70.33.62.0
- 70.33.63.0/24AS33339NemontRPKI Not found70.33.63.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.