BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
142.217.0.0/16
Announced exactly
- 142.217.0.0/16AS577Bell CanadaRPKI Not found142.217.0.0
- Registry
- ARIN · Canada · Oct 28, 1992
- Delegated block
- 142.217.0.0 – 142.217.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 142.217.0.0/18AS35911TelebecRPKI Not found142.217.0.0
- 142.217.64.0/19AS35911TelebecRPKI Not found142.217.64.0
- 142.217.96.0/21AS35911TelebecRPKI Not found142.217.96.0
- 142.217.97.0/24AS35911TelebecRPKI Not found142.217.97.0
- 142.217.104.0/22AS35911TelebecRPKI Not found142.217.104.0
- 142.217.108.0/24AS35911TelebecRPKI Not found142.217.108.0
- 142.217.109.0/24AS35911TelebecRPKI Not found142.217.109.0
- 142.217.110.0/23AS35911TelebecRPKI Not found142.217.110.0
- 142.217.112.0/22AS35911TelebecRPKI Not found142.217.112.0
- 142.217.116.0/23AS35911TelebecRPKI Not found142.217.116.0
- 142.217.118.0/23AS35911TelebecRPKI Not found142.217.118.0
- 142.217.120.0/24AS35911TelebecRPKI Not found142.217.120.0
- 142.217.121.0/24AS35911TelebecRPKI Not found142.217.121.0
- 142.217.122.0/23AS35911TelebecRPKI Not found142.217.122.0
- 142.217.124.0/22AS35911TelebecRPKI Not found142.217.124.0
- 142.217.128.0/22AS35911TelebecRPKI Not found142.217.128.0
- 142.217.132.0/23AS35911TelebecRPKI Not found142.217.132.0
- 142.217.134.0/24AS35911TelebecRPKI Not found142.217.134.0
- 142.217.135.0/24AS35911TelebecRPKI Not found142.217.135.0
- 142.217.136.0/22AS35911TelebecRPKI Not found142.217.136.0
- 142.217.140.0/22AS35911TelebecRPKI Not found142.217.140.0
- 142.217.144.0/24AS35911TelebecRPKI Not found142.217.144.0
- 142.217.145.0/24AS35911TelebecRPKI Not found142.217.145.0
- 142.217.152.0/21AS35911TelebecRPKI Not found142.217.152.0
- 142.217.160.0/21AS35911TelebecRPKI Not found142.217.160.0
- 142.217.168.0/21AS35911TelebecRPKI Not found142.217.168.0
- 142.217.176.0/22AS35911TelebecRPKI Not found142.217.176.0
- 142.217.180.0/23AS35911TelebecRPKI Not found142.217.180.0
- 142.217.182.0/24AS35911TelebecRPKI Not found142.217.182.0
- 142.217.183.0/24AS35911TelebecRPKI Not found142.217.183.0
- 142.217.184.0/23AS35911TelebecRPKI Not found142.217.184.0
- 142.217.186.0/23AS35911TelebecRPKI Not found142.217.186.0
- 142.217.188.0/22AS35911TelebecRPKI Not found142.217.188.0
- 142.217.192.0/22AS35911TelebecRPKI Not found142.217.192.0
- 142.217.196.0/24AS35911TelebecRPKI Not found142.217.196.0
- 142.217.197.0/24AS35911TelebecRPKI Not found142.217.197.0
- 142.217.198.0/23AS35911TelebecRPKI Not found142.217.198.0
- 142.217.200.0/21AS35911TelebecRPKI Not found142.217.200.0
- 142.217.208.0/20AS35911TelebecRPKI Not found142.217.208.0
- 142.217.224.0/21AS35911TelebecRPKI Not found142.217.224.0
- 142.217.232.0/22AS35911TelebecRPKI Not found142.217.232.0
- 142.217.236.0/23AS35911TelebecRPKI Not found142.217.236.0
- 142.217.238.0/24AS35911TelebecRPKI Not found142.217.238.0
- 142.217.239.0/24AS35911TelebecRPKI Not found142.217.239.0
- 142.217.240.0/20AS35911TelebecRPKI Not found142.217.240.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.