bgpreport

Network · data from 2026-11-12

AS213471 IPPNOC

Registry name: IPPNOC YAMAMOTO Hiroshi, JP · PeeringDB

0IPv4 routes
8IPv6 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
3Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS213471, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213471, 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.
2a06:41:10::/44 Valid RIR databaseRIPE 636 100% 67
2a06:41::/44 Valid RIR databaseRIPE 635 100% 69
2a06:41:20::/44 Valid RIR databaseRIPE 635 100% 69
2a06:41:70::/44 Valid RIR databaseRIPE 633 100% 69
2a0b:4e07:d7::/48 Valid RIR databaseRIPE 633 100% 69
2602:f2dc:95::/48 Valid RIR databaseARIN 2 0%low visibility 2
2a06:41:80::/42 Valid RIR databaseRIPE 2 0%low visibility 2
2a06:41:60::/44 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS213471'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 10 are in fix.csv.

  • Route object: not announced10

Route objects not announced

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

2a06:41::/40RIPEValid
2a06:41:30::/44RIPEValid
2a06:41:40::/44RIPEValid
2a06:41:50::/44RIPEValid
2a06:41:80::/41RIPEValid
2a06:41:c0::/44RIPEValid
2a0b:4e07:d4::/46RIPENo ROA
2a0b:4e07:d4::/48RIPEInvalid: origin
2a0b:4e07:d5::/48RIPENo ROA
2a0b:4e07:d6::/48RIPEValid

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.