BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
194.231.0.0/16
Announced exactly
- 194.231.0.0/16AS3257GTT Communications Inc.RPKI Not found194.231.0.0
- Registry
- RIPE NCC · United States · Jan 24, 1996
- Delegated block
- 194.231.0.0 – 194.231.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 194.231.0.0/21AS3320Deutsche Telekom AGRPKI Not found194.231.0.0
- 194.231.8.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.8.0
- 194.231.12.0/23AS3320Deutsche Telekom AGRPKI Not found194.231.12.0
- 194.231.16.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.16.0
- 194.231.20.0/23AS3320Deutsche Telekom AGRPKI Not found194.231.20.0
- 194.231.23.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.23.0
- 194.231.24.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.24.0
- 194.231.28.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.28.0
- 194.231.30.0/23AS3320Deutsche Telekom AGRPKI Not found194.231.30.0
- 194.231.32.0/23AS3320Deutsche Telekom AGRPKI Not found194.231.32.0
- 194.231.35.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.35.0
- 194.231.36.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.36.0
- 194.231.41.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.41.0
- 194.231.42.0/23AS3320Deutsche Telekom AGRPKI Not found194.231.42.0
- 194.231.44.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.44.0
- 194.231.48.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.48.0
- 194.231.51.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.51.0
- 194.231.54.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.54.0
- 194.231.56.0/21AS3320Deutsche Telekom AGRPKI Not found194.231.56.0
- 194.231.64.0/20AS3320Deutsche Telekom AGRPKI Not found194.231.64.0
- 194.231.80.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.80.0
- 194.231.84.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.84.0
- 194.231.86.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.86.0
- 194.231.88.0/21AS3320Deutsche Telekom AGRPKI Not found194.231.88.0
- 194.231.96.0/21AS3320Deutsche Telekom AGRPKI Not found194.231.96.0
- 194.231.104.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.104.0
- 194.231.105.0/24AS5605NetUSE AGRPKI Not found194.231.105.0
- 194.231.106.0/23AS3320Deutsche Telekom AGRPKI Not found194.231.106.0
- 194.231.108.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.108.0
- 194.231.112.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.112.0
- 194.231.114.0/23AS3320Deutsche Telekom AGRPKI Not found194.231.114.0
- 194.231.116.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.116.0
- 194.231.120.0/21AS3320Deutsche Telekom AGRPKI Not found194.231.120.0
- 194.231.128.0/24AS44803Webdock.io ApSRPKI Valid194.231.128.0
- 194.231.129.0/24AS44803Webdock.io ApSRPKI Valid194.231.129.0
- 194.231.130.0/24AS44803Webdock.io ApSRPKI Valid194.231.130.0
- 194.231.131.0/24AS44803Webdock.io ApSRPKI Valid194.231.131.0
- 194.231.133.0/24AS61317Hivelocity LLCRPKI Valid194.231.133.0
- 194.231.134.0/24AS218729TEXT TECHNOLOGY LIMITEDRPKI Valid194.231.134.0
- 194.231.140.0/24AS154402Fredyun NetworkRPKI Valid194.231.140.0
- 194.231.141.0/24AS140641YOTTA NETWORK SERVICES PRIVATE LIMITEDRPKI Valid194.231.141.0
- 194.231.144.0/22AS4766Korea TelecomRPKI Valid194.231.144.0
- 194.231.153.0/24AS134494Code For Host Inc LtdRPKI Valid194.231.153.0
- 194.231.155.0/24AS397630Blazing SEO, LLCRPKI Valid194.231.155.0
- 194.231.156.0/24AS396356Latitude.shRPKI Valid194.231.156.0
- 194.231.160.0/20AS3320Deutsche Telekom AGRPKI Not found194.231.160.0
- 194.231.176.0/21AS3320Deutsche Telekom AGRPKI Not found194.231.176.0
- 194.231.184.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.184.0
- 194.231.188.0/23AS3320Deutsche Telekom AGRPKI Not found194.231.188.0
- 194.231.191.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.191.0
- 194.231.192.0/23AS5650Frontier Communications of America, Inc.RPKI Valid194.231.192.0
- 194.231.194.0/24AS20473The Constant Company, LLCRPKI Valid194.231.194.0
- 194.231.197.0/24AS61317Hivelocity LLCRPKI Valid194.231.197.0
- 194.231.200.0/24AS44803Webdock.io ApSRPKI Valid194.231.200.0
- 194.231.202.0/24AS218862DIGITAL ZERO ONE LTDRPKI Valid194.231.202.0
- 194.231.204.0/24AS47377Orange Belgium SARPKI Valid194.231.204.0
- 194.231.205.0/24AS47377Orange Belgium SARPKI Valid194.231.205.0
- 194.231.206.0/24AS47377Orange Belgium SARPKI Valid194.231.206.0
- 194.231.207.0/24AS47377Orange Belgium SARPKI Valid194.231.207.0
- 194.231.215.0/24AS401476Spruce Creek Networks LLCRPKI Valid194.231.215.0
- 194.231.216.0/24AS199808ShieldCore SASRPKI Valid194.231.216.0
- 194.231.217.0/24AS208915HYPERLXC MEDICAL LTDRPKI Valid194.231.217.0
- 194.231.220.0/24AS209622uPress IncRPKI Valid194.231.220.0
- 194.231.224.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.224.0
- 194.231.229.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.229.0
- 194.231.230.0/23AS3320Deutsche Telekom AGRPKI Not found194.231.230.0
- 194.231.232.0/21AS3320Deutsche Telekom AGRPKI Not found194.231.232.0
- 194.231.240.0/22AS3320Deutsche Telekom AGRPKI Not found194.231.240.0
- 194.231.244.0/23AS3320Deutsche Telekom AGRPKI Not found194.231.244.0
- 194.231.247.0/24AS3320Deutsche Telekom AGRPKI Not found194.231.247.0
- 194.231.248.0/21AS3320Deutsche Telekom AGRPKI Not found194.231.248.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.