bgpreport

Network · data from 2026-11-12

AS56594 cb-byo-ip CGI GLOBAL LIMITED

Registry name: cb-byo-ip CGI GLOBAL LIMITED, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56594, 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.
217.145.79.0/24 Invalid: origin Other origin only 2 0%low visibility 2
31.58.137.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
151.242.43.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.158.169.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
31.59.46.0/24 Valid RIR databaseRIPE 670 100% 67
31.59.47.0/24 Valid RIR databaseRIPE 670 100% 67
31.59.92.0/24 Valid RIR databaseRIPE 670 100% 67
31.59.93.0/24 Valid RIR databaseRIPE 670 100% 67
31.59.94.0/24 Valid RIR databaseRIPE 670 100% 67
31.59.95.0/24 Valid RIR databaseRIPE 670 100% 67
31.59.114.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
31.59.185.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
151.242.69.0/24 Valid RIR databaseRADB, RIPE 670 100% 67

AS-SET

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

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin217.145.79.0/24ROAs covering it name AS834, AS8851, AS19905, not AS56594. If AS56594 should announce it, add a ROA for AS56594.2 of 673
Route object: none217.145.79.0/24Route objects for it name AS834. Add a route object with origin AS56594 in the RIR database for the space.2 of 673

Route objects not announced

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