bgpreport

Network · data from 2026-11-12

AS54720 CLOUDKEY - Global IP Networks INC

Registry name: CLOUDKEY - Global IP Networks INC, US · not in PeeringDB

8IPv4 routes 87.5% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS54720, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS54720, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
198.22.145.0/24 No ROA Other IRR onlyNTTCOM 670 100% 67
66.180.39.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
66.180.42.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
66.180.41.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
66.180.36.0/24 Valid Other IRR onlyNTTCOM 670 100% 67
66.180.38.0/24 Valid Other IRR onlyNTTCOM 670 100% 67
66.180.40.0/24 Valid Other IRR onlyNTTCOM 670 100% 67
66.180.40.0/22 Valid RIR databaseARIN, NTTCOM 672 100% 67

AS-SET

AS54720 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 11 are in fix.csv.

  • ROA: none1
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none198.22.145.0/24No ROA covers it. Add a ROA for AS54720, maxLength 24.670 of 673
Route object: RIR198.22.145.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
Route object: RIR66.180.39.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR66.180.42.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR66.180.41.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR66.180.36.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
Route object: RIR66.180.38.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
Route object: RIR66.180.40.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS54720 whose prefix no peer sees AS54720 announce. Many are kept on purpose (backup routes, space announced only in some places).

66.180.36.0/22ARINValid
66.180.36.0/23NTTCOMValid
66.180.43.0/24NTTCOMValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.