Network · data from 2026-11-12
AS43201 Telematika LLC
Registry name: TELEMATIKA-AS Telematika LLC, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43201, 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.
| 195.60.236.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.228.160.0/23 | Valid | Nonecovered by 193.228.160.0/22 | 673 100% |
| 193.228.162.0/23 | Valid | Nonecovered by 193.228.160.0/22 | 673 100% |
| 91.247.77.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.247.79.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.228.160.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.158.220.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.158.220.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.158.222.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS43201: as-set-tele-matika. 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 (AS43201 isn't in the set, or no route object for AS43201 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 | AS43201 in it | Not covered |
|---|---|---|---|---|---|
| as-set-tele-matika | RIPElists itself further down2 member sets in no database: AS-DONCLIP, AS-MULTSYS | 206 | 70 | 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 17 are in fix.csv.
- ROA: none1
- Route object: none2
- AS-SET: missing member2
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.60.236.0/24 | No ROA covers it. Add a ROA for AS43201, maxLength 24. |
| Route object: none | 193.228.160.0/23 | No route object for it. A route object for 193.228.160.0/22 with origin AS43201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43201 in the RIR database for the space. |
| Route object: none | 193.228.162.0/23 | No route object for it. A route object for 193.228.160.0/22 with origin AS43201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43201 in the RIR database for the space. |
| AS-SET: missing member | as-set-tele-matika | AS-SET-TELE-MATIKA (RIPE) lists AS-DONCLIP; no IRR database read has it. |
| AS-SET: missing member | as-set-tele-matika | AS-SET-TELE-MATIKA (RIPE) lists AS-MULTSYS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS43201 whose prefix no peer sees AS43201 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.42.216.0/24 | RIPE | Valid |
| 31.222.251.0/24 | RIPE | Valid |
| 37.72.131.0/24 | RIPE | Valid |
| 37.72.139.0/24 | RIPE | Valid |
| 46.16.33.0/24 | RIPE | Valid |
| 46.175.132.0/24 | RIPE | Valid |
| 91.213.155.0/24 | RIPE | Valid |
| 94.103.182.0/24 | RIPE | No ROA |
| 193.3.170.0/24 | RIPE | Valid |
| 194.104.139.0/24 | RIPE | Valid |
| 194.104.140.0/24 | RIPE | Valid |
| 2a0c:e1c0::/29 | 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.