Network · data from 2026-11-12
AS271798 AS271798 - TECNO WIFI SRL
Registry name: AS271798 - TECNO WIFI SRL, AR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271798, 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.49.232.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2803:4010::/35 | No ROA | Other IRR onlyRADB | 634 100% |
AS-SET
AS271798 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 15 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 179.49.232.0/24 | No ROA covers it. Add a ROA for AS271798, maxLength 24. |
| Route object: RIR | 179.49.232.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2803:4010::/35 | No ROA covers it. Add a ROA for AS271798, maxLength 35. |
| Route object: RIR | 2803:4010::/35 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271798 whose prefix no peer sees AS271798 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.49.233.0/24 | RADB | No ROA |
| 179.49.234.0/24 | RADB | No ROA |
| 179.49.235.0/24 | RADB | No ROA |
| 2803:4010::/32 | RADB | No ROA |
| 2803:4010:2000::/35 | RADB | No ROA |
| 2803:4010:4000::/35 | RADB | No ROA |
| 2803:4010:6000::/35 | RADB | No ROA |
| 2803:4010:8000::/35 | RADB | No ROA |
| 2803:4010:a000::/35 | RADB | No ROA |
| 2803:4010:c000::/35 | RADB | No ROA |
| 2803:4010:e000::/35 | 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.