Network · data from 2026-11-12
AS39749 Befree-AS Befree Ltd
Registry name: Befree-AS Befree Ltd, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39749, 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.
| 89.113.16.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 94.140.195.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 188.227.24.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS39749 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 11 are in fix.csv.
- ROA: none3
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.113.16.0/21 | No ROA covers it. Add a ROA for AS39749, maxLength 21. |
| ROA: none | 94.140.195.0/24 | No ROA covers it. Add a ROA for AS39749, maxLength 24. |
| ROA: none | 188.227.24.0/24 | No ROA covers it. Add a ROA for AS39749, maxLength 24. |
Route objects not announced
Route objects with origin AS39749 whose prefix no peer sees AS39749 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.113.16.0/24 | RIPE | No ROA |
| 89.113.17.0/24 | RIPE | No ROA |
| 89.113.18.0/24 | RIPE | No ROA |
| 89.113.19.0/24 | RIPE | No ROA |
| 89.113.20.0/24 | RIPE | No ROA |
| 89.113.21.0/24 | RIPE | No ROA |
| 89.113.22.0/24 | RIPE | No ROA |
| 89.113.23.0/24 | 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.