Network · data from 2026-11-12

AS61307 AS STV

Registry name: EE-AS-STV AS STV, EE · PeeringDB

12IPv4 routes 100.0% RPKI valid · 33.3% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 8 with no route object for this origin

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

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

Announced routes

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


31.24.56.0/22	Valid	Nonecovered by 31.24.56.0/21	673 100%	67
31.24.60.0/22	Valid	Nonecovered by 31.24.56.0/21	673 100%	67
85.196.192.0/19	Valid	Nonecovered by 85.196.192.0/18	673 100%	67
85.196.224.0/19	Valid	Nonecovered by 85.196.192.0/18	673 100%	67
185.97.248.0/23	Valid	Nonecovered by 185.97.248.0/22	673 100%	67
185.97.250.0/23	Valid	Nonecovered by 185.97.248.0/22	673 100%	67
93.185.240.0/21	Valid	Nonecovered by 93.185.240.0/20	672 100%	67
93.185.248.0/21	Valid	Nonecovered by 93.185.240.0/20	672 100%	67
31.24.56.0/21	Valid	RIR databaseRIPE	673 100%	67
85.196.192.0/18	Valid	RIR databaseRIPE	673 100%	67
93.185.240.0/20	Valid	RIR databaseRIPE	673 100%	67
185.97.248.0/22	Valid	RIR databaseRIPE	673 100%	67
2a03:4360::/32	Valid	RIR databaseRIPE	636 100%	67

AS-SET

AS61307'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 8 are in fix.csv.

Route object: none8

Change	Prefix or set	Detail	Full-table peers
Route object: none	31.24.56.0/22	No route object for it. A route object for 31.24.56.0/21 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.	673 of 673
Route object: none	31.24.60.0/22	No route object for it. A route object for 31.24.56.0/21 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.	673 of 673
Route object: none	85.196.192.0/19	No route object for it. A route object for 85.196.192.0/18 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.	673 of 673
Route object: none	85.196.224.0/19	No route object for it. A route object for 85.196.192.0/18 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.	673 of 673
Route object: none	185.97.248.0/23	No route object for it. A route object for 185.97.248.0/22 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.	673 of 673
Route object: none	185.97.250.0/23	No route object for it. A route object for 185.97.248.0/22 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.	673 of 673
Route object: none	93.185.240.0/21	No route object for it. A route object for 93.185.240.0/20 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.	672 of 673
Route object: none	93.185.248.0/21	No route object for it. A route object for 93.185.240.0/20 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

31.24.56.0/22

No route object for it. A route object for 31.24.56.0/21 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.

673 of 673

Route object: none

31.24.60.0/22

673 of 673

Route object: none

85.196.192.0/19

No route object for it. A route object for 85.196.192.0/18 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.

673 of 673

Route object: none

85.196.224.0/19

673 of 673

Route object: none

185.97.248.0/23

No route object for it. A route object for 185.97.248.0/22 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.

673 of 673

Route object: none

185.97.250.0/23

673 of 673

Route object: none

93.185.240.0/21

No route object for it. A route object for 93.185.240.0/20 with origin AS61307 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61307 in the RIR database for the space.

672 of 673

Route object: none

93.185.248.0/21

672 of 673

Route objects not announced

Every route object with origin AS61307 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.