Network · data from 2026-11-12
AS215373 DELSKA-C4 Sabiedriba ar ierobezotu atbildibu DELSKA Latvia
Registry name: DELSKA-C4 Sabiedriba ar ierobezotu atbildibu DELSKA Latvia, LV · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215373, 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.
| 89.124.10.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.124.11.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.124.8.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 89.124.9.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.84.44.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 81.16.236.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 89.47.175.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.111.19.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.111.22.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.111.25.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.111.26.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.111.27.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.111.28.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.111.29.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.111.30.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.111.31.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.219.156.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.219.157.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.219.158.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.219.159.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.164.210.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 37.203.35.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.203.37.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.203.38.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS215373 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 12 are in fix.csv.
- ROA: none6
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.124.10.0/24 | No ROA covers it. Add a ROA for AS215373, maxLength 24. |
| ROA: none | 89.124.11.0/24 | No ROA covers it. Add a ROA for AS215373, maxLength 24. |
| ROA: none | 89.124.8.0/24 | No ROA covers it. Add a ROA for AS215373, maxLength 24. |
| ROA: none | 89.124.9.0/24 | No ROA covers it. Add a ROA for AS215373, maxLength 24. |
| ROA: none | 185.84.44.0/24 | No ROA covers it. Add a ROA for AS215373, maxLength 24. |
| ROA: none | 81.16.236.0/24 | No ROA covers it. Add a ROA for AS215373, maxLength 24. |
Route objects not announced
Route objects with origin AS215373 whose prefix no peer sees AS215373 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.111.9.0/24 | RIPE | Valid |
| 89.111.10.0/24 | RIPE | Valid |
| 89.111.26.0/23 | RIPE | Valid |
| 89.111.28.0/22 | RIPE | Valid |
| 185.219.156.0/22 | RIPE | Valid |
| 2001:470:65c::/48 | ARIN | Valid |
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.