Network · data from 2026-11-12
AS199669 ATLEX.RU
Registry name: ATLEX-AS Okay-Telecom Ltd., RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199669, 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.
| 185.71.196.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 2a11:2084::/32 | No ROA | RIR databaseRIPE | 633 100% |
| 2a11:8305::/32 | No ROA | RIR databaseRIPE | 633 100% |
| 2a11:aac4::/32 | No ROA | RIR databaseRIPE | 633 100% |
| 2a11:c107::/32 | No ROA | RIR databaseRIPE | 633 100% |
| 46.29.118.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.109.200.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 109.196.166.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 170.168.21.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.10.44.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.195.170.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.38.10.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.38.11.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.10.44.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a03:ec0::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:ec0:1::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS199669: AS-ATLEX. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS199669 isn't in the set, or no route object for AS199669 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS199669 in it | Not covered |
|---|---|---|---|---|---|
| AS-ATLEX | RIPE | 1 | 1 | Yes | 0 |
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 7 are in fix.csv.
- ROA: none5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.71.196.0/22 | No ROA covers it. Add a ROA for AS199669, maxLength 22. |
| ROA: none | 2a11:2084::/32 | No ROA covers it. Add a ROA for AS199669, maxLength 32. |
| ROA: none | 2a11:8305::/32 | No ROA covers it. Add a ROA for AS199669, maxLength 32. |
| ROA: none | 2a11:aac4::/32 | No ROA covers it. Add a ROA for AS199669, maxLength 32. |
| ROA: none | 2a11:c107::/32 | No ROA covers it. Add a ROA for AS199669, maxLength 32. |
Route objects not announced
Route objects with origin AS199669 whose prefix no peer sees AS199669 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 93.183.112.0/24 | RIPE | Valid |
| 2a03:ec0::/32 | RIPE | No ROA |
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.