BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
209.205.128.0/18
Announced exactly
- 209.205.128.0/18AS4314Vexus FiberRPKI Not found209.205.128.0
- Registry
- ARIN · United States · Jun 6, 2000
- Delegated block
- 209.205.128.0 – 209.205.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 209.205.129.0/24AS4314Vexus FiberRPKI Not found209.205.129.0
- 209.205.130.0/24AS4314Vexus FiberRPKI Not found209.205.130.0
- 209.205.131.0/24AS4314Vexus FiberRPKI Not found209.205.131.0
- 209.205.132.0/24AS4314Vexus FiberRPKI Not found209.205.132.0
- 209.205.133.0/24AS13693Vexus FiberRPKI Not found209.205.133.0
- 209.205.134.0/23AS13693Vexus FiberRPKI Not found209.205.134.0
- 209.205.136.0/24AS13693Vexus FiberRPKI Not found209.205.136.0
- 209.205.137.0/24AS13693Vexus FiberRPKI Not found209.205.137.0
- 209.205.138.0/23AS4314Vexus FiberRPKI Not found209.205.138.0
- 209.205.140.0/24AS13693Vexus FiberRPKI Not found209.205.140.0
- 209.205.141.0/24AS13693Vexus FiberRPKI Not found209.205.141.0
- 209.205.142.0/23AS13693Vexus FiberRPKI Not found209.205.142.0
- 209.205.144.0/24AS4314Vexus FiberRPKI Not found209.205.144.0
- 209.205.145.0/24AS4314Vexus FiberRPKI Not found209.205.145.0
- 209.205.146.0/23AS13693Vexus FiberRPKI Not found209.205.146.0
- 209.205.148.0/23AS13693Vexus FiberRPKI Not found209.205.148.0
- 209.205.150.0/24AS4314Vexus FiberRPKI Not found209.205.150.0
- 209.205.151.0/24AS13693Vexus FiberRPKI Not found209.205.151.0
- 209.205.152.0/24AS13693Vexus FiberRPKI Not found209.205.152.0
- 209.205.153.0/24AS13693Vexus FiberRPKI Not found209.205.153.0
- 209.205.154.0/24AS4314Vexus FiberRPKI Not found209.205.154.0
- 209.205.155.0/24AS13693Vexus FiberRPKI Not found209.205.155.0
- 209.205.156.0/23AS13693Vexus FiberRPKI Not found209.205.156.0
- 209.205.158.0/24AS13693Vexus FiberRPKI Not found209.205.158.0
- 209.205.159.0/24AS13693Vexus FiberRPKI Not found209.205.159.0
- 209.205.160.0/22AS13693Vexus FiberRPKI Not found209.205.160.0
- 209.205.164.0/24AS4314Vexus FiberRPKI Not found209.205.164.0
- 209.205.165.0/24AS4314Vexus FiberRPKI Not found209.205.165.0
- 209.205.166.0/24AS4314Vexus FiberRPKI Not found209.205.166.0
- 209.205.167.0/24AS4314Vexus FiberRPKI Not found209.205.167.0
- 209.205.168.0/24AS13693Vexus FiberRPKI Not found209.205.168.0
- 209.205.169.0/24AS13693Vexus FiberRPKI Not found209.205.169.0
- 209.205.171.0/24AS4314Vexus FiberRPKI Not found209.205.171.0
- 209.205.172.0/24AS13693Vexus FiberRPKI Not found209.205.172.0
- 209.205.173.0/24AS13693Vexus FiberRPKI Not found209.205.173.0
- 209.205.174.0/24AS13693Vexus FiberRPKI Not found209.205.174.0
- 209.205.176.0/24AS13693Vexus FiberRPKI Not found209.205.176.0
- 209.205.177.0/24AS13693Vexus FiberRPKI Not found209.205.177.0
- 209.205.178.0/24AS13693Vexus FiberRPKI Not found209.205.178.0
- 209.205.179.0/24AS13693Vexus FiberRPKI Not found209.205.179.0
- 209.205.180.0/24AS13693Vexus FiberRPKI Not found209.205.180.0
- 209.205.181.0/24AS13693Vexus FiberRPKI Not found209.205.181.0
- 209.205.182.0/24AS4314Vexus FiberRPKI Not found209.205.182.0
- 209.205.183.0/24AS13693Vexus FiberRPKI Not found209.205.183.0
- 209.205.184.0/24AS4314Vexus FiberRPKI Not found209.205.184.0
- 209.205.185.0/24AS4314Vexus FiberRPKI Not found209.205.185.0
- 209.205.186.0/24AS4314Vexus FiberRPKI Not found209.205.186.0
- 209.205.187.0/24AS13693Vexus FiberRPKI Not found209.205.187.0
- 209.205.188.0/24AS4314Vexus FiberRPKI Not found209.205.188.0
- 209.205.190.0/24AS13693Vexus FiberRPKI Not found209.205.190.0
- 209.205.191.0/24AS13693Vexus FiberRPKI Not found209.205.191.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.