Network · data from 2026-11-12
AS49058 DKTEL-PLT-AS DK Svyaz OOO
Registry name: DKTEL-PLT-AS DK Svyaz OOO, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49058, 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.
| 185.25.10.1/32 | Valid | Nonecovered by 185.25.10.0/23 | 6 1%low visibility |
| 95.131.176.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.25.9.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.25.10.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS49058 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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.25.10.1/32 | No route object for it. A route object for 185.25.10.0/23 with origin AS49058 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49058 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49058 whose prefix no peer sees AS49058 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a00:7b60::/32 | RIPE | 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.