bgpreport

Network · data from 2026-11-12

AS59586 CAG-AS CAG Datastod AB

Registry name: CAG-AS CAG Datastod AB, SE · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 66.7% with a route object
2IPv6 routes 100.0% RPKI valid · 100.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 AS59586, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59586, 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.
94.136.75.0/24 Valid None 672 100% 66
91.240.252.0/23 Valid RIR databaseRIPE 672 100% 66
185.148.140.0/22 Valid RIR databaseRIPE 672 100% 66
2001:67c:1ba4::/48 Valid RIR databaseRIPE 636 100% 69
2a07:6000::/29 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS59586 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: none94.136.75.0/24No route object for it. Add a route object with origin AS59586 in the RIR database for the space.672 of 673

Route objects not announced

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