BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
128.177.0.0/16
Announced exactly
- 128.177.0.0/16AS6461Zayo BandwidthRPKI Valid128.177.0.0
- Registry
- ARIN · United States · Jul 28, 1997
- Delegated block
- 128.177.0.0 – 128.177.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 128.177.2.0/24AS7170Manhattan West, LLCRPKI Valid128.177.2.0
- 128.177.3.0/24AS13344NetEx Inc.RPKI Valid128.177.3.0
- 128.177.13.0/24AS398731Goodman Manufacturing Company, L.P.RPKI Valid128.177.13.0
- 128.177.14.0/24AS21534BroadSoft, Inc.RPKI Valid128.177.14.0
- 128.177.31.0/24AS32337Nowcom CorporationRPKI Valid128.177.31.0
- 128.177.36.0/24AS21534BroadSoft, Inc.RPKI Valid128.177.36.0
- 128.177.43.0/24AS400523InterSystems CorporationRPKI Valid128.177.43.0
- 128.177.52.0/24AS31998Konceptio Data Services LLCRPKI Valid128.177.52.0
- 128.177.60.0/24AS19753RESERVEDRPKI Valid128.177.60.0
- 128.177.93.0/24AS33321Zayo BandwidthRPKI Valid128.177.93.0
- 128.177.95.0/24AS3257GTT-BACKBONE GTTRPKI Invalid128.177.95.0
- 128.177.99.0/24AS53294Fox News ChannelRPKI Valid128.177.99.0
- 128.177.102.0/24AS19755Cruise LLCRPKI Valid128.177.102.0
- 128.177.111.0/24AS26664BECURPKI Valid128.177.111.0
- 128.177.125.0/24AS22616ZSCALER, INC.RPKI Valid128.177.125.0
- 128.177.129.0/24AS22616ZSCALER, INC.RPKI Valid128.177.129.0
- 128.177.134.0/24AS41264GOOGLE-IT-RO-ISPRPKI Valid128.177.134.0
- 128.177.135.0/24AS22616ZSCALER, INC.RPKI Valid128.177.135.0
- 128.177.136.0/24AS22616ZSCALER, INC.RPKI Valid128.177.136.0
- 128.177.137.0/24AS46667Evercore Partners Services East, LLCRPKI Valid128.177.137.0
- 128.177.138.0/24AS18731Cityside FiberRPKI Valid128.177.138.0
- 128.177.160.0/24AS21734Trading Technologies Intl, Inc.RPKI Valid128.177.160.0
- 128.177.161.0/24AS36180Cisco IoTRPKI Valid128.177.161.0
- 128.177.179.0/24AS203Level 3 Parent, LLCRPKI Valid128.177.179.0
- 128.177.181.0/24AS63296Amarillo WirelessRPKI Valid128.177.181.0
- 128.177.186.0/24AS25755National Public Radio, Inc.RPKI Valid128.177.186.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.