bgpreport

Network · data from 2026-11-12

AS275 NTTA-275 - NTT America, Inc.

Registry name: NTTA-275 - NTT America, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS275, 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.
2001:418:1401:ae::/64 Valid None 42 7%low visibility 27
2001:728:0:7000::/64 Valid None 42 7%low visibility 27
2001:728:401:21::/64 Valid None 42 7%low visibility 27
2001:728:0:5000::1532/127 Valid None 34 5%low visibility 23
129.250.35.16/28 Valid None 28 4%low visibility 22
185.84.19.224/27 Valid None 28 4%low visibility 22
213.130.47.16/28 Valid None 28 4%low visibility 22
5.158.213.64/31 Valid None 18 3%low visibility 15
204.141.84.0/22 Valid Other IRR onlyNTTCOM 673 100% 67
2001:418:144d::/48 Valid Other IRR onlyNTTCOM 635 100% 67

AS-SET

AS275 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 10 are in fix.csv.

  • Route object: none8
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none2001:418:1401:ae::/64No route object for it. Add a route object with origin AS275 in the RIR database for the space.42 of 636
Route object: none2001:728:0:7000::/64No route object for it. Add a route object with origin AS275 in the RIR database for the space.42 of 636
Route object: none2001:728:401:21::/64No route object for it. Add a route object with origin AS275 in the RIR database for the space.42 of 636
Route object: none2001:728:0:5000::1532/127No route object for it. Add a route object with origin AS275 in the RIR database for the space.34 of 636
Route object: none129.250.35.16/28No route object for it. Add a route object with origin AS275 in the RIR database for the space.28 of 673
Route object: none185.84.19.224/27No route object for it. Add a route object with origin AS275 in the RIR database for the space.28 of 673
Route object: none213.130.47.16/28No route object for it. Add a route object with origin AS275 in the RIR database for the space.28 of 673
Route object: none5.158.213.64/31No route object for it. Add a route object with origin AS275 in the RIR database for the space.18 of 673
Route object: RIR204.141.84.0/22Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR2001:418:144d::/48Route object only in NTTCOM. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS275 is announced.

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.