Skip to content
ipaddress.fi

BGP Prefix Lookup

Enter a prefix (or a single address). Answered from our daily copy of the global routing table.

Examples:

113.64.0.0/11

One collector's view (APNIC). A route filtered before it reaches that collector is not listed.

Announced exactly

Registry
APNIC · China · Nov 3, 2008
Delegated block
113.64.0.0 – 113.95.255.255

Covering routes

0

No less-specific route covers it.

More-specific routes

33 more-specifics from 8 origin AS(es)
  • 113.64.0.0/20AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid113.64.0.0
  • 113.64.16.0/20AS140309CHINATELECOM-GUANGDONG-ZHONGSHAN-5G-NETWORK CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Not found113.64.16.0
  • 113.64.32.0/20AS140318CHINATELECOM-GUANGDONG-HEYUAN-5G-NETWORK CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found113.64.32.0
  • 113.64.128.0/18AS140309CHINATELECOM-GUANGDONG-ZHONGSHAN-5G-NETWORK CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Not found113.64.128.0
  • 113.64.208.0/22AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Valid113.64.208.0
  • 113.64.210.0/24AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Invalid113.64.210.0
  • 113.64.211.0/24AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Invalid113.64.211.0
  • 113.64.212.0/22AS140311CHINATELECOM-GUANGDONG-JIANGMEN-5G-NETWORK CHINATELECOM Guangdong province Jiangmen 5G networkRPKI Valid113.64.212.0
  • 113.64.230.0/23AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid113.64.230.0
  • 113.64.248.0/24AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid113.64.248.0
  • 113.64.252.0/22AS140311CHINATELECOM-GUANGDONG-JIANGMEN-5G-NETWORK CHINATELECOM Guangdong province Jiangmen 5G networkRPKI Valid113.64.252.0
  • 113.75.0.0/21AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid113.75.0.0
  • 113.75.8.0/21AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid113.75.8.0
  • 113.75.16.0/20AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid113.75.16.0
  • 113.75.32.0/21AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid113.75.32.0
  • 113.75.40.0/21AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid113.75.40.0
  • 113.75.48.0/21AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid113.75.48.0
  • 113.75.56.0/21AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid113.75.56.0
  • 113.75.64.0/18AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid113.75.64.0
  • 113.75.128.0/20AS140318CHINATELECOM-GUANGDONG-HEYUAN-5G-NETWORK CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found113.75.128.0
  • 113.75.144.0/20AS140318CHINATELECOM-GUANGDONG-HEYUAN-5G-NETWORK CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found113.75.144.0
  • 113.75.160.0/21AS140318CHINATELECOM-GUANGDONG-HEYUAN-5G-NETWORK CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found113.75.160.0
  • 113.75.168.0/21AS140318CHINATELECOM-GUANGDONG-HEYUAN-5G-NETWORK CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found113.75.168.0
  • 113.75.176.0/20AS140318CHINATELECOM-GUANGDONG-HEYUAN-5G-NETWORK CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found113.75.176.0
  • 113.75.192.0/18AS140318CHINATELECOM-GUANGDONG-HEYUAN-5G-NETWORK CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found113.75.192.0
  • 113.82.128.0/19AS140320CHINATELECOM-GUANGDONG-SHANWEI-5G-NETWORK CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid113.82.128.0
  • 113.82.160.0/19AS140320CHINATELECOM-GUANGDONG-SHANWEI-5G-NETWORK CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid113.82.160.0
  • 113.82.192.0/19AS140320CHINATELECOM-GUANGDONG-SHANWEI-5G-NETWORK CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid113.82.192.0
  • 113.82.224.0/19AS140320CHINATELECOM-GUANGDONG-SHANWEI-5G-NETWORK CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid113.82.224.0
  • 113.84.0.0/17AS134774CHINANET-GUANGDONG-SHENZHEN-MAN CHINANET Guangdong province Shenzhen MAN networkRPKI Valid113.84.0.0
  • 113.84.128.0/17AS134774CHINANET-GUANGDONG-SHENZHEN-MAN CHINANET Guangdong province Shenzhen MAN networkRPKI Valid113.84.128.0
  • 113.85.0.0/17AS140311CHINATELECOM-GUANGDONG-JIANGMEN-5G-NETWORK CHINATELECOM Guangdong province Jiangmen 5G networkRPKI Valid113.85.0.0
  • 113.93.0.0/16AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Valid113.93.0.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.

Related