bgpreport

Network · data from 2026-11-12

AS20571 EXOMI Exomi Oy

Registry name: EXOMI Exomi Oy, FI · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20571, 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.
217.169.70.0/24 Valid Other origin onlycovered by 217.169.64.0/21 673 100% 66
217.169.76.0/22 Valid Other origin onlycovered by 217.169.64.0/20 673 100% 66
217.169.64.0/22 Valid RIR databaseRIPE 673 100% 66
2a0a:b7c0::/32 Valid RIR databaseRIPE 635 100% 67
217.169.65.0/24 Valid RIR databaseRIPE 219 33% 56

AS-SET

AS20571 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.

  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none217.169.70.0/24Route objects for it name AS45010. A route object for 217.169.64.0/21 with origin AS20571 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20571 in the RIR database for the space.673 of 673
Route object: none217.169.76.0/22Route objects for it name AS45010. A route object for 217.169.64.0/20 with origin AS20571 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20571 in the RIR database for the space.673 of 673

Route objects not announced

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

217.169.64.0/20RIPEValid
217.169.64.0/21RIPEValid
217.169.64.0/24RIPEValid
217.169.66.0/24RIPEValid

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.