Network · data from 2026-11-12
AS272201 AS272201 - ACSNET TELECOM
Registry name: AS272201 - ACSNET TELECOM, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS272201, 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.
| 179.48.139.0/24 | No ROA | Other IRR onlyRADB, TC | 663 99% |
| 2804:837c::/32 | No ROA | Other IRR onlyRADB, TC | 629 99% |
AS-SET
AS272201 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 6 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 179.48.139.0/24 | No ROA covers it. Add a ROA for AS272201, maxLength 24. |
| Route object: RIR | 179.48.139.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:837c::/32 | No ROA covers it. Add a ROA for AS272201, maxLength 32. |
| Route object: RIR | 2804:837c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS272201 whose prefix no peer sees AS272201 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:837c::/33 | RADB | No ROA |
| 2804:837c:8000::/33 | 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.