BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
149.34.0.0/15
Announced exactly
- 149.34.0.0/15AS174Cogent Communications, LLCRPKI Not found149.34.0.0
- Registry
- ARIN · United States · Jan 28, 1992
- Delegated block
- 149.34.0.0 – 149.34.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 149.34.32.0/24AS174Cogent Communications, LLCRPKI Not found149.34.32.0
- 149.34.33.0/24AS174Cogent Communications, LLCRPKI Not found149.34.33.0
- 149.34.34.0/24AS174Cogent Communications, LLCRPKI Not found149.34.34.0
- 149.34.35.0/24AS174Cogent Communications, LLCRPKI Not found149.34.35.0
- 149.34.36.0/24AS174Cogent Communications, LLCRPKI Not found149.34.36.0
- 149.34.37.0/24AS174Cogent Communications, LLCRPKI Not found149.34.37.0
- 149.34.38.0/24AS174Cogent Communications, LLCRPKI Not found149.34.38.0
- 149.34.39.0/24AS174Cogent Communications, LLCRPKI Not found149.34.39.0
- 149.34.40.0/24AS174Cogent Communications, LLCRPKI Not found149.34.40.0
- 149.34.41.0/24AS174Cogent Communications, LLCRPKI Not found149.34.41.0
- 149.34.42.0/24AS174Cogent Communications, LLCRPKI Not found149.34.42.0
- 149.34.43.0/24AS174Cogent Communications, LLCRPKI Not found149.34.43.0
- 149.34.44.0/24AS174Cogent Communications, LLCRPKI Not found149.34.44.0
- 149.34.45.0/24AS174Cogent Communications, LLCRPKI Not found149.34.45.0
- 149.34.46.0/24AS174Cogent Communications, LLCRPKI Not found149.34.46.0
- 149.34.47.0/24AS174Cogent Communications, LLCRPKI Not found149.34.47.0
- 149.34.48.0/24AS3132Red Cientifica PeruanaRPKI Not found149.34.48.0
- 149.34.49.0/24AS3132Red Cientifica PeruanaRPKI Not found149.34.49.0
- 149.34.50.0/24AS3132Red Cientifica PeruanaRPKI Not found149.34.50.0
- 149.34.51.0/24AS3132Red Cientifica PeruanaRPKI Not found149.34.51.0
- 149.34.128.0/18AS201838ASN-COMMUNITYFIBRERPKI Not found149.34.128.0
- 149.34.192.0/19AS208972GIBIRNET-RPKI Valid149.34.192.0
- 149.34.192.0/24AS208972GIBIRNET-RPKI Valid149.34.192.0
- 149.34.193.0/24AS208972GIBIRNET-RPKI Valid149.34.193.0
- 149.34.194.0/24AS208972GIBIRNET-RPKI Valid149.34.194.0
- 149.34.195.0/24AS208972GIBIRNET-RPKI Valid149.34.195.0
- 149.34.196.0/24AS208972GIBIRNET-RPKI Valid149.34.196.0
- 149.34.197.0/24AS208972GIBIRNET-RPKI Valid149.34.197.0
- 149.34.198.0/24AS208972GIBIRNET-RPKI Valid149.34.198.0
- 149.34.199.0/24AS208972GIBIRNET-RPKI Valid149.34.199.0
- 149.34.200.0/24AS208972GIBIRNET-RPKI Valid149.34.200.0
- 149.34.201.0/24AS208972GIBIRNET-RPKI Valid149.34.201.0
- 149.34.202.0/24AS208972GIBIRNET-RPKI Valid149.34.202.0
- 149.34.203.0/24AS208972GIBIRNET-RPKI Valid149.34.203.0
- 149.34.204.0/24AS208972GIBIRNET-RPKI Valid149.34.204.0
- 149.34.205.0/24AS208972GIBIRNET-RPKI Valid149.34.205.0
- 149.34.206.0/24AS208972GIBIRNET-RPKI Valid149.34.206.0
- 149.34.207.0/24AS208972GIBIRNET-RPKI Valid149.34.207.0
- 149.34.208.0/24AS208972GIBIRNET-RPKI Valid149.34.208.0
- 149.34.209.0/24AS208972GIBIRNET-RPKI Valid149.34.209.0
- 149.34.210.0/24AS208972GIBIRNET-RPKI Valid149.34.210.0
- 149.34.211.0/24AS208972GIBIRNET-RPKI Valid149.34.211.0
- 149.34.212.0/24AS208972GIBIRNET-RPKI Valid149.34.212.0
- 149.34.213.0/24AS208972GIBIRNET-RPKI Valid149.34.213.0
- 149.34.214.0/24AS208972GIBIRNET-RPKI Valid149.34.214.0
- 149.34.215.0/24AS208972GIBIRNET-RPKI Valid149.34.215.0
- 149.34.216.0/24AS208972GIBIRNET-RPKI Valid149.34.216.0
- 149.34.217.0/24AS208972GIBIRNET-RPKI Valid149.34.217.0
- 149.34.218.0/24AS208972GIBIRNET-RPKI Valid149.34.218.0
- 149.34.219.0/24AS208972GIBIRNET-RPKI Valid149.34.219.0
- 149.34.220.0/24AS208972GIBIRNET-RPKI Valid149.34.220.0
- 149.34.221.0/24AS208972GIBIRNET-RPKI Valid149.34.221.0
- 149.34.222.0/24AS208972GIBIRNET-RPKI Valid149.34.222.0
- 149.34.223.0/24AS208972GIBIRNET-RPKI Valid149.34.223.0
- 149.34.224.0/20AS27823Dattatec.comRPKI Valid149.34.224.0
- 149.34.224.0/24AS27823Dattatec.comRPKI Valid149.34.224.0
- 149.34.225.0/24AS27823Dattatec.comRPKI Valid149.34.225.0
- 149.34.226.0/24AS27823Dattatec.comRPKI Valid149.34.226.0
- 149.34.227.0/24AS27823Dattatec.comRPKI Valid149.34.227.0
- 149.34.240.0/24AS212238CDNEXTRPKI Not found149.34.240.0
- 149.34.241.0/24AS212238CDNEXTRPKI Not found149.34.241.0
- 149.34.242.0/23AS212238CDNEXTRPKI Not found149.34.242.0
- 149.34.244.0/24AS212238CDNEXTRPKI Not found149.34.244.0
- 149.34.245.0/24AS212238CDNEXTRPKI Not found149.34.245.0
- 149.34.246.0/24AS212238CDNEXTRPKI Not found149.34.246.0
- 149.34.247.0/24AS212238CDNEXTRPKI Not found149.34.247.0
- 149.34.248.0/24AS212238CDNEXTRPKI Not found149.34.248.0
- 149.34.249.0/24AS212238CDNEXTRPKI Not found149.34.249.0
- 149.34.250.0/24AS212238CDNEXTRPKI Not found149.34.250.0
- 149.34.251.0/24AS212238CDNEXTRPKI Not found149.34.251.0
- 149.34.252.0/24AS212238CDNEXTRPKI Not found149.34.252.0
- 149.34.253.0/24AS212238CDNEXTRPKI Not found149.34.253.0
- 149.34.254.0/23AS212238CDNEXTRPKI Not found149.34.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, 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.