Network · data from 2026-11-12

AS39900 GOODTEC SIA GOOD

Registry name: GOODTEC SIA GOOD, LV · not in PeeringDB

9IPv4 routes 100.0% 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

0No 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 AS39900, seen from no peer

Announced routes

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


95.164.91.0/24	Valid	RIR databaseRIPE	673 100%	67
138.249.142.0/23	Valid	RIR databaseRIPE	673 100%	67
141.98.184.0/22	Valid	RIR databaseRIPE	673 100%	67
193.124.254.0/24	Valid	RIR databaseRIPE	673 100%	67
194.9.118.0/24	Valid	RIR databaseRIPE	673 100%	67
45.15.67.0/24	Valid	RIR databaseRIPE	672 100%	67
72.56.52.0/24	Valid	RIR databaseRIPE	672 100%	67
72.56.53.0/24	Valid	RIR databaseRIPE	672 100%	67
77.90.46.0/24	Valid	RIR databaseRIPE	672 100%	67
2a0b:88c0:48::/48	Valid	RIR databaseRIPE	636 100%	67
2a12:b2c0:6::/48	Valid	RIR databaseRIPE	634 100%	67
2a13:6c40::/29	Valid	RIR databaseRIPE	633 100%	67

AS-SET

AS39900 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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