BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
240c:c000::/20
Announced exactly
- 240c:c000::/20AS23910China Next Generation Internet CERNET2RPKI Not found240c:c000::
- Registry
- APNIC · China · Jan 29, 2019
- Delegated block
- 240c:c000:: – 240c:cfff:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 240c:c001::/32AS24349CERNET2 IX at Peking UniversityRPKI Valid240c:c001::
- 240c:c017::/32AS24349CERNET2 IX at Peking UniversityRPKI Valid240c:c017::
- 240c:c018::/32AS24350CERNET2 IX at Beijing University of Posts and TelecommunicationsRPKI Valid240c:c018::
- 240c:c019::/32AS24349CERNET2 IX at Peking UniversityRPKI Valid240c:c019::
- 240c:c02f::/32AS24349CERNET2 IX at Peking UniversityRPKI Valid240c:c02f::
- 240c:c0a0::/32AS23910China Next Generation Internet CERNET2RPKI Invalid240c:c0a0::
- 240c:c0a1::/32AS4538China Education and Research Network CenterRPKI Valid240c:c0a1::
- 240c:c0a8::/33AS24348CERNET2 IX at Tsinghua UniversityRPKI Valid240c:c0a8::
- 240c:c0a8::/34AS24348CERNET2 IX at Tsinghua UniversityRPKI Valid240c:c0a8::
- 240c:c0a8:3c82::/48AS138370CERNET2 regional IX at Nanchang UniversityRPKI Valid240c:c0a8:3c82::
- 240c:c0a8:4000::/34AS24348CERNET2 IX at Tsinghua UniversityRPKI Valid240c:c0a8:4000::
- 240c:c0a8:5c26::/48AS24365CERNET2 IX at Fudan UniversityRPKI Invalid240c:c0a8:5c26::
- 240c:c0a8:5c49::/48AS24366CERNET2 IX at Tongji UniversityRPKI Valid240c:c0a8:5c49::
- 240c:c0a8:8000::/33AS24348CERNET2 IX at Tsinghua UniversityRPKI Valid240c:c0a8:8000::
- 240c:c0a8:8000::/34AS24348CERNET2 IX at Tsinghua UniversityRPKI Valid240c:c0a8:8000::
- 240c:c0a8:9c01::/48AS138440CERNET2 regional IX at Hainan Normal UniversityRPKI Valid240c:c0a8:9c01::
- 240c:c0a8:c000::/34AS24348CERNET2 IX at Tsinghua UniversityRPKI Valid240c:c0a8:c000::
- 240c:c0a9:1000::/40AS4538China Education and Research Network CenterRPKI Valid240c:c0a9:1000::
- 240c:c220::/32AS24352CERNET2 IX at Tianjin UniversityRPKI Valid240c:c220::
- 240c:c221::/32AS24352CERNET2 IX at Tianjin UniversityRPKI Valid240c:c221::
- 240c:c246::/32AS138375CERNET2 regional IX at Inner Mongolia UniversityRPKI Valid240c:c246::
- 240c:c283::/32AS24353CERNET2 IX at Xi'an Jiaotong UniversityRPKI Valid240c:c283::
- 240c:c286::/32AS24353CERNET2 IX at Xi'an Jiaotong UniversityRPKI Valid240c:c286::
- 240c:c288::/32AS24353CERNET2 IX at Xi'an Jiaotong UniversityRPKI Valid240c:c288::
- 240c:c28f::/32AS24353CERNET2 IX at Xi'an Jiaotong UniversityRPKI Valid240c:c28f::
- 240c:c295::/32AS24353CERNET2 IX at Xi'an Jiaotong UniversityRPKI Valid240c:c295::
- 240c:c29f::/32AS24353CERNET2 IX at Xi'an Jiaotong UniversityRPKI Valid240c:c29f::
- 240c:c381::/32AS138377CERNET2 regional IX at Qinghai Normal UniversityRPKI Valid240c:c381::
- 240c:c406::/32AS24369CERNET2 IX at Northeast UniversityRPKI Valid240c:c406::
- 240c:c410::/32AS24369CERNET2 IX at Northeast UniversityRPKI Valid240c:c410::
- 240c:c586::/32AS24372CERNET2 IX at Harbin Institute of TechnologyRPKI Valid240c:c586::
- 240c:c602::/32AS24361CERNET2 IX at Southeast UniversityRPKI Valid240c:c602::
- 240c:c603::/32AS24361CERNET2 IX at Southeast UniversityRPKI Valid240c:c603::
- 240c:c604::/32AS24361CERNET2 IX at Southeast UniversityRPKI Valid240c:c604::
- 240c:c608::/32AS24361CERNET2 IX at Southeast UniversityRPKI Valid240c:c608::
- 240c:c64c::/32AS24361CERNET2 IX at Southeast UniversityRPKI Valid240c:c64c::
- 240c:c651::/32AS24361CERNET2 IX at Southeast UniversityRPKI Not found240c:c651::
- 240c:c701::/32AS24365CERNET2 IX at Fudan UniversityRPKI Valid240c:c701::
- 240c:c702::/32AS24366CERNET2 IX at Tongji UniversityRPKI Valid240c:c702::
- 240c:c715::/32AS24364CERNET2 IX at Shanghai Jiaotong UniversityRPKI Valid240c:c715::
- 240c:c726::/32AS24364CERNET2 IX at Shanghai Jiaotong UniversityRPKI Valid240c:c726::
- 240c:c781::/32AS24367CERNET2 IX at Zhejiang UniversityRPKI Valid240c:c781::
- 240c:c783::/32AS24367CERNET2 IX at Zhejiang UniversityRPKI Valid240c:c783::
- 240c:c795::/32AS24367CERNET2 IX at Zhejiang UniversityRPKI Valid240c:c795::
- 240c:c7b9::/32AS24367CERNET2 IX at Zhejiang UniversityRPKI Valid240c:c7b9::
- 240c:c803::/32AS24362CERNET2 IX at University of Science and Technology of ChinaRPKI Valid240c:c803::
- 240c:c901::/32AS138370CERNET2 regional IX at Nanchang UniversityRPKI Valid240c:c901::
- 240c:c981::/32AS24355CERNET2 IX at University of Electronic Science and Technology of ChinaRPKI Valid240c:c981::
- 240c:c983::/32AS24355CERNET2 IX at University of Electronic Science and Technology of ChinaRPKI Valid240c:c983::
- 240c:c99d::/32AS24355CERNET2 IX at University of Electronic Science and Technology of ChinaRPKI Valid240c:c99d::
- 240c:ca02::/32AS138371CERNET2 regional IX at Ocean University of ChinaRPKI Valid240c:ca02::
- 240c:ca03::/32AS138371CERNET2 regional IX at Ocean University of ChinaRPKI Valid240c:ca03::
- 240c:ca05::/32AS138371CERNET2 regional IX at Ocean University of ChinaRPKI Valid240c:ca05::
- 240c:ca07::/32AS138371CERNET2 regional IX at Ocean University of ChinaRPKI Valid240c:ca07::
- 240c:ca09::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca09::
- 240c:ca0b::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca0b::
- 240c:ca0c::/32AS138371CERNET2 regional IX at Ocean University of ChinaRPKI Valid240c:ca0c::
- 240c:ca0d::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca0d::
- 240c:ca0e::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca0e::
- 240c:ca0f::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca0f::
- 240c:ca10::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca10::
- 240c:ca11::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca11::
- 240c:ca12::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca12::
- 240c:ca13::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca13::
- 240c:ca14::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca14::
- 240c:ca15::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca15::
- 240c:ca18::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca18::
- 240c:ca19::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca19::
- 240c:ca1b::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca1b::
- 240c:ca1d::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca1d::
- 240c:ca21::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca21::
- 240c:ca23::/32AS138371CERNET2 regional IX at Ocean University of ChinaRPKI Valid240c:ca23::
- 240c:ca28::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca28::
- 240c:ca29::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca29::
- 240c:ca30::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca30::
- 240c:ca38::/32AS24363CERNET2 IX at Shandong UniversityRPKI Not found240c:ca38::
- 240c:ca43::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca43::
- 240c:ca47::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca47::
- 240c:ca48::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca48::
- 240c:ca49::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca49::
- 240c:ca49:8000::/33AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:ca49:8000::
- 240c:caa1::/32AS24363CERNET2 IX at Shandong UniversityRPKI Valid240c:caa1::
- 240c:cb02::/32AS24360CERNET2 IX at Zhengzhou UniversityRPKI Valid240c:cb02::
- 240c:cb06::/32AS24360CERNET2 IX at Zhengzhou UniversityRPKI Valid240c:cb06::
- 240c:cb21::/32AS24360CERNET2 IX at Zhengzhou UniversityRPKI Valid240c:cb21::
- 240c:cb3a::/32AS24360CERNET2 IX at Zhengzhou UniversityRPKI Valid240c:cb3a::
- 240c:cc02::/32AS24358CERNET2 IX at Huazhong University of Science and TechnologyRPKI Valid240c:cc02::
- 240c:cd01:cd01::/48AS24357CERNET2 IX at South China University of TechnologyRPKI Valid240c:cd01:cd01::
- 240c:cd05:cd05::/48AS24357CERNET2 IX at South China University of TechnologyRPKI Valid240c:cd05:cd05::
- 240c:cd15:1000::/48AS24357CERNET2 IX at South China University of TechnologyRPKI Valid240c:cd15:1000::
- 240c:cd22::/32AS24357CERNET2 IX at South China University of TechnologyRPKI Valid240c:cd22::
- 240c:cd22:cd22::/48AS24357CERNET2 IX at South China University of TechnologyRPKI Valid240c:cd22:cd22::
- 240c:cd44::/32AS138369CERNET2 regional IX at Shenzhen UniversityRPKI Valid240c:cd44::
- 240c:cd45::/32AS24357CERNET2 IX at South China University of TechnologyRPKI Valid240c:cd45::
- 240c:cda1::/32AS24357CERNET2 IX at South China University of TechnologyRPKI Valid240c:cda1::
- 240c:cda3::/32AS138369CERNET2 regional IX at Shenzhen UniversityRPKI Valid240c:cda3::
- 240c:ce04::/32AS24359CERNET2 IX at Central South UniversityRPKI Valid240c:ce04::
- 240c:ce81::/32AS138393CERNET2 regional IX at Guangxi UniversityRPKI Valid240c:ce81::
- 240c:ce83::/32AS138438CERNET2 regional IX at Guangxi Normal UniversityRPKI Valid240c:ce83::
- 240c:ce84::/32AS138438CERNET2 regional IX at Guangxi Normal UniversityRPKI Valid240c:ce84::
Showing the first 100.
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.