BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
205.228.0.0/14
Announced exactly
- 205.228.0.0/14AS701Verizon BusinessRPKI Not found205.228.0.0
- Registry
- ARIN · United States · Apr 14, 1995
- Delegated block
- 205.228.0.0 – 205.231.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 205.228.11.0/24AS56311Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.11.0
- 205.228.12.0/24AS5049Morgan Stanley Group Inc.RPKI Not found205.228.12.0
- 205.228.15.0/24AS5049Morgan Stanley Group Inc.RPKI Not found205.228.15.0
- 205.228.18.0/24AS5049Morgan Stanley Group Inc.RPKI Not found205.228.18.0
- 205.228.26.0/24AS56311Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.26.0
- 205.228.37.0/24AS18221Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.37.0
- 205.228.38.0/24AS38282Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.38.0
- 205.228.41.0/24AS56311Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.41.0
- 205.228.50.0/24AS56311Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.50.0
- 205.228.51.0/24AS56311Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.51.0
- 205.228.53.0/24AS5049Morgan Stanley Group Inc.RPKI Not found205.228.53.0
- 205.228.54.0/24AS5049Morgan Stanley Group Inc.RPKI Not found205.228.54.0
- 205.228.64.0/19AS21439Morgan Stanley & Co. International PLCRPKI Not found205.228.64.0
- 205.228.96.0/24AS18258Morgan Stanley Japan LimitedRPKI Not found205.228.96.0
- 205.228.99.0/24AS10082Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.99.0
- 205.228.101.0/24AS10082Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.101.0
- 205.228.102.0/24AS10082Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.102.0
- 205.228.104.0/24AS18258Morgan Stanley Japan LimitedRPKI Not found205.228.104.0
- 205.228.106.0/24AS10082Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.106.0
- 205.228.108.0/24AS18258Morgan Stanley Japan LimitedRPKI Not found205.228.108.0
- 205.228.109.0/24AS10082Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.109.0
- 205.228.111.0/24AS10082Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.111.0
- 205.228.112.0/24AS56080Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.112.0
- 205.228.118.0/24AS18258Morgan Stanley Japan LimitedRPKI Not found205.228.118.0
- 205.228.122.0/24AS56080Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.122.0
- 205.228.123.0/24AS18258Morgan Stanley Japan LimitedRPKI Not found205.228.123.0
- 205.228.124.0/24AS10082Morgan Stanley Management Service (Singapore) Pte. LtdRPKI Not found205.228.124.0
- 205.228.245.0/24AS7270IDT CorporationRPKI Not found205.228.245.0
- 205.229.101.0/24AS21759National Rural Utilities Cooperative Finance CorporationRPKI Not found205.229.101.0
- 205.231.96.0/20AS4195D. E. Shaw & Co. LPRPKI Not found205.231.96.0
- 205.231.102.0/24AS4195D. E. Shaw & Co. LPRPKI Not found205.231.102.0
- 205.231.104.0/24AS4195D. E. Shaw & Co. LPRPKI Not found205.231.104.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.