bgpreport

Network · data from 2026-11-12

AS199727 asten-cloud-idf ASTEN CLOUD SAS

Registry name: asten-cloud-idf ASTEN CLOUD SAS, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199727, 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.
2a04:1170::/31 Valid None 604 95% 67
185.37.41.0/24 Valid RIR databaseRIPE 673 100% 67
185.37.42.0/24 Valid RIR databaseRIPE 673 100% 67
185.37.43.0/24 Valid RIR databaseRIPE 673 100% 67
185.189.172.0/24 Valid RIR databaseRIPE 673 100% 67
185.189.173.0/24 Valid RIR databaseRIPE 673 100% 67
185.189.174.0/24 Valid RIR databaseRIPE 673 100% 67
185.189.175.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2a04:1170::/31No route object for it. Add a route object with origin AS199727 in the RIR database for the space.604 of 636

Route objects not announced

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