bgpreport

Network · data from 2026-11-12

AS197860 Haruka Network

Registry name: NET-HARUKA Haruka Network Limited, GB · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
8IPv6 routes 100.0% RPKI valid · 75.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS197860, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS197860, 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.
2a12:bec0:390::/48 Valid Nonecovered by 2a12:bec0:390::/44 633 100% 67
2a12:bec4:1010::/48 Valid Nonecovered by 2a12:bec4:1010::/44 633 100% 67
109.105.193.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.38.223.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
74.2.4.0/24 Valid RIR databaseARIN, RADB 671 100% 68
103.76.86.0/24 Valid RIR databaseRIPE 665 99% 67
2a12:bec4:2020::/48 Valid RIR databaseRIPE 636 100% 69
2a12:bec4:2023::/48 Valid RIR databaseRIPE 636 100% 69
2a12:bec4:2024::/48 Valid RIR databaseRIPE 635 100% 69
2a12:bec0:390::/44 Valid RIR databaseRIPE 633 100% 67
2a12:bec4:1010::/44 Valid RIR databaseRIPE 633 100% 67
2a12:bec4:2021::/48 Valid RIR databaseRIPE 330 52% 63

AS-SET

PeeringDB's irr_as_set for AS197860: AS197860:AS-HARUKA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS197860 isn't in the set, or no route object for AS197860 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS197860 in itNot covered
AS197860:AS-HARUKA RIPE 3498 Yes 0

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

  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2a12:bec0:390::/48No route object for it. A route object for 2a12:bec0:390::/44 with origin AS197860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197860 in the RIR database for the space.633 of 636
Route object: none2a12:bec4:1010::/48No route object for it. A route object for 2a12:bec4:1010::/44 with origin AS197860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197860 in the RIR database for the space.633 of 636

Route objects not announced

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

2a0c:9a40:95d0::/44RIPEInvalid: origin
2a12:bec4:2020::/44RIPEValid

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.