BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
141.138.0.0/18
Announced exactly
- 141.138.0.0/18AS13046Hrvatski Telekom d.d.RPKI Valid141.138.0.0
- Registry
- RIPE NCC · Croatia · Jun 29, 2011
- Delegated block
- 141.138.0.0 – 141.138.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 141.138.4.0/23AS13046Hrvatski Telekom d.d.RPKI Valid141.138.4.0
- 141.138.4.0/24AS198548Overseas Trade Co. Ltd. d.o.o.RPKI Valid141.138.4.0
- 141.138.7.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.7.0
- 141.138.8.0/22AS13046Hrvatski Telekom d.d.RPKI Valid141.138.8.0
- 141.138.8.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.8.0
- 141.138.10.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.10.0
- 141.138.11.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.11.0
- 141.138.12.0/22AS13046Hrvatski Telekom d.d.RPKI Valid141.138.12.0
- 141.138.12.0/24AS198785Sedmi Odjel d.o.o.RPKI Valid141.138.12.0
- 141.138.13.0/24AS212550Sedmi Odjel d.o.o.RPKI Valid141.138.13.0
- 141.138.14.0/24AS198785Sedmi Odjel d.o.o.RPKI Valid141.138.14.0
- 141.138.15.0/24AS212550Sedmi Odjel d.o.o.RPKI Valid141.138.15.0
- 141.138.16.0/21AS13046Hrvatski Telekom d.d.RPKI Valid141.138.16.0
- 141.138.24.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.24.0
- 141.138.25.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.25.0
- 141.138.26.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.26.0
- 141.138.29.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.29.0
- 141.138.30.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.30.0
- 141.138.31.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.31.0
- 141.138.32.0/19AS13046Hrvatski Telekom d.d.RPKI Valid141.138.32.0
- 141.138.32.0/20AS13046Hrvatski Telekom d.d.RPKI Valid141.138.32.0
- 141.138.32.0/21AS13046Hrvatski Telekom d.d.RPKI Valid141.138.32.0
- 141.138.40.0/21AS13046Hrvatski Telekom d.d.RPKI Valid141.138.40.0
- 141.138.48.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.48.0
- 141.138.49.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.49.0
- 141.138.50.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.50.0
- 141.138.53.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.53.0
- 141.138.55.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.55.0
- 141.138.57.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.57.0
- 141.138.58.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.58.0
- 141.138.59.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.59.0
- 141.138.60.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.60.0
- 141.138.61.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.61.0
- 141.138.62.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.62.0
- 141.138.63.0/24AS13046Hrvatski Telekom d.d.RPKI Valid141.138.63.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. 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.