bgpreport

Network · data from 2026-11-12

AS14427 RagingWire HI Internet Connect - NTT

Registry name: NTT-GLOBAL-DATA-CENTERS-AMERICA-INC - NTT Global Data Centers Americas, INC., US · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
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
1Route objects not announced registered with origin AS14427, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS14427, 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.
2606:9500:3000::/36 No ROA Other IRR onlyRADB 636 100% 67
208.185.76.0/24 Valid Other IRR onlyRADB 673 100% 67
2001:438:7d::/48 Valid Other IRR onlyRADB 636 100% 67

AS-SET

AS14427's PeeringDB record names no 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 5 are in fix.csv.

  • ROA: none1
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2606:9500:3000::/36No ROA covers it. Add a ROA for AS14427, maxLength 36.636 of 636
Route object: RIR2606:9500:3000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR208.185.76.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2001:438:7d::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

8.41.131.0/24RADBNo ROA

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.