bgpreport

Network · data from 2026-11-12

AS9999 AT TOKYO Corporation

Registry name: ATTOKYO - AT TOKYO Corporation, JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9999, 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.
202.243.223.0/24 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
203.80.6.0/23 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
2405:1800::/32 No ROA Other IRR onlyJPIRR, RADB 636 100% 68
110.44.20.0/22 Valid Other IRR onlyJPIRR, RADB 672 100% 67
119.59.64.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
165.100.192.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
202.13.124.0/22 Valid Other IRR onlyJPIRR, RADB 672 100% 67
203.89.128.0/22 Valid Other IRR onlyJPIRR, RADB 672 100% 67
203.223.24.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
211.132.0.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
219.99.128.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67

AS-SET

AS9999'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 14 are in fix.csv.

  • ROA: none3
  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
ROA: none202.243.223.0/24No ROA covers it. Add a ROA for AS9999, maxLength 24.673 of 673
Route object: RIR202.243.223.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.80.6.0/23No ROA covers it. Add a ROA for AS9999, maxLength 23.673 of 673
Route object: RIR203.80.6.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none2405:1800::/32No ROA covers it. Add a ROA for AS9999, maxLength 32.636 of 636
Route object: RIR2405:1800::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR110.44.20.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR119.59.64.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR165.100.192.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.13.124.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.89.128.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.223.24.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR211.132.0.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.99.128.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS9999 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.