BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
82.138.64.0/18
Announced exactly
- 82.138.64.0/18AS174Cogent Communications, LLCRPKI Not found82.138.64.0
- Registry
- RIPE NCC · United States · Jul 17, 2003
- Delegated block
- 82.138.64.0 – 82.138.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 82.138.64.0/23AS41765IPGARDE-ASRPKI Valid82.138.64.0
- 82.138.66.0/23AS198545FLEXNETWORK-ASRPKI Not found82.138.66.0
- 82.138.68.0/23AS198545FLEXNETWORK-ASRPKI Not found82.138.68.0
- 82.138.75.0/24AS47600RUBIXDATACENTERRPKI Not found82.138.75.0
- 82.138.76.0/23AS198545FLEXNETWORK-ASRPKI Not found82.138.76.0
- 82.138.80.0/22AS198545FLEXNETWORK-ASRPKI Not found82.138.80.0
- 82.138.84.0/23AS198545FLEXNETWORK-ASRPKI Not found82.138.84.0
- 82.138.86.0/24AS47600RUBIXDATACENTERRPKI Valid82.138.86.0
- 82.138.88.0/22AS198545FLEXNETWORK-ASRPKI Not found82.138.88.0
- 82.138.92.0/23AS198545FLEXNETWORK-ASRPKI Not found82.138.92.0
- 82.138.96.0/22AS60641HEXATELRPKI Not found82.138.96.0
- 82.138.104.0/22AS198545FLEXNETWORK-ASRPKI Not found82.138.104.0
- 82.138.108.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.108.0
- 82.138.109.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.109.0
- 82.138.110.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.110.0
- 82.138.111.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.111.0
- 82.138.112.0/22AS198545FLEXNETWORK-ASRPKI Not found82.138.112.0
- 82.138.116.0/22AS198545FLEXNETWORK-ASRPKI Not found82.138.116.0
- 82.138.120.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.120.0
- 82.138.121.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.121.0
- 82.138.122.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.122.0
- 82.138.123.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.123.0
- 82.138.124.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.124.0
- 82.138.125.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.125.0
- 82.138.127.0/24AS206119VEGANET-TELEKOMRPKI Valid82.138.127.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.