Network · data from 2026-11-12

AS203833 firstcolo Austria

Registry name: AT-FIRSTCOLO firstcolo GmbH, DE · PeeringDB

7IPv4 routes 42.9% RPKI valid · 100.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

4No ROA 0 with no route object for this origin

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

3Route objects not announced registered with origin AS203833, seen from no peer

Announced routes

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


168.81.255.0/24	No ROA	Other IRR onlyRADB	666 99%	67
196.18.175.0/24	No ROA	Other IRR onlyRADB	666 99%	67
5.187.28.0/24	No ROA	RIR databaseRIPE	672 100%	67
109.169.80.0/24	No ROA	RIR databaseRIPE	672 100%	67
79.133.32.0/23	Valid	RIR databaseRIPE	672 100%	67
79.133.43.0/24	Valid	RIR databaseRIPE	672 100%	67
159.100.24.0/22	Valid	RIR databaseRIPE	672 100%	67
2a00:11c0:38::/48	Valid	RIR databaseRIPE	635 100%	67

AS-SET

AS203833'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 9 are in fix.csv.

ROA: none4
Route object: RIR2
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
ROA: none	168.81.255.0/24	No ROA covers it. Add a ROA for AS203833, maxLength 24.	666 of 673
Route object: RIR	168.81.255.0/24	Route object only in RADB. Add it in the RIR database for the space.	666 of 673
ROA: none	196.18.175.0/24	No ROA covers it. Add a ROA for AS203833, maxLength 24.	666 of 673
Route object: RIR	196.18.175.0/24	Route object only in RADB. Add it in the RIR database for the space.	666 of 673
ROA: none	5.187.28.0/24	No ROA covers it. Add a ROA for AS203833, maxLength 24.	672 of 673
ROA: none	109.169.80.0/24	No ROA covers it. Add a ROA for AS203833, maxLength 24.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

168.81.255.0/24

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

666 of 673

Route object: RIR

168.81.255.0/24

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

666 of 673

ROA: none

196.18.175.0/24

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

666 of 673

Route object: RIR

196.18.175.0/24

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

666 of 673

ROA: none

5.187.28.0/24

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

672 of 673

ROA: none

109.169.80.0/24

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

672 of 673

Route objects not announced

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


172.247.36.0/24	RIPE-NONAUTH	No ROA
185.171.204.0/22	RIPE	Invalid: origin
2a01:7e1::/32	RIPE	Valid

172.247.36.0/24

RIPE-NONAUTH

No ROA

185.171.204.0/22

RIPE

Invalid: origin

2a01:7e1::/32

RIPE

Valid

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.