Network · data from 2026-11-12
AS58314 B2B-Telecom SvyazResurs-Kuban, LLC
Registry name: B2B-Telecom SvyazResurs-Kuban, LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58314, 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.91.252.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.91.253.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.91.254.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 193.242.148.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 193.242.149.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.130.188.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.130.189.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.130.190.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.130.191.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.130.172.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 45.130.173.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 2a05:edc0::/29 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS58314 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 18 are in fix.csv.
- ROA: none12
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.91.252.0/24 | No ROA covers it. Add a ROA for AS58314, maxLength 24. |
| ROA: none | 185.91.253.0/24 | No ROA covers it. Add a ROA for AS58314, maxLength 24. |
| ROA: none | 185.91.254.0/24 | No ROA covers it. Add a ROA for AS58314, maxLength 24. |
| ROA: none | 193.242.148.0/22 | No ROA covers it. Add a ROA for AS58314, maxLength 22. |
| ROA: none | 193.242.149.0/24 | No ROA covers it. Add a ROA for AS58314, maxLength 24. |
| ROA: none | 45.130.188.0/24 | No ROA covers it. Add a ROA for AS58314, maxLength 24. |
| ROA: none | 45.130.189.0/24 | No ROA covers it. Add a ROA for AS58314, maxLength 24. |
| ROA: none | 45.130.190.0/24 | No ROA covers it. Add a ROA for AS58314, maxLength 24. |
| ROA: none | 45.130.191.0/24 | No ROA covers it. Add a ROA for AS58314, maxLength 24. |
| ROA: none | 45.130.172.0/24 | No ROA covers it. Add a ROA for AS58314, maxLength 24. |
| ROA: none | 45.130.173.0/24 | No ROA covers it. Add a ROA for AS58314, maxLength 24. |
| ROA: none | 2a05:edc0::/29 | No ROA covers it. Add a ROA for AS58314, maxLength 29. |
Route objects not announced
Route objects with origin AS58314 whose prefix no peer sees AS58314 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.130.174.0/24 | RIPE | No ROA |
| 185.91.252.0/22 | RIPE | No ROA |
| 185.91.255.0/24 | RIPE | No ROA |
| 193.242.148.0/24 | RIPE | No ROA |
| 193.242.150.0/24 | RIPE | No ROA |
| 193.242.151.0/24 | 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.