BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
78.130.128.0/17
Announced exactly
- 78.130.128.0/17AS9070Cooolbox ADRPKI Valid78.130.128.0
- Registry
- RIPE NCC · Bulgaria · May 11, 2007
- Delegated block
- 78.130.128.0 – 78.130.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 78.130.128.0/24AS48900Info Data Center Ltd.RPKI Valid78.130.128.0
- 78.130.132.0/22AS29667Atlantis Net Ltd.RPKI Valid78.130.132.0
- 78.130.136.0/22AS29667Atlantis Net Ltd.RPKI Valid78.130.136.0
- 78.130.140.0/23AS29667Atlantis Net Ltd.RPKI Valid78.130.140.0
- 78.130.143.0/24AS47647E-FELLOWSRPKI Valid78.130.143.0
- 78.130.152.0/24AS9070Cooolbox ADRPKI Valid78.130.152.0
- 78.130.153.0/24AS9070Cooolbox ADRPKI Valid78.130.153.0
- 78.130.154.0/24AS9070Cooolbox ADRPKI Valid78.130.154.0
- 78.130.156.0/24AS15362Risk Engineering Ltd.RPKI Valid78.130.156.0
- 78.130.158.0/24AS9070Cooolbox ADRPKI Valid78.130.158.0
- 78.130.159.0/24AS9070Cooolbox ADRPKI Valid78.130.159.0
- 78.130.160.0/24AS9070Cooolbox ADRPKI Valid78.130.160.0
- 78.130.161.0/24AS9070Cooolbox ADRPKI Valid78.130.161.0
- 78.130.162.0/24AS9070Cooolbox ADRPKI Valid78.130.162.0
- 78.130.163.0/24AS9070Cooolbox ADRPKI Valid78.130.163.0
- 78.130.164.0/24AS9070Cooolbox ADRPKI Valid78.130.164.0
- 78.130.165.0/24AS9070Cooolbox ADRPKI Valid78.130.165.0
- 78.130.166.0/24AS9070Cooolbox ADRPKI Valid78.130.166.0
- 78.130.182.0/24AS9070Cooolbox ADRPKI Valid78.130.182.0
- 78.130.210.0/24AS9070Cooolbox ADRPKI Valid78.130.210.0
- 78.130.211.0/24AS9070Cooolbox ADRPKI Valid78.130.211.0
- 78.130.212.0/24AS9070Cooolbox ADRPKI Valid78.130.212.0
- 78.130.213.0/24AS9070Cooolbox ADRPKI Valid78.130.213.0
- 78.130.214.0/24AS9070Cooolbox ADRPKI Valid78.130.214.0
- 78.130.215.0/24AS9070Cooolbox ADRPKI Valid78.130.215.0
- 78.130.222.0/24AS9070Cooolbox ADRPKI Valid78.130.222.0
- 78.130.223.0/24AS9070Cooolbox ADRPKI Valid78.130.223.0
- 78.130.224.0/24AS9070Cooolbox ADRPKI Valid78.130.224.0
- 78.130.228.0/24AS9070Cooolbox ADRPKI Valid78.130.228.0
- 78.130.229.0/24AS9070Cooolbox ADRPKI Valid78.130.229.0
- 78.130.230.0/24AS9070Cooolbox ADRPKI Valid78.130.230.0
- 78.130.231.0/24AS9070Cooolbox ADRPKI Valid78.130.231.0
- 78.130.236.0/24AS9070Cooolbox ADRPKI Valid78.130.236.0
- 78.130.239.0/24AS9070Cooolbox ADRPKI Valid78.130.239.0
- 78.130.254.0/24AS9070Cooolbox ADRPKI Valid78.130.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, 49.224.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.