Network · data from 2026-11-12
AS202413 PRONKIN-AS Pronkin Timofei
Registry name: PRONKIN-AS Pronkin Timofei, EE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202413, 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.56.12.0/24 | Invalid: origin | Other origin only | 53 8%low visibility |
AS-SET
AS202413 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 17 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 31.56.12.0/24 | ROAs covering it name AS834, AS197666, not AS202413. If AS202413 should announce it, add a ROA for AS202413. |
| Route object: none | 31.56.12.0/24 | Route objects for it name AS197666. Add a route object with origin AS202413 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202413 whose prefix no peer sees AS202413 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2.27.59.0/24 | RIPE | Valid |
| 2.27.61.0/24 | RIPE | Valid |
| 31.58.232.0/23 | RIPE | Valid |
| 31.59.39.0/24 | RIPE | Valid |
| 31.59.209.0/24 | RIPE | Valid |
| 94.183.203.0/24 | RIPE | Valid |
| 94.183.208.0/24 | RIPE | Valid |
| 94.183.209.0/24 | RIPE | Valid |
| 94.183.226.0/24 | RIPE | Valid |
| 94.183.238.0/24 | RIPE | Valid |
| 94.183.239.0/24 | RIPE | Valid |
| 94.183.254.0/24 | RIPE | Valid |
| 217.60.8.0/23 | RIPE | Valid |
| 217.60.67.0/24 | RIPE | Valid |
| 217.60.99.0/24 | 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.