Network · data from 2026-11-12
AS201211 LLC "Tvoi Telecom"
Registry name: DRUGOYTEL-AS LLC "Drugoy Telecom", RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201211, 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.
| 45.94.21.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 45.94.104.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 45.133.217.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 45.147.202.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 46.21.240.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 62.133.52.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 95.130.226.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.219.52.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 194.110.8.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 45.147.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.130.224.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.19.202.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.73.16.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.82.24.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.164.174.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.178.118.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a05:3e80::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS201211: AS-DRUGOYTEL. 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 (AS201211 isn't in the set, or no route object for AS201211 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 | AS201211 in it | Not covered |
|---|---|---|---|---|---|
| AS-DRUGOYTEL | RIPE | 12 | 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 9 are in fix.csv.
- ROA: none9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.94.21.0/24 | No ROA covers it. Add a ROA for AS201211, maxLength 24. |
| ROA: none | 45.94.104.0/22 | No ROA covers it. Add a ROA for AS201211, maxLength 22. |
| ROA: none | 45.133.217.0/24 | No ROA covers it. Add a ROA for AS201211, maxLength 24. |
| ROA: none | 45.147.202.0/23 | No ROA covers it. Add a ROA for AS201211, maxLength 23. |
| ROA: none | 46.21.240.0/22 | No ROA covers it. Add a ROA for AS201211, maxLength 22. |
| ROA: none | 62.133.52.0/22 | No ROA covers it. Add a ROA for AS201211, maxLength 22. |
| ROA: none | 95.130.226.0/24 | No ROA covers it. Add a ROA for AS201211, maxLength 24. |
| ROA: none | 185.219.52.0/23 | No ROA covers it. Add a ROA for AS201211, maxLength 23. |
| ROA: none | 194.110.8.0/22 | No ROA covers it. Add a ROA for AS201211, maxLength 22. |
Route objects not announced
Every route object with origin AS201211 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.