bgpreport

Network · data from 2026-11-12

AS9997 Suzuka Cable Co.

Registry name: MECHA - Suzuka Cable Co.,Ltd, JP · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS9997, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9997, 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.
61.120.128.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
61.206.240.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
123.242.232.0/21 Valid Other IRR onlyJPIRR, RADB 671 100% 67
133.226.96.0/19 Valid Other IRR onlyJPIRR 671 100% 67
202.211.80.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
203.171.8.0/21 Valid Other IRR onlyJPIRR, RADB 671 100% 67
220.219.0.0/16 Valid Other IRR onlyJPIRR 671 100% 67
218.226.0.0/16 Valid Other IRR onlyJPIRR 670 100% 67
103.2.36.0/22 Valid Other IRR onlyJPIRR, NTTCOM, RADB 669 99% 67
219.100.40.0/22 Valid Other IRR onlyJPIRR 669 99% 67
2402:700::/32 Valid Other IRR onlyJPIRR, RADB 635 100% 69

AS-SET

AS9997'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 11 are in fix.csv.

  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
Route object: RIR61.120.128.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR61.206.240.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR123.242.232.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR133.226.96.0/19Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR202.211.80.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.171.8.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR220.219.0.0/16Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR218.226.0.0/16Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
Route object: RIR103.2.36.0/22Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR219.100.40.0/22Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
Route object: RIR2402:700::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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