BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
207.179.128.0/18
Announced exactly
- 207.179.128.0/18AS855Bell CanadaRPKI Valid207.179.128.0
- Registry
- ARIN · Canada · Aug 30, 1996
- Delegated block
- 207.179.128.0 – 207.179.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 207.179.128.0/24AS855Bell CanadaRPKI Valid207.179.128.0
- 207.179.129.0/24AS855Bell CanadaRPKI Valid207.179.129.0
- 207.179.130.0/24AS29907Cirrus9 Inc.RPKI Valid207.179.130.0
- 207.179.132.0/24AS17170McCain Foods LimitedRPKI Valid207.179.132.0
- 207.179.134.0/23AS855Bell CanadaRPKI Valid207.179.134.0
- 207.179.137.0/24AS855Bell CanadaRPKI Valid207.179.137.0
- 207.179.138.0/24AS32747Atlantic Lottery CorporationRPKI Valid207.179.138.0
- 207.179.139.0/24AS32747Atlantic Lottery CorporationRPKI Valid207.179.139.0
- 207.179.143.0/24AS29907Cirrus9 Inc.RPKI Valid207.179.143.0
- 207.179.148.0/24AS855Bell CanadaRPKI Valid207.179.148.0
- 207.179.152.0/24AS855Bell CanadaRPKI Valid207.179.152.0
- 207.179.153.0/24AS855Bell CanadaRPKI Valid207.179.153.0
- 207.179.154.0/24AS855Bell CanadaRPKI Valid207.179.154.0
- 207.179.155.0/24AS29907Cirrus9 Inc.RPKI Valid207.179.155.0
- 207.179.156.0/24AS29907Cirrus9 Inc.RPKI Valid207.179.156.0
- 207.179.158.0/23AS855Bell CanadaRPKI Valid207.179.158.0
- 207.179.160.0/24AS855Bell CanadaRPKI Valid207.179.160.0
- 207.179.161.0/24AS855Bell CanadaRPKI Valid207.179.161.0
- 207.179.162.0/24AS855Bell CanadaRPKI Valid207.179.162.0
- 207.179.164.0/23AS855Bell CanadaRPKI Valid207.179.164.0
- 207.179.175.0/24AS855Bell CanadaRPKI Valid207.179.175.0
- 207.179.177.0/24AS32441Advanced Training & Services Inc.RPKI Valid207.179.177.0
- 207.179.184.0/23AS855Bell CanadaRPKI Valid207.179.184.0
- 207.179.187.0/24AS855Bell CanadaRPKI Valid207.179.187.0
- 207.179.188.0/24AS855Bell CanadaRPKI Valid207.179.188.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.