BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
80.253.128.0/19
Announced exactly
- 80.253.128.0/19AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.128.0
- Registry
- RIPE NCC · Iran · Dec 13, 2001
- Delegated block
- 80.253.128.0 – 80.253.143.255
Covering routes
No less-specific route covers it.
More-specific routes
- 80.253.129.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.129.0
- 80.253.133.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.133.0
- 80.253.135.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.135.0
- 80.253.136.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.136.0
- 80.253.139.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.139.0
- 80.253.140.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.140.0
- 80.253.145.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.145.0
- 80.253.147.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.147.0
- 80.253.148.0/22AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.148.0
- 80.253.148.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.148.0
- 80.253.151.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.151.0
- 80.253.152.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.152.0
- 80.253.157.0/24AS59708Rayan Hamafza Company Public Joint StockRPKI Valid80.253.157.0
- 80.253.158.0/24AS24631Tose'h Fanavari Ertebabat Pasargad Arian Co. PJSRPKI Valid80.253.158.0
- 80.253.159.0/24AS61239Naji Research & Development Company Private Join-StockRPKI Valid80.253.159.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.