Network · data from 2026-11-12
AS30729 TRANSFER-AS TRANSFER Ltd.
Registry name: TRANSFER-AS TRANSFER Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS30729, 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.
| 81.23.192.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 185.18.112.0/22 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS30729 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: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 81.23.192.0/20 | No ROA covers it. Add a ROA for AS30729, maxLength 20. |
| ROA: none | 185.18.112.0/22 | No ROA covers it. Add a ROA for AS30729, maxLength 22. |
Route objects not announced
Route objects with origin AS30729 whose prefix no peer sees AS30729 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.205.128.0/17 | RADB | No ROA |
| 82.205.128.0/19 | RADB | No ROA |
| 168.187.243.0/24 | RADB | No ROA |
| 194.146.236.0/22 | RADB | No ROA |
| 195.47.234.0/24 | RADB | 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.