bgpreport

Network · data from 2026-11-12

AS207966 STS Services

Registry name: STSKZ AO "State Technical Service", KZ · PeeringDB

3IPv4 routes 33.3% RPKI valid · 66.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No 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 AS207966, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS207966, 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.
89.218.4.68/30 Invalid: origin None 1 0%low visibility 1
195.12.120.0/24 No ROA RIR databaseRIPE 673 100% 66
91.214.42.0/23 Valid RIR databaseRIPE 673 100% 66
2a00:5da1:100::/48 Valid RIR databaseRIPE 636 100% 68

AS-SET

AS207966'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: origin1
  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin89.218.4.68/30ROAs covering it name AS9198, not AS207966. If AS207966 should announce it, add a ROA for AS207966.1 of 673
Route object: none89.218.4.68/30No route object for it. Add a route object with origin AS207966 in the RIR database for the space.1 of 673
ROA: none195.12.120.0/24No ROA covers it. Add a ROA for AS207966, maxLength 24.673 of 673

Route objects not announced

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