Network · data from 2026-11-12
AS47438 Pskovline
Registry name: PSKOVLINE-AS Pskovline Ltd., RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47438, 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.
| 31.132.96.0/19 | No ROA | RIR databaseRIPE | 671 100% |
| 89.23.0.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 89.23.8.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 89.23.16.0/20 | No ROA | RIR databaseRIPE | 671 100% |
| 91.204.136.0/22 | No ROA | RIR databaseRADB, RIPE | 671 100% |
| 91.237.148.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 109.207.176.0/20 | No ROA | RIR databaseRIPE | 671 100% |
| 176.113.0.0/19 | No ROA | RIR databaseRIPE | 671 100% |
| 176.113.32.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 188.130.240.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 2001:67c:233c::/48 | No ROA | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS47438: AS-PSKOVLINE. 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 (AS47438 isn't in the set, or no route object for AS47438 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 | AS47438 in it | Not covered |
|---|---|---|---|---|---|
| AS-PSKOVLINE | RIPE | 3 | 1 | 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 12 are in fix.csv.
- ROA: none11
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 31.132.96.0/19 | No ROA covers it. Add a ROA for AS47438, maxLength 19. |
| ROA: none | 89.23.0.0/21 | No ROA covers it. Add a ROA for AS47438, maxLength 21. |
| ROA: none | 89.23.8.0/21 | No ROA covers it. Add a ROA for AS47438, maxLength 21. |
| ROA: none | 89.23.16.0/20 | No ROA covers it. Add a ROA for AS47438, maxLength 20. |
| ROA: none | 91.204.136.0/22 | No ROA covers it. Add a ROA for AS47438, maxLength 22. |
| ROA: none | 91.237.148.0/24 | No ROA covers it. Add a ROA for AS47438, maxLength 24. |
| ROA: none | 109.207.176.0/20 | No ROA covers it. Add a ROA for AS47438, maxLength 20. |
| ROA: none | 176.113.0.0/19 | No ROA covers it. Add a ROA for AS47438, maxLength 19. |
| ROA: none | 176.113.32.0/21 | No ROA covers it. Add a ROA for AS47438, maxLength 21. |
| ROA: none | 188.130.240.0/22 | No ROA covers it. Add a ROA for AS47438, maxLength 22. |
| ROA: none | 2001:67c:233c::/48 | No ROA covers it. Add a ROA for AS47438, maxLength 48. |
Route objects not announced
Route objects with origin AS47438 whose prefix no peer sees AS47438 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.23.0.0/19 | 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.