Network · data from 2026-11-12
AS49777 ATEXS-AS ATEXS PLUS Ltd.
Registry name: ATEXS-AS ATEXS PLUS Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49777, 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.
| 178.218.32.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 178.218.40.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.218.41.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.218.42.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.218.43.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.218.44.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.218.45.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.218.46.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.218.47.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.109.70.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 193.109.70.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.109.71.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS49777 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 20 are in fix.csv.
- ROA: none12
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 178.218.32.0/20 | No ROA covers it. Add a ROA for AS49777, maxLength 20. |
| ROA: none | 178.218.40.0/24 | No ROA covers it. Add a ROA for AS49777, maxLength 24. |
| ROA: none | 178.218.41.0/24 | No ROA covers it. Add a ROA for AS49777, maxLength 24. |
| ROA: none | 178.218.42.0/24 | No ROA covers it. Add a ROA for AS49777, maxLength 24. |
| ROA: none | 178.218.43.0/24 | No ROA covers it. Add a ROA for AS49777, maxLength 24. |
| ROA: none | 178.218.44.0/24 | No ROA covers it. Add a ROA for AS49777, maxLength 24. |
| ROA: none | 178.218.45.0/24 | No ROA covers it. Add a ROA for AS49777, maxLength 24. |
| ROA: none | 178.218.46.0/24 | No ROA covers it. Add a ROA for AS49777, maxLength 24. |
| ROA: none | 178.218.47.0/24 | No ROA covers it. Add a ROA for AS49777, maxLength 24. |
| ROA: none | 193.109.70.0/23 | No ROA covers it. Add a ROA for AS49777, maxLength 23. |
| ROA: none | 193.109.70.0/24 | No ROA covers it. Add a ROA for AS49777, maxLength 24. |
| ROA: none | 193.109.71.0/24 | No ROA covers it. Add a ROA for AS49777, maxLength 24. |
Route objects not announced
Route objects with origin AS49777 whose prefix no peer sees AS49777 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.218.32.0/24 | RIPE | No ROA |
| 178.218.33.0/24 | RIPE | No ROA |
| 178.218.34.0/24 | RIPE | No ROA |
| 178.218.35.0/24 | RIPE | No ROA |
| 178.218.36.0/24 | RIPE | No ROA |
| 178.218.37.0/24 | RIPE | No ROA |
| 178.218.38.0/24 | RIPE | No ROA |
| 178.218.39.0/24 | 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.