bgpreport

Network · data from 2026-11-12

AS205862 federal-service-arkea FEDERAL SERVICE GIE

Registry name: federal-service-arkea FEDERAL SERVICE GIE, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205862, 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.204.41.0/24 Valid None 673 100% 67
185.204.43.0/24 Valid None 673 100% 67
2a0d:b00:3501::/48 Valid None 632 99% 67
2a0d:b00:9201::/48 Valid None 632 99% 67
2a0d:b00:3502::/48 Valid None 629 99% 67
2a0d:b00:2901::/48 Valid None 3 0%low visibility 3
185.204.40.0/24 Valid RIR databaseRIPE 672 100% 67
185.204.42.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS205862 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: none6
ChangePrefix or setDetailFull-table peers
Route object: none185.204.41.0/24No route object for it. Add a route object with origin AS205862 in the RIR database for the space.673 of 673
Route object: none185.204.43.0/24No route object for it. Add a route object with origin AS205862 in the RIR database for the space.673 of 673
Route object: none2a0d:b00:3501::/48No route object for it. Add a route object with origin AS205862 in the RIR database for the space.632 of 636
Route object: none2a0d:b00:9201::/48No route object for it. Add a route object with origin AS205862 in the RIR database for the space.632 of 636
Route object: none2a0d:b00:3502::/48No route object for it. Add a route object with origin AS205862 in the RIR database for the space.629 of 636
Route object: none2a0d:b00:2901::/48No route object for it. Add a route object with origin AS205862 in the RIR database for the space.3 of 636

Route objects not announced

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