Network · data from 2026-11-12
AS61755 AS61755 - TECSOFTNET SOLUCOES EM INFORMATICA LTDA - ME
Registry name: AS61755 - TECSOFTNET SOLUCOES EM INFORMATICA LTDA - ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61755, 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.
| 131.100.44.0/22 | Valid | Other IRR onlyTC | 670 100% |
| 2804:1be4::/32 | Valid | Other IRR onlyTC | 634 100% |
AS-SET
AS61755 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 8 are in fix.csv.
- Route object: RIR2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 131.100.44.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1be4::/32 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61755 whose prefix no peer sees AS61755 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.100.44.0/23 | TC | Valid |
| 131.100.44.0/24 | TC | Valid |
| 131.100.45.0/24 | TC | Valid |
| 131.100.46.0/23 | TC | Valid |
| 131.100.46.0/24 | TC | Valid |
| 131.100.47.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.