bgpreport

Network · data from 2026-11-12

AS25548 SCS-Telecom

Registry name: SCS-TELECOM-AS SCS - Telecom LLP, KZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25548, 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.
31.148.202.0/24 Valid Nonecovered by 31.148.202.0/23 672 100% 66
93.170.36.0/24 Valid Nonecovered by 93.170.36.0/22 672 100% 66
93.170.37.0/24 Valid Nonecovered by 93.170.36.0/22 672 100% 66
93.170.38.0/23 Valid Nonecovered by 93.170.36.0/22 672 100% 66
95.47.187.0/24 Valid Nonecovered by 95.47.186.0/23 671 100% 66
31.148.202.0/23 Valid RIR databaseRIPE 673 100% 66
95.47.178.0/23 Valid RIR databaseRIPE 673 100% 66
95.47.186.0/23 Valid RIR databaseRIPE 673 100% 66
2a11:12c0::/29 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS25548'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 6 are in fix.csv.

  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none31.148.202.0/24No route object for it. A route object for 31.148.202.0/23 with origin AS25548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25548 in the RIR database for the space.672 of 673
Route object: none93.170.36.0/24No route object for it. A route object for 93.170.36.0/22 with origin AS25548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25548 in the RIR database for the space.672 of 673
Route object: none93.170.37.0/24No route object for it. A route object for 93.170.36.0/22 with origin AS25548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25548 in the RIR database for the space.672 of 673
Route object: none93.170.38.0/23No route object for it. A route object for 93.170.36.0/22 with origin AS25548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25548 in the RIR database for the space.672 of 673
Route object: none95.47.187.0/24No route object for it. A route object for 95.47.186.0/23 with origin AS25548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25548 in the RIR database for the space.671 of 673

Route objects not announced

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

93.170.36.0/22RIPEValid

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.