bgpreport

Network · data from 2026-11-12

AS201939 Koesio Corporate Technologies

Registry name: DSMI Heliaq SAS, FR · PeeringDB

5IPv4 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
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS201939, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201939, 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.57.52.0/22 No ROA RIR databaseRIPE 671 100% 66
185.57.52.0/24 No ROA RIR databaseRIPE 671 100% 67
185.57.53.0/24 No ROA RIR databaseRIPE 671 100% 67
185.57.54.0/24 No ROA RIR databaseRIPE 671 100% 67
185.57.55.0/24 No ROA RIR databaseRIPE 671 100% 67
2a02:5820::/32 No ROA RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS201939: AS-DSMI. 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 (AS201939 isn't in the set, or no route object for AS201939 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 objectsAS201939 in itNot covered
AS-DSMI RIPE 116 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 6 are in fix.csv.

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none185.57.52.0/22No ROA covers it. Add a ROA for AS201939, maxLength 22.671 of 673
ROA: none185.57.52.0/24No ROA covers it. Add a ROA for AS201939, maxLength 24.671 of 673
ROA: none185.57.53.0/24No ROA covers it. Add a ROA for AS201939, maxLength 24.671 of 673
ROA: none185.57.54.0/24No ROA covers it. Add a ROA for AS201939, maxLength 24.671 of 673
ROA: none185.57.55.0/24No ROA covers it. Add a ROA for AS201939, maxLength 24.671 of 673
ROA: none2a02:5820::/32No ROA covers it. Add a ROA for AS201939, maxLength 32.634 of 636

Route objects not announced

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