bgpreport

Network · data from 2026-11-12

AS58003 Planeetta Internet

Registry name: PLANEETTA-AS Planeetta Internet Oy, FI · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58003, 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.217.192.0/21 No ROA RIR databaseRIPE 673 100% 66
37.233.88.0/21 No ROA RIR databaseRIPE 673 100% 66
79.171.232.0/21 No ROA RIR databaseRIPE 673 100% 66
84.234.64.0/20 No ROA RIR databaseRIPE 673 100% 66
91.224.88.0/23 No ROA RIR databaseRIPE 673 100% 66
94.199.56.0/21 No ROA RIR databaseRIPE 673 100% 66
185.28.244.0/22 No ROA RIR databaseRIPE 673 100% 66
185.179.116.0/22 No ROA RIR databaseRIPE 673 100% 66
185.163.152.0/22 No ROA RIR databaseRIPE 669 99% 67
91.223.27.0/24 No ROA RIR databaseRIPE 668 99% 67
2a00:9560::/29 No ROA RIR databaseRIPE 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS58003: AS58003:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS58003 isn't in the set, or no route object for AS58003 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS58003 in itNot covered
AS58003:AS-ALL RIPE 5129 Yes 0

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

  • ROA: none11
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none31.217.192.0/21No ROA covers it. Add a ROA for AS58003, maxLength 21.673 of 673
ROA: none37.233.88.0/21No ROA covers it. Add a ROA for AS58003, maxLength 21.673 of 673
ROA: none79.171.232.0/21No ROA covers it. Add a ROA for AS58003, maxLength 21.673 of 673
ROA: none84.234.64.0/20No ROA covers it. Add a ROA for AS58003, maxLength 20.673 of 673
ROA: none91.224.88.0/23No ROA covers it. Add a ROA for AS58003, maxLength 23.673 of 673
ROA: none94.199.56.0/21No ROA covers it. Add a ROA for AS58003, maxLength 21.673 of 673
ROA: none185.28.244.0/22No ROA covers it. Add a ROA for AS58003, maxLength 22.673 of 673
ROA: none185.179.116.0/22No ROA covers it. Add a ROA for AS58003, maxLength 22.673 of 673
ROA: none185.163.152.0/22No ROA covers it. Add a ROA for AS58003, maxLength 22.669 of 673
ROA: none91.223.27.0/24No ROA covers it. Add a ROA for AS58003, maxLength 24.668 of 673
ROA: none2a00:9560::/29No ROA covers it. Add a ROA for AS58003, maxLength 29.632 of 636

Route objects not announced

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

109.106.8.0/22RIPENo ROA
2a00:9560::/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.