BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
149.235.0.0/16
Announced exactly
- 149.235.0.0/16AS3257GTT Communications Inc.RPKI Not found149.235.0.0
- Registry
- RIPE NCC · Germany · Jan 1, 1984
- Delegated block
- 149.235.0.0 – 149.235.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 149.235.0.0/20AS203160Open Text CorporationRPKI Not found149.235.0.0
- 149.235.0.0/21AS203160Open Text CorporationRPKI Not found149.235.0.0
- 149.235.8.0/21AS203160Open Text CorporationRPKI Not found149.235.8.0
- 149.235.8.0/24AS203160Open Text CorporationRPKI Not found149.235.8.0
- 149.235.10.0/24AS203160Open Text CorporationRPKI Not found149.235.10.0
- 149.235.11.0/24AS203160Open Text CorporationRPKI Not found149.235.11.0
- 149.235.12.0/24AS203160Open Text CorporationRPKI Not found149.235.12.0
- 149.235.13.0/24AS203160Open Text CorporationRPKI Not found149.235.13.0
- 149.235.14.0/24AS203160Open Text CorporationRPKI Not found149.235.14.0
- 149.235.15.0/24AS203160Open Text CorporationRPKI Not found149.235.15.0
- 149.235.16.0/21AS205527Open Text CorporationRPKI Not found149.235.16.0
- 149.235.16.0/24AS205527Open Text CorporationRPKI Not found149.235.16.0
- 149.235.17.0/24AS205527Open Text CorporationRPKI Not found149.235.17.0
- 149.235.18.0/24AS205527Open Text CorporationRPKI Not found149.235.18.0
- 149.235.22.0/24AS2686AT&T Enterprises, LLCRPKI Not found149.235.22.0
- 149.235.23.0/24AS205527Open Text CorporationRPKI Not found149.235.23.0
- 149.235.24.0/21AS205527Open Text CorporationRPKI Not found149.235.24.0
- 149.235.26.0/23AS205527Open Text CorporationRPKI Not found149.235.26.0
- 149.235.28.0/23AS205527Open Text CorporationRPKI Not found149.235.28.0
- 149.235.32.0/23AS8232GXS International Inc.RPKI Not found149.235.32.0
- 149.235.34.0/23AS8232GXS International Inc.RPKI Not found149.235.34.0
- 149.235.36.0/22AS203160Open Text CorporationRPKI Not found149.235.36.0
- 149.235.40.0/21AS203160Open Text CorporationRPKI Not found149.235.40.0
- 149.235.48.0/21AS203160Open Text CorporationRPKI Not found149.235.48.0
- 149.235.224.0/21AS16751Open Text CorporationRPKI Not found149.235.224.0
- 149.235.241.0/24AS16751Open Text CorporationRPKI Not found149.235.241.0
- 149.235.254.0/24AS16751Open Text CorporationRPKI Not found149.235.254.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.