Network · data from 2026-11-12
AS12993 DELSKA Latvia
Registry name: DEAC-AS Sabiedriba ar ierobezotu atbildibu DELSKA Latvia, LV · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12993, 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.
| 94.158.20.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 77.83.1.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 37.203.32.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 81.94.224.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 82.21.227.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.22.224.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.23.204.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.24.220.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.25.210.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.26.219.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 89.111.0.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 178.16.16.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 185.34.24.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.34.24.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.34.26.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.219.156.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.105.104.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.108.144.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.108.185.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.200.96.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 194.9.175.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.152.32.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 195.216.236.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.110.66.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 213.110.67.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 37.203.32.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 37.203.39.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.28.56.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.108.146.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 2a00:17c0::/32 | Valid | RIR databaseRADB, RIPE | 635 100% |
| 2a00:17c0:a0::/44 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:17c0:d0::/44 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS12993: AS-DEAC. 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 (AS12993 isn't in the set, or no route object for AS12993 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 | AS12993 in it | Not covered |
|---|---|---|---|---|---|
| AS-DEAC | RIPElists itself further down | 41 | 4 | 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 46 are in fix.csv.
- ROA: none2
- Route object: not announced44
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 94.158.20.0/24 | No ROA covers it. Add a ROA for AS12993, maxLength 24. |
| ROA: none | 77.83.1.0/24 | No ROA covers it. Add a ROA for AS12993, maxLength 24. |
Route objects not announced
Route objects with origin AS12993 whose prefix no peer sees AS12993 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.203.37.0/24 | RIPE | Valid |
| 37.203.38.0/24 | RIPE | Valid |
| 81.94.229.0/24 | RIPE | Valid |
| 82.21.237.0/24 | RADB, RIPE | Valid |
| 82.23.214.0/24 | RADB, RIPE | Valid |
| 82.24.214.0/24 | RADB, RIPE | Valid |
| 82.25.234.0/24 | RADB, RIPE | Valid |
| 82.26.220.0/24 | RADB, RIPE | Valid |
| 82.26.230.0/24 | RADB, RIPE | Valid |
| 82.26.233.0/24 | RADB, RIPE | Valid |
| 82.27.210.0/24 | RADB, RIPE | Valid |
| 82.27.218.0/24 | RADB, RIPE | Valid |
| 82.27.220.0/24 | RADB, RIPE | Valid |
| 82.29.211.0/24 | RADB, RIPE | Valid |
| 82.29.220.0/24 | RADB, RIPE | Valid |
| 89.111.4.0/24 | RIPE | Invalid: maxLength |
| 89.111.11.0/24 | RIPE | Invalid: maxLength |
| 89.111.12.0/24 | RIPE | Invalid: maxLength |
| 89.111.15.0/24 | RIPE | Invalid: maxLength |
| 89.111.18.0/24 | RIPE | Invalid: maxLength |
| 89.111.20.0/22 | RIPE | Invalid: maxLength |
| 89.111.20.0/24 | RIPE | Invalid: maxLength |
| 89.111.22.0/24 | RIPE | Valid |
| 89.111.23.0/24 | RIPE | Invalid: maxLength |
| 89.111.24.0/21 | RIPE | Invalid: maxLength |
| 89.111.25.0/24 | RIPE | Valid |
| 89.111.26.0/24 | RIPE | Valid |
| 89.111.27.0/24 | RIPE | Invalid: maxLength |
| 89.111.32.0/19 | RIPE | Invalid: maxLength |
| 89.111.38.0/24 | RIPE | Valid |
| 89.111.48.0/20 | RIPE | Invalid: maxLength |
| 89.111.48.0/24 | RIPE | Invalid: maxLength |
| 89.111.53.0/24 | RIPE | Invalid: maxLength |
| 89.111.54.0/24 | RIPE | Invalid: maxLength |
| 89.111.55.0/24 | RIPE | Invalid: maxLength |
| 89.111.56.0/24 | RIPE | Invalid: maxLength |
| 89.111.57.0/24 | RIPE | Invalid: maxLength |
| 89.111.59.0/24 | RIPE | Invalid: maxLength |
| 89.111.60.0/24 | RIPE | Invalid: maxLength |
| 89.111.61.0/24 | RIPE | Invalid: maxLength |
| 89.111.62.0/24 | RIPE | Invalid: maxLength |
| 89.111.63.0/24 | RIPE | Invalid: maxLength |
| 193.108.144.0/22 | RIPE | Valid |
| 2a00:17c0:dc01::/48 | RIPE | Invalid: maxLength |
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.