Network · data from 2026-11-12
AS274365 AS274365 - IT TECNOLOGIA EM TI LTDA
Registry name: AS274365 - IT TECNOLOGIA EM TI LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS274365, 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.
| 2804:96e0::/32 | No ROA | None | 354 56% |
| 212.134.92.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 198.23.218.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 109.66.186.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
AS-SET
AS274365 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 4 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:96e0::/32 | No ROA covers it. Add a ROA for AS274365, maxLength 32. |
| Route object: none | 2804:96e0::/32 | No route object for it. Add a route object with origin AS274365 in the RIR database for the space. |
| Route object: RIR | 212.134.92.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS274365 whose prefix no peer sees AS274365 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 79.182.190.0/24 | RADB, RIPE | 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.