bgpreport

Network · data from 2026-11-12

AS41369 DATACENTER-AS Advania Finland Oy

Registry name: DATACENTER-AS Advania Finland Oy, FI · not in PeeringDB

17IPv4 routes 88.2% RPKI valid · 100.0% with a route object
3IPv6 routes 66.7% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
2No 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 AS41369, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41369, 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.
2a06:f800::/29 Invalid: origin RIR databaseRIPE 100 16% 38
91.213.97.0/24 No ROA RIR databaseRIPE 671 100% 66
185.136.20.0/22 No ROA RIR databaseRIPE 671 100% 66
185.87.244.0/24 Valid RIR databaseRIPE 673 100% 70
80.242.25.0/24 Valid RIR databaseRIPE 672 100% 70
80.242.30.0/24 Valid RIR databaseRIPE 672 100% 70
93.191.120.0/21 Valid RIR databaseRIPE 672 100% 66
185.87.244.0/22 Valid RIR databaseRIPE 672 100% 66
5.250.160.0/21 Valid RIR databaseRIPE 671 100% 66
77.240.16.0/23 Valid RIR databaseRIPE 671 100% 66
77.240.24.0/21 Valid RIR databaseRIPE 671 100% 66
79.171.224.0/21 Valid RIR databaseRIPE 671 100% 66
80.242.16.0/20 Valid RIR databaseRIPE 671 100% 66
89.250.48.0/20 Valid RIR databaseRIPE 671 100% 66
94.199.112.0/21 Valid RIR databaseRIPE 671 100% 66
185.145.172.0/22 Valid RIR databaseRIPE 671 100% 66
194.48.220.0/22 Valid RIR databaseRIPE 671 100% 66
195.60.252.0/22 Valid RIR databaseRIPE 671 100% 66
2a00:f5c0::/32 Valid RIR databaseRIPE 633 100% 67
2a0c:c6c0::/29 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS41369 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 6 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin2a06:f800::/29ROAs covering it name AS56334, not AS41369. If AS41369 should announce it, add a ROA for AS41369.100 of 636
ROA: none91.213.97.0/24No ROA covers it. Add a ROA for AS41369, maxLength 24.671 of 673
ROA: none185.136.20.0/22No ROA covers it. Add a ROA for AS41369, maxLength 22.671 of 673

Route objects not announced

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

77.240.18.0/23RIPENo ROA
77.240.20.0/22RIPENo ROA
2a01:60c0::/32RIPENo ROA

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.