bgpreport

Network · data from 2026-11-12

AS205250 TURUNKAUPUNKI Turun Kaupunki

Registry name: TURUNKAUPUNKI Turun Kaupunki, FI · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205250, 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.
185.224.72.0/23 Valid None 673 100% 67
185.224.74.0/23 Valid RIR databaseRIPE 673 100% 67
192.103.86.0/24 Valid RIR databaseRIPE 673 100% 67
192.103.91.0/24 Valid RIR databaseRIPE 673 100% 67
192.103.92.0/24 Valid RIR databaseRIPE 673 100% 67
192.103.105.0/24 Valid RIR databaseRIPE 673 100% 67
192.103.106.0/24 Valid RIR databaseRIPE 673 100% 67
192.103.110.0/24 Valid RIR databaseRIPE 673 100% 67
192.103.111.0/24 Valid RIR databaseRIPE 673 100% 67
192.103.116.0/24 Valid RIR databaseRIPE 673 100% 67
2a0c:fc00::/32 Valid RIR databaseRIPE 635 100% 67
2a0c:fc01::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS205250 isn't in PeeringDB, where networks name their 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none185.224.72.0/23No route object for it. Add a route object with origin AS205250 in the RIR database for the space.673 of 673

Route objects not announced

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