bgpreport

Network · data from 2026-11-12

AS55895 echigo-IX - N.S.Computer Service Co.,Ltd.

Registry name: echigo-IX - N.S.Computer Service Co.,Ltd., JP · not in PeeringDB

1IPv4 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 AS55895, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55895, 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.
117.102.169.0/24 Valid Other IRR onlyJPIRR, NTTCOM, RADB 669 99% 67
2400:e000:105::/48 Valid Other IRR onlyJPIRR, NTTCOM, RADB 633 100% 70

AS-SET

AS55895 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 2 are in fix.csv.

  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: RIR117.102.169.0/24Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2400:e000:105::/48Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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