bgpreport

Network · data from 2026-11-12

AS57333 ASKASPIYTELEKOM

Registry name: ASKASPIYTELEKOM KaspiyTelekom Ltd., RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57333, 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.
176.97.168.0/22 Invalid: maxLength Nonecovered by 176.97.168.0/21 2 0%low visibility 2
176.97.160.0/19 Valid RIR databaseRIPE 673 100% 67
176.97.168.0/21 Valid RIR databaseRIPE 673 100% 67
176.97.176.0/21 Valid RIR databaseRIPE 673 100% 67
176.97.184.0/21 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS57333'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 3 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength176.97.168.0/22ROA 176.97.160.0/19 AS57333 has maxLength 19; ROA 176.97.168.0/21 AS57333 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 176.97.168.0/22.2 of 673
Route object: none176.97.168.0/22No route object for it. A route object for 176.97.168.0/21 with origin AS57333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57333 in the RIR database for the space.2 of 673

Route objects not announced

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

176.97.160.0/21RIPEValid

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.