BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
76.75.0.0/18
Announced exactly
- 76.75.0.0/18AS8057Vision Net, Inc.RPKI Not found76.75.0.0
- Registry
- ARIN · United States · Apr 19, 2007
- Delegated block
- 76.75.0.0 – 76.75.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 76.75.0.0/24AS33339NemontRPKI Not found76.75.0.0
- 76.75.1.0/24AS33339NemontRPKI Not found76.75.1.0
- 76.75.3.0/24AS8057Vision Net, Inc.RPKI Not found76.75.3.0
- 76.75.4.0/23AS40933Triangle CommunicationsRPKI Valid76.75.4.0
- 76.75.4.0/24AS40933Triangle CommunicationsRPKI Valid76.75.4.0
- 76.75.5.0/24AS40933Triangle CommunicationsRPKI Valid76.75.5.0
- 76.75.8.0/21AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found76.75.8.0
- 76.75.16.0/24AS33339NemontRPKI Not found76.75.16.0
- 76.75.17.0/24AS8057Vision Net, Inc.RPKI Not found76.75.17.0
- 76.75.18.0/24AS8057Vision Net, Inc.RPKI Not found76.75.18.0
- 76.75.19.0/24AS33339NemontRPKI Not found76.75.19.0
- 76.75.20.0/22AS33339NemontRPKI Not found76.75.20.0
- 76.75.20.0/23AS33339NemontRPKI Not found76.75.20.0
- 76.75.22.0/23AS33339NemontRPKI Not found76.75.22.0
- 76.75.24.0/23AS33339NemontRPKI Not found76.75.24.0
- 76.75.24.0/24AS33339NemontRPKI Not found76.75.24.0
- 76.75.25.0/24AS33339NemontRPKI Not found76.75.25.0
- 76.75.26.0/24AS402710NorthernRPKI Not found76.75.26.0
- 76.75.27.0/24AS40933Triangle CommunicationsRPKI Valid76.75.27.0
- 76.75.28.0/24AS40933Triangle CommunicationsRPKI Valid76.75.28.0
- 76.75.29.0/24AS8057Vision Net, Inc.RPKI Not found76.75.29.0
- 76.75.30.0/24AS33339NemontRPKI Not found76.75.30.0
- 76.75.32.0/24AS33339NemontRPKI Not found76.75.32.0
- 76.75.33.0/24AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found76.75.33.0
- 76.75.34.0/23AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found76.75.34.0
- 76.75.36.0/23AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found76.75.36.0
- 76.75.39.0/24AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found76.75.39.0
- 76.75.43.0/24AS33339NemontRPKI Not found76.75.43.0
- 76.75.44.0/24AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found76.75.44.0
- 76.75.45.0/24AS399079Linctel Communications Inc.RPKI Not found76.75.45.0
- 76.75.48.0/23AS33339NemontRPKI Not found76.75.48.0
- 76.75.49.0/24AS33339NemontRPKI Not found76.75.49.0
- 76.75.50.0/23AS40933Triangle CommunicationsRPKI Valid76.75.50.0
- 76.75.50.0/24AS40933Triangle CommunicationsRPKI Valid76.75.50.0
- 76.75.51.0/24AS40933Triangle CommunicationsRPKI Valid76.75.51.0
- 76.75.52.0/24AS33339NemontRPKI Not found76.75.52.0
- 76.75.53.0/24AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found76.75.53.0
- 76.75.54.0/24AS8057Vision Net, Inc.RPKI Not found76.75.54.0
- 76.75.55.0/24AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found76.75.55.0
- 76.75.57.0/24AS33339NemontRPKI Not found76.75.57.0
- 76.75.58.0/23AS196053 Rivers Telephone Cooperative, Inc.RPKI Not found76.75.58.0
- 76.75.61.0/24AS8057Vision Net, Inc.RPKI Not found76.75.61.0
- 76.75.62.0/24AS8057Vision Net, Inc.RPKI Not found76.75.62.0
- 76.75.63.0/24AS40933Triangle CommunicationsRPKI Valid76.75.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.