Network · data from 2026-11-12
AS266449 INTERLIGA SOLUCOES TECNOLOGICAS
Registry name: AS266449 - INTERLIGA SOLUCOES TECNOLOGICAS LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266449, 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.
| 170.82.236.0/22 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 2804:3800::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
AS-SET
AS266449's PeeringDB record names no 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 8 are in fix.csv.
- Route object: RIR2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 170.82.236.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3800::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266449 whose prefix no peer sees AS266449 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.82.236.0/23 | TC | Valid |
| 170.82.236.0/24 | TC | Valid |
| 170.82.237.0/24 | RADB, TC | Valid |
| 170.82.238.0/23 | TC | Valid |
| 170.82.238.0/24 | TC | Valid |
| 170.82.239.0/24 | TC | 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.