BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
209.52.0.0/15
Announced exactly
- 209.52.0.0/15AS852TELUS Communications Inc.RPKI Valid209.52.0.0
- Registry
- ARIN · Canada · Jan 13, 2000
- Delegated block
- 209.52.0.0 – 209.53.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 209.52.0.0/19AS852TELUS Communications Inc.RPKI Valid209.52.0.0
- 209.52.38.0/24AS40934Fortinet Inc.RPKI Valid209.52.38.0
- 209.52.40.0/22AS852TELUS Communications Inc.RPKI Valid209.52.40.0
- 209.52.104.0/21AS852TELUS Communications Inc.RPKI Valid209.52.104.0
- 209.52.117.0/24AS40934Fortinet Inc.RPKI Valid209.52.117.0
- 209.52.130.0/24AS40934Fortinet Inc.RPKI Valid209.52.130.0
- 209.52.182.0/23AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI Valid209.52.182.0
- 209.52.184.0/23AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI Valid209.52.184.0
- 209.52.184.0/24AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI Valid209.52.184.0
- 209.52.228.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.52.228.0
- 209.52.236.0/22AS54359TELUS Communications Inc.RPKI Valid209.52.236.0
- 209.53.107.0/24AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI Valid209.53.107.0
- 209.53.108.0/23AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI Valid209.53.108.0
- 209.53.126.0/24AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI Valid209.53.126.0
- 209.53.169.0/24AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI Valid209.53.169.0
- 209.53.170.0/23AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI Valid209.53.170.0
- 209.53.172.0/23AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI Valid209.53.172.0
- 209.53.174.0/24AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPRPKI Valid209.53.174.0
- 209.53.180.0/23AS852TELUS Communications Inc.RPKI Valid209.53.180.0
- 209.53.193.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.193.0
- 209.53.194.0/23AS25668Cipherkey Exchange Corp.RPKI Valid209.53.194.0
- 209.53.194.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.194.0
- 209.53.195.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.195.0
- 209.53.196.0/22AS25668Cipherkey Exchange Corp.RPKI Valid209.53.196.0
- 209.53.196.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.196.0
- 209.53.197.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.197.0
- 209.53.198.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.198.0
- 209.53.199.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.199.0
- 209.53.200.0/21AS25668Cipherkey Exchange Corp.RPKI Valid209.53.200.0
- 209.53.208.0/22AS25668Cipherkey Exchange Corp.RPKI Valid209.53.208.0
- 209.53.208.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.208.0
- 209.53.209.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.209.0
- 209.53.210.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.210.0
- 209.53.211.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.211.0
- 209.53.212.0/23AS25668Cipherkey Exchange Corp.RPKI Valid209.53.212.0
- 209.53.212.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.212.0
- 209.53.213.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.213.0
- 209.53.214.0/24AS25668Cipherkey Exchange Corp.RPKI Valid209.53.214.0
- 209.53.232.0/24AS36000Northern Health AuthorityRPKI Valid209.53.232.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.