bgpreport

Network · data from 2026-11-12

AS202246 Valoo Oy

Registry name: valoo Valoo Oy, FI · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202246, 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.
109.68.135.0/24 Invalid: maxLength Nonecovered by 109.68.128.0/21 5 1%low visibility 5
109.204.188.0/23 Valid Nonecovered by 109.204.176.0/20 225 33% 56
185.25.200.0/22 Valid RIR databaseRIPE 673 100% 66
109.68.128.0/21 Valid RIR databaseRIPE 672 100% 67
109.204.176.0/20 Valid RIR databaseRIPE 672 100% 67
171.22.241.0/24 Valid RIR databaseRIPE 672 100% 67
178.22.16.0/21 Valid RIR databaseRIPE 672 100% 67
185.128.16.0/22 Valid RIR databaseRIPE 672 100% 67
2a10:a5c0::/32 Valid RIR databaseRIPE 633 100% 67
2a10:a5c1::/32 Valid RIR databaseRIPE 633 100% 67
2a10:a5c2::/32 Valid RIR databaseRIPE 633 100% 67
2a10:a5c3::/32 Valid RIR databaseRIPE 633 100% 67
2a10:a5c4::/32 Valid RIR databaseRIPE 633 100% 67
2a10:a5c5::/32 Valid RIR databaseRIPE 633 100% 67
2a10:a5c6::/32 Valid RIR databaseRIPE 633 100% 67
2a10:a5c7::/32 Valid RIR databaseRIPE 633 100% 67
2a10:a5c0::/29 Valid RIR databaseRIPE 632 99% 67
2a10:a5c0::/36 Valid RIR databaseRIPE 337 53% 63
2a10:a5c0:1000::/36 Valid RIR databaseRIPE 337 53% 63
2a10:a5c0:4000::/36 Valid RIR databaseRIPE 337 53% 63
2a10:a5c0:5000::/36 Valid RIR databaseRIPE 337 53% 63
2a10:a5c0:c000::/36 Valid RIR databaseRIPE 333 52% 63
2a10:a5c0:8000::/36 Valid RIR databaseRIPE 332 52% 63
2a10:a5c0:9000::/36 Valid RIR databaseRIPE 332 52% 63
2a10:a5c0:d000::/36 Valid RIR databaseRIPE 332 52% 63
109.204.176.0/22 Valid RIR databaseRIPE 225 33% 56
109.204.180.0/23 Valid RIR databaseRIPE 225 33% 56
109.204.184.0/22 Valid RIR databaseRIPE 225 33% 56

AS-SET

PeeringDB's irr_as_set for AS202246: AS202246:AS-VALOO. 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 (AS202246 isn't in the set, or no route object for AS202246 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 objectsAS202246 in itNot covered
AS202246:AS-VALOO RIPE 4434 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 3 are in fix.csv.

  • ROA: maxLength1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: maxLength109.68.135.0/24ROA 109.68.128.0/21 AS202246 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 109.68.135.0/24.5 of 673
Route object: none109.68.135.0/24No route object for it. A route object for 109.68.128.0/21 with origin AS202246 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202246 in the RIR database for the space.5 of 673
Route object: none109.204.188.0/23No route object for it. A route object for 109.204.176.0/20 with origin AS202246 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202246 in the RIR database for the space.225 of 673

Route objects not announced

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