bgpreport

Network · data from 2026-11-12

AS146950 Haruue Network Limited

Registry name: HARUUE-AS-AP - Haruue Network Limited, HK · PeeringDB

0IPv4 routes
11IPv6 routes 45.5% RPKI valid · 90.9% with a route object
3RPKI invalid 3 origin · 0 maxLength
3No ROA 1 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS146950, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS146950, 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.

2a0a:6040:2d10::/44 Invalid: origin RIR databaseRIPE 15 2%low visibility 11
2a0a:6040:2d10::/45 Invalid: origin RIR databaseRIPE 15 2%low visibility 11
2a0a:6040:2d18::/45 Invalid: origin RIR databaseRIPE 15 2%low visibility 11
2406:4440:a0::/45 No ROA Other IRR onlyALTDB 635 100% 68
2406:4440:a8::/45 No ROA Other IRR onlyALTDB 634 100% 68
2406:4440:a0::/44 No ROA RIR databaseALTDB, APNIC, RADB 633 100% 68
2602:feda:b68::/48 Valid Nonecovered by 2602:feda:b60::/44 634 100% 68
2602:feda:b60::/48 Valid Other IRR onlyALTDB 635 100% 68
2602:feda:b61::/48 Valid Other IRR onlyALTDB 635 100% 68
2602:feda:b62::/48 Valid Other IRR onlyALTDB 634 100% 68
2602:feda:b60::/44 Valid Other IRR onlyALTDB, RADB 633 100% 68

AS-SET

PeeringDB's irr_as_set for AS146950: AS146950:AS-ALL. 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 (AS146950 isn't in the set, or no route object for AS146950 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 objectsAS146950 in itNot covered
AS146950:AS-ALL ALTDB 4238 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 20 are in fix.csv.

  • ROA: origin3
  • ROA: none3
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin2a0a:6040:2d10::/44ROAs covering it name AS200256, not AS146950. If AS146950 should announce it, add a ROA for AS146950.15 of 636
ROA: origin2a0a:6040:2d10::/45ROAs covering it name AS200256, not AS146950. If AS146950 should announce it, add a ROA for AS146950.15 of 636
ROA: origin2a0a:6040:2d18::/45ROAs covering it name AS200256, not AS146950. If AS146950 should announce it, add a ROA for AS146950.15 of 636
ROA: none2406:4440:a0::/45No ROA covers it. Add a ROA for AS146950, maxLength 45.635 of 636
Route object: RIR2406:4440:a0::/45Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
ROA: none2406:4440:a8::/45No ROA covers it. Add a ROA for AS146950, maxLength 45.634 of 636
Route object: RIR2406:4440:a8::/45Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
ROA: none2406:4440:a0::/44No ROA covers it. Add a ROA for AS146950, maxLength 44.633 of 636
Route object: none2602:feda:b68::/48No route object for it. A route object for 2602:feda:b60::/44 with origin AS146950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS146950 in the RIR database for the space.634 of 636
Route object: RIR2602:feda:b60::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2602:feda:b61::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2602:feda:b62::/48Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:feda:b60::/44Route object only in ALTDB, RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

2602:feda:b64::/48ALTDBValid
2602:feda:b65::/48ALTDBValid
2602:feda:b66::/48ALTDBValid
2602:feda:b67::/48ALTDB, RADBValid
2602:feda:b69::/48ALTDBValid
2a0a:6040:2d00::/44RIPEInvalid: origin
2a0a:6040:2d0f::/48RIPEInvalid: origin

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.