Network · data from 2026-11-12
AS42516 Sovtest Internet
Registry name: SOVTEST-INTERNET-AS Sovtest-Internet Limited Liability Company, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42516, 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.
| 91.204.144.0/22 | No ROA | Other origin only | 31 5%low visibility |
| 195.93.164.0/23 | No ROA | Other origin only | 31 5%low visibility |
| 185.5.16.0/22 | No ROA | RIR databaseRIPE | 44 7%low visibility |
| 77.243.0.0/20 | No ROA | RIR databaseRIPE | 42 6%low visibility |
| 128.65.136.0/21 | No ROA | RIR databaseRIPE | 42 6%low visibility |
| 195.49.184.0/22 | No ROA | RIR databaseRIPE | 42 6%low visibility |
AS-SET
PeeringDB's irr_as_set for AS42516: AS-SOVTEST. 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 (AS42516 isn't in the set, or no route object for AS42516 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 | AS42516 in it | Not covered |
|---|---|---|---|---|---|
| AS-SOVTEST | RIPE | 5 | 1 | Yes | 2 |
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 9 are in fix.csv.
- ROA: none6
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.204.144.0/22 | No ROA covers it. Add a ROA for AS42516, maxLength 22. |
| Route object: none | 91.204.144.0/22 | Route objects for it name AS44266, AS47465. Add a route object with origin AS42516 in the RIR database for the space. |
| ROA: none | 195.93.164.0/23 | No ROA covers it. Add a ROA for AS42516, maxLength 23. |
| Route object: none | 195.93.164.0/23 | Route objects for it name AS44266. Add a route object with origin AS42516 in the RIR database for the space. |
| ROA: none | 185.5.16.0/22 | No ROA covers it. Add a ROA for AS42516, maxLength 22. |
| ROA: none | 77.243.0.0/20 | No ROA covers it. Add a ROA for AS42516, maxLength 20. |
| ROA: none | 128.65.136.0/21 | No ROA covers it. Add a ROA for AS42516, maxLength 21. |
| ROA: none | 195.49.184.0/22 | No ROA covers it. Add a ROA for AS42516, maxLength 22. |
Route objects not announced
Route objects with origin AS42516 whose prefix no peer sees AS42516 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a02:69c0::/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.