BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
135.196.0.0/16
Announced exactly
- 135.196.0.0/16AS3257GTT Communications Inc.RPKI Not found135.196.0.0
- Registry
- RIPE NCC · United States · Sep 15, 2000
- Delegated block
- 135.196.0.0 – 135.196.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 135.196.4.0/24AS9009M247 Europe SRLRPKI Valid135.196.4.0
- 135.196.6.0/24AS30058FDCservers.netRPKI Valid135.196.6.0
- 135.196.9.0/24AS30058FDCservers.netRPKI Valid135.196.9.0
- 135.196.12.0/23AS3257GTT Communications Inc.RPKI Not found135.196.12.0
- 135.196.18.0/24AS396356Latitude.shRPKI Valid135.196.18.0
- 135.196.21.0/24AS212238Datacamp LimitedRPKI Valid135.196.21.0
- 135.196.23.0/24AS59711HZ Hosting LtdRPKI Valid135.196.23.0
- 135.196.24.0/23AS9009M247 Europe SRLRPKI Valid135.196.24.0
- 135.196.27.0/24AS59711HZ Hosting LtdRPKI Valid135.196.27.0
- 135.196.28.0/23AS9009M247 Europe SRLRPKI Valid135.196.28.0
- 135.196.31.0/24AS30058FDCservers.netRPKI Valid135.196.31.0
- 135.196.35.0/24AS59711HZ Hosting LtdRPKI Valid135.196.35.0
- 135.196.48.0/21AS3257GTT Communications Inc.RPKI Valid135.196.48.0
- 135.196.56.0/21AS3257GTT Communications Inc.RPKI Invalid135.196.56.0
- 135.196.80.0/21AS3257GTT Communications Inc.RPKI Not found135.196.80.0
- 135.196.88.0/23AS9009M247 Europe SRLRPKI Valid135.196.88.0
- 135.196.98.0/24AS59711HZ Hosting LtdRPKI Valid135.196.98.0
- 135.196.102.0/23AS9009M247 Europe SRLRPKI Valid135.196.102.0
- 135.196.105.0/24AS59711HZ Hosting LtdRPKI Valid135.196.105.0
- 135.196.106.0/24AS212238Datacamp LimitedRPKI Valid135.196.106.0
- 135.196.108.0/22AS9009M247 Europe SRLRPKI Valid135.196.108.0
- 135.196.116.0/24AS59711HZ Hosting LtdRPKI Valid135.196.116.0
- 135.196.122.0/24AS3257GTT Communications Inc.RPKI Not found135.196.122.0
- 135.196.127.0/24AS3257GTT Communications Inc.RPKI Not found135.196.127.0
- 135.196.132.0/23AS9009M247 Europe SRLRPKI Valid135.196.132.0
- 135.196.135.0/24AS3257GTT Communications Inc.RPKI Not found135.196.135.0
- 135.196.136.0/21AS3257GTT Communications Inc.RPKI Not found135.196.136.0
- 135.196.144.0/22AS9009M247 Europe SRLRPKI Valid135.196.144.0
- 135.196.155.0/24AS4766Korea TelecomRPKI Valid135.196.155.0
- 135.196.156.0/23AS9009M247 Europe SRLRPKI Valid135.196.156.0
- 135.196.158.0/24AS3320Deutsche Telekom AGRPKI Not found135.196.158.0
- 135.196.160.0/24AS3320Deutsche Telekom AGRPKI Not found135.196.160.0
- 135.196.164.0/23AS9009M247 Europe SRLRPKI Valid135.196.164.0
- 135.196.166.0/24AS4766Korea TelecomRPKI Valid135.196.166.0
- 135.196.171.0/24AS43180Trunk Networks LTDRPKI Valid135.196.171.0
- 135.196.172.0/23AS9009M247 Europe SRLRPKI Valid135.196.172.0
- 135.196.176.0/23AS9009M247 Europe SRLRPKI Valid135.196.176.0
- 135.196.180.0/23AS212238Datacamp LimitedRPKI Valid135.196.180.0
- 135.196.185.0/24AS212238Datacamp LimitedRPKI Valid135.196.185.0
- 135.196.186.0/23AS59711HZ Hosting LtdRPKI Valid135.196.186.0
- 135.196.202.0/24AS9009M247 Europe SRLRPKI Valid135.196.202.0
- 135.196.204.0/24AS9009M247 Europe SRLRPKI Valid135.196.204.0
- 135.196.218.0/24AS203061UAB code200RPKI Valid135.196.218.0
- 135.196.225.0/24AS3320Deutsche Telekom AGRPKI Not found135.196.225.0
- 135.196.227.0/24AS203061UAB code200RPKI Valid135.196.227.0
- 135.196.228.0/23AS3257GTT Communications Inc.RPKI Valid135.196.228.0
- 135.196.232.0/23AS3257GTT Communications Inc.RPKI Valid135.196.232.0
- 135.196.236.0/24AS4766Korea TelecomRPKI Valid135.196.236.0
- 135.196.238.0/23AS3257GTT Communications Inc.RPKI Valid135.196.238.0
- 135.196.244.0/24AS4766Korea TelecomRPKI Valid135.196.244.0
- 135.196.248.0/24AS4766Korea TelecomRPKI Valid135.196.248.0
- 135.196.252.0/24AS4766Korea TelecomRPKI Valid135.196.252.0
- 135.196.254.0/24AS4766Korea TelecomRPKI Valid135.196.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, 2.48.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.