bgpreport

Network · data from 2026-11-12

AS38462 OCE-AS-AP - Osaki Computer Engineering Co.Ltd

Registry name: OCE-AS-AP - Osaki Computer Engineering Co.Ltd, JP · not in PeeringDB

6IPv4 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
1Route objects not announced registered with origin AS38462, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38462, 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.
113.130.0.0/18 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
116.214.80.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
119.82.16.0/21 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
120.50.208.0/20 Valid RIR databaseAPNIC, RADB 672 100% 67
120.143.64.0/19 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
203.86.248.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
2405:8000::/32 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS38462 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 1 are in fix.csv.

  • Route object: not announced1

Route objects not announced

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

49.156.176.0/20NTTCOMNo 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.