Network · data from 2026-11-12

AS34019 Hivane

Registry name: HIVANE Hivane Association, FR · PeeringDB

6IPv4 routes 66.7% RPKI valid · 100.0% with a route object

3IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

2No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS34019, seen from no peer

Announced routes

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


44.31.71.0/24	No ROA	Other IRR onlyALTDB, RADB	673 100%	66
44.31.102.0/24	No ROA	Other IRR onlyALTDB, RADB	673 100%	66
193.17.192.0/24	Valid	RIR databaseRIPE	672 100%	66
193.106.116.0/22	Valid	RIR databaseRIPE	672 100%	66
193.164.153.0/24	Valid	RIR databaseRIPE	672 100%	66
193.200.42.0/23	Valid	RIR databaseRIPE	672 100%	66
2001:67c:1740::/48	Valid	RIR databaseRIPE	634 100%	67
2001:7a8:800::/47	Valid	RIR databaseRIPE	634 100%	67
2001:7a8:810::/44	Valid	RIR databaseRIPE	634 100%	67

AS-SET

PeeringDB's irr_as_set for AS34019: RIPE::AS34019:AS-HIVANE. 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 (AS34019 isn't in the set, or no route object for AS34019 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.

Name	Database	ASNs	Sets	Route objects	AS34019 in it	Not covered
RIPE::AS34019:AS-HIVANE	RIPElists itself further down	58	32	305	Yes	0

Name

Database

ASNs

Sets

Route objects

AS34019 in it

Not covered

RIPE::AS34019:AS-HIVANE

RIPElists itself further down

305

Yes

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.

ROA: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	44.31.71.0/24	No ROA covers it. Add a ROA for AS34019, maxLength 24.	673 of 673
Route object: RIR	44.31.71.0/24	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	44.31.102.0/24	No ROA covers it. Add a ROA for AS34019, maxLength 24.	673 of 673
Route object: RIR	44.31.102.0/24	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

44.31.71.0/24

No ROA covers it. Add a ROA for AS34019, maxLength 24.

673 of 673

Route object: RIR

44.31.71.0/24

Route object only in ALTDB, RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

44.31.102.0/24

No ROA covers it. Add a ROA for AS34019, maxLength 24.

673 of 673

Route object: RIR

44.31.102.0/24

Route object only in ALTDB, RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

Every route object with origin AS34019 is announced.

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.