Network · data from 2026-11-12
AS30936 RENET-COM-AS RENET COM Ltd.
Registry name: RENET-COM-AS RENET COM Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS30936, 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.
| 91.240.219.0/24 | No ROA | Other origin only | 224 33% |
| 82.116.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 87.238.232.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.39.116.0/22 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS30936 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 14 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.240.219.0/24 | No ROA covers it. Add a ROA for AS30936, maxLength 24. |
| Route object: none | 91.240.219.0/24 | Route objects for it name AS206850. Add a route object with origin AS30936 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS30936 whose prefix no peer sees AS30936 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.116.32.0/24 | RIPE | Invalid: maxLength |
| 82.116.37.0/24 | RIPE | Invalid: maxLength |
| 82.116.42.0/23 | RIPE | Invalid: maxLength |
| 82.116.43.0/24 | RIPE | Invalid: maxLength |
| 82.116.44.0/24 | RIPE | Invalid: maxLength |
| 82.116.49.0/24 | RIPE | Invalid: maxLength |
| 82.116.51.0/24 | RIPE | Invalid: maxLength |
| 82.116.52.0/24 | RIPE | Invalid: maxLength |
| 82.116.53.0/24 | RIPE | Invalid: maxLength |
| 82.116.56.0/23 | RIPE | Invalid: maxLength |
| 82.116.60.0/24 | RIPE | Invalid: maxLength |
| 2a01:4420::/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.