bgpreport

Network · data from 2026-11-12

AS60630 ARN

Registry name: ARN Association Alsace Reseau Neutre, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60630, 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.
2a00:5881:8120::/48 Invalid: maxLength RIR databaseRIPE 6 1%low visibility 2
89.234.141.0/24 Valid RIR databaseRIPE 672 100% 66
89.234.151.0/24 Valid RIR databaseRIPE 672 100% 66
2a00:5881:8100::/40 Valid RIR databaseRIPE 633 100% 69

AS-SET

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

  • ROA: maxLength1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2a00:5881:8120::/48ROA 2a00:5881:8100::/40 AS60630 has maxLength 40; the route is a /48. Raise the maxLength, or add a ROA for 2a00:5881:8120::/48.6 of 636

Route objects not announced

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