bgpreport

Network · data from 2026-11-12

AS39906 CoProSys

Registry name: COPROSYS CoProSys a.s., CZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39906, 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.
77.104.204.0/24 Valid Nonecovered by 77.104.192.0/19 671 100% 67
77.104.242.0/24 Valid Nonecovered by 77.104.224.0/19 671 100% 67
5.59.34.0/24 Valid RIR databaseRIPE 672 100% 67
77.104.192.0/18 Valid RIR databaseRIPE 672 100% 67
80.82.144.0/20 Valid RIR databaseRIPE 672 100% 67
81.92.144.0/20 Valid RIR databaseRIPE 672 100% 67
93.170.84.0/22 Valid RIR databaseRIPE 672 100% 67
94.138.96.0/19 Valid RIR databaseRIPE 672 100% 67
95.46.33.0/24 Valid RIR databaseRIPE 672 100% 67
178.23.232.0/21 Valid RIR databaseRIPE 672 100% 67
185.67.132.0/22 Valid RIR databaseRIPE 672 100% 67
2001:678:e54::/48 Valid RIR databaseRIPE 636 100% 67
2a02:da8::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS39906'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 14 are in fix.csv.

  • Route object: none2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none77.104.204.0/24No route object for it. A route object for 77.104.192.0/19 with origin AS39906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39906 in the RIR database for the space.671 of 673
Route object: none77.104.242.0/24No route object for it. A route object for 77.104.224.0/19 with origin AS39906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39906 in the RIR database for the space.671 of 673

Route objects not announced

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

5.59.0.0/16RIPENo ROA
77.104.192.0/19RIPEValid
77.104.224.0/19RIPEValid
80.82.144.0/21RIPEValid
80.82.152.0/21RIPEValid
81.92.144.0/21RIPEValid
81.92.152.0/21RIPEValid
94.138.96.0/20RIPEValid
94.138.112.0/20RIPEValid
178.23.232.0/22RIPEValid
178.23.236.0/22RIPEValid
2a02:da8:5::/48RIPEValid

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.