bgpreport

Network · data from 2026-11-12

AS25618 SHINE - SHINESHAN

Registry name: SHINE - SHINESHAN, US · not in PeeringDB

2IPv4 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
5Route objects not announced registered with origin AS25618, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25618, 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.
23.144.164.0/24 Valid RIR databaseARIN, NTTCOM, RADB 673 100% 67
23.147.28.0/24 Valid RIR databaseARIN 673 100% 67
2602:f585::/40 Valid RIR databaseARIN, NTTCOM, RADB 635 100% 68

AS-SET

AS25618 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 5 are in fix.csv.

  • Route object: not announced5

Route objects not announced

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

23.162.124.0/24ARINValid
23.162.156.0/24ARINValid
204.126.126.0/23NTTCOMNo ROA
204.126.126.0/24NTTCOMNo ROA
204.126.127.0/24NTTCOMNo 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.