bgpreport

Network · data from 2026-11-12

AS20688 CHUDO-TELECOM-AS Chudo Telecom Ltd.

Registry name: CHUDO-TELECOM-AS Chudo Telecom Ltd., RU · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 60.0% with a route object
0IPv6 routes
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
0Route objects not announced registered with origin AS20688, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20688, 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.
146.120.4.0/22 Valid Nonecovered by 146.120.0.0/21 672 100% 67
146.120.6.0/23 Valid Nonecovered by 146.120.0.0/21 672 100% 67
92.38.2.0/24 Valid RIR databaseRIPE 672 100% 67
146.120.0.0/21 Valid RIR databaseRIPE 672 100% 66
185.18.91.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS20688 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.

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none146.120.4.0/22No route object for it. A route object for 146.120.0.0/21 with origin AS20688 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20688 in the RIR database for the space.672 of 673
Route object: none146.120.6.0/23No route object for it. A route object for 146.120.0.0/21 with origin AS20688 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20688 in the RIR database for the space.672 of 673

Route objects not announced

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