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:

61.140.0.0/14

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

Announced exactly

Registry
APNIC · China · Jun 24, 1999
Delegated block
61.140.0.0 – 61.143.255.255

Covering routes

0

No less-specific route covers it.

More-specific routes

34 more-specifics from 9 origin AS(es)
  • 61.141.0.0/22AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid61.141.0.0
  • 61.141.1.0/24AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid61.141.1.0
  • 61.141.4.0/24AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid61.141.4.0
  • 61.141.6.0/23AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid61.141.6.0
  • 61.141.8.0/21AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid61.141.8.0
  • 61.141.16.0/20AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid61.141.16.0
  • 61.141.33.0/24AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid61.141.33.0
  • 61.141.34.0/23AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid61.141.34.0
  • 61.141.48.0/23AS134763CT-DONGGUAN-IDC CHINANET Guangdong province networkRPKI Valid61.141.48.0
  • 61.141.63.0/24AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid61.141.63.0
  • 61.142.48.0/24AS140309CHINATELECOM-GUANGDONG-ZHONGSHAN-5G-NETWORK CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Valid61.142.48.0
  • 61.142.49.0/24AS140311CHINATELECOM-GUANGDONG-JIANGMEN-5G-NETWORK CHINATELECOM Guangdong province Jiangmen 5G networkRPKI Valid61.142.49.0
  • 61.143.0.0/20AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Valid61.143.0.0
  • 61.143.0.0/24AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Invalid61.143.0.0
  • 61.143.2.0/24AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Invalid61.143.2.0
  • 61.143.3.0/24AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Invalid61.143.3.0
  • 61.143.4.0/24AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Invalid61.143.4.0
  • 61.143.5.0/24AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Invalid61.143.5.0
  • 61.143.6.0/24AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Invalid61.143.6.0
  • 61.143.8.0/21AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Invalid61.143.8.0
  • 61.143.16.0/21AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Valid61.143.16.0
  • 61.143.24.0/23AS136199CHINANET-GUANGDONG-YUEDONG-MAN CHINANET Guangdong province Yuedong MAN networkRPKI Valid61.143.24.0
  • 61.143.26.0/23AS135089CHINANET-GUANGZHOU-SOUTHBASE-IDC China TelecomRPKI Valid61.143.26.0
  • 61.143.136.0/21AS140311CHINATELECOM-GUANGDONG-JIANGMEN-5G-NETWORK CHINATELECOM Guangdong province Jiangmen 5G networkRPKI Valid61.143.136.0
  • 61.143.144.0/21AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid61.143.144.0
  • 61.143.145.0/24AS140319CHINATELECOM-GUANGDONG-QINGYUAN-5G-NETWORK CHINATELECOM Guangdong province Qingyuan 5G networkRPKI Valid61.143.145.0
  • 61.143.152.0/23AS140309CHINATELECOM-GUANGDONG-ZHONGSHAN-5G-NETWORK CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Not found61.143.152.0
  • 61.143.155.0/24AS140309CHINATELECOM-GUANGDONG-ZHONGSHAN-5G-NETWORK CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Not found61.143.155.0
  • 61.143.156.0/22AS140309CHINATELECOM-GUANGDONG-ZHONGSHAN-5G-NETWORK CHINATELECOM Guangdong province Zhongshan 5G networkRPKI Not found61.143.156.0
  • 61.143.168.0/21AS140320CHINATELECOM-GUANGDONG-SHANWEI-5G-NETWORK CHINATELECOM Guangdong province Shanwei 5G networkRPKI Valid61.143.168.0
  • 61.143.184.0/21AS140308CHINATELECOM-GUANGDONG-ZHUHAI-5G-NETWORK CHINATELECOM Guangdong province Zhuhai 5G networkRPKI Valid61.143.184.0
  • 61.143.240.0/21AS140318CHINATELECOM-GUANGDONG-HEYUAN-5G-NETWORK CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found61.143.240.0
  • 61.143.248.0/22AS140318CHINATELECOM-GUANGDONG-HEYUAN-5G-NETWORK CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found61.143.248.0
  • 61.143.252.0/22AS140318CHINATELECOM-GUANGDONG-HEYUAN-5G-NETWORK CHINATELECOM Guangdong province Heyuan 5G networkRPKI Not found61.143.252.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