bgpreport

Network · data from 2026-11-12

AS34941 CYBERCOM-AS Cygrids Communications AB

Registry name: CYBERCOM-AS Cygrids Communications AB, SE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34941, 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.
82.39.162.0/23 No ROA None 671 100% 66
185.112.138.0/24 Valid Nonecovered by 185.112.138.0/23 672 100% 66
185.112.139.0/24 Valid Nonecovered by 185.112.138.0/23 669 99% 67
85.118.200.0/24 Valid RIR databaseRIPE 673 100% 67
85.118.201.0/24 Valid RIR databaseRIPE 673 100% 67
85.118.202.0/24 Valid RIR databaseRIPE 673 100% 67
85.118.203.0/24 Valid RIR databaseRIPE 673 100% 67
85.118.204.0/24 Valid RIR databaseRIPE 673 100% 67
85.118.205.0/24 Valid RIR databaseRIPE 673 100% 67
85.118.207.0/24 Valid RIR databaseRIPE 673 100% 67
185.112.136.0/23 Valid RIR databaseRIPE 672 100% 66
85.118.206.0/24 Valid RIR databaseRIPE 669 99% 67
2a06:6180:4000::/40 Valid RIR databaseRIPE 636 100% 67
2a06:6187:8000::/35 Valid RIR databaseRIPE 636 100% 67
2a06:6180::/40 Valid RIR databaseRIPE 635 100% 67
2a06:6180:8000::/40 Valid RIR databaseRIPE 635 100% 67
2a06:6187::/35 Valid RIR databaseRIPE 635 100% 67
2a06:6187:4000::/35 Valid RIR databaseRIPE 635 100% 67
85.118.200.0/21 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • ROA: none1
  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none82.39.162.0/23No ROA covers it. Add a ROA for AS34941, maxLength 23.671 of 673
Route object: none82.39.162.0/23No route object for it. Add a route object with origin AS34941 in the RIR database for the space.671 of 673
Route object: none185.112.138.0/24No route object for it. A route object for 185.112.138.0/23 with origin AS34941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34941 in the RIR database for the space.672 of 673
Route object: none185.112.139.0/24No route object for it. A route object for 185.112.138.0/23 with origin AS34941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34941 in the RIR database for the space.669 of 673

Route objects not announced

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

82.39.162.0/24RADB, RIPEValid
82.39.163.0/24RADB, RIPEValid
185.112.138.0/23RIPENo 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.