Network · data from 2026-11-12
AS48430 FIRSTDC-AS Perviy TSOD LLC
Registry name: FIRSTDC-AS Perviy TSOD LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48430, 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.
| 188.119.120.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 194.156.100.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 2001:67c:29b8::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 94.231.222.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.139.212.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2a07:1840::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS48430 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 7 are in fix.csv.
- ROA: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 188.119.120.0/24 | No ROA covers it. Add a ROA for AS48430, maxLength 24. |
| ROA: none | 194.156.100.0/22 | No ROA covers it. Add a ROA for AS48430, maxLength 22. |
| ROA: none | 2001:67c:29b8::/48 | No ROA covers it. Add a ROA for AS48430, maxLength 48. |
Route objects not announced
Route objects with origin AS48430 whose prefix no peer sees AS48430 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.133.60.0/22 | RIPE | Invalid: origin |
| 93.185.164.0/22 | RIPE | No ROA |
| 193.233.47.0/24 | RIPE | Valid |
| 2a0c:7b00::/29 | 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.