bgpreport

Network · data from 2026-11-12

AS204818 HOSTEUR

Registry name: HOSTEUR-NET-CORE Hosteur SAS, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204818, 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.

45.92.108.0/22 No ROA RIR databaseRIPE 673 100% 66
185.245.92.0/23 No ROA RIR databaseRIPE 673 100% 66
185.245.94.0/23 No ROA RIR databaseRIPE 673 100% 66
194.88.246.0/23 No ROA RIR databaseRIPE 673 100% 66
213.134.14.0/24 No ROA RIR databaseRIPE 673 100% 67
81.161.58.0/24 No ROA RIR databaseRIPE 672 100% 66
2a0d:5380::/29 No ROA RIR databaseRIPE 633 100% 70
46.182.4.0/22 Valid RIR databaseRIPE 673 100% 66
185.148.76.0/24 Valid RIR databaseRIPE 673 100% 66
185.148.77.0/24 Valid RIR databaseRIPE 673 100% 66
185.148.79.0/24 Valid RIR databaseRIPE 673 100% 66
185.158.4.0/22 Valid RIR databaseRIPE 673 100% 66
217.16.0.0/20 Valid RIR databaseRIPE 673 100% 66
46.16.205.0/24 Valid RIR databaseRIPE 668 99% 67
46.16.207.0/24 Valid RIR databaseRIPE 668 99% 67

AS-SET

AS204818's PeeringDB record names no 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 12 are in fix.csv.

  • ROA: none7
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none45.92.108.0/22No ROA covers it. Add a ROA for AS204818, maxLength 22.673 of 673
ROA: none185.245.92.0/23No ROA covers it. Add a ROA for AS204818, maxLength 23.673 of 673
ROA: none185.245.94.0/23No ROA covers it. Add a ROA for AS204818, maxLength 23.673 of 673
ROA: none194.88.246.0/23No ROA covers it. Add a ROA for AS204818, maxLength 23.673 of 673
ROA: none213.134.14.0/24No ROA covers it. Add a ROA for AS204818, maxLength 24.673 of 673
ROA: none81.161.58.0/24No ROA covers it. Add a ROA for AS204818, maxLength 24.672 of 673
ROA: none2a0d:5380::/29No ROA covers it. Add a ROA for AS204818, maxLength 29.633 of 636

Route objects not announced

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

46.16.206.0/24RIPEValid
193.218.120.0/24RIPEValid
2001:470:213::/48ARINValid
2a05:36c0::/29RIPEValid
2c0f:7e00::/32AFRINICNo ROA

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.