Network · data from 2026-11-12
AS264990 AS264990 - WT INFORMATICA TELECOMUNICACOES LTDA - ME
Registry name: AS264990 - WT INFORMATICA TELECOMUNICACOES LTDA - ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264990, 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.84.20.0/23 | No ROA | Nonecovered by 170.84.20.0/22 | 671 100% |
| 2804:3110:7ff8::/45 | No ROA | Nonecovered by 2804:3110::/33 | 635 100% |
| 2804:3110:8000::/33 | No ROA | Nonecovered by 2804:3110::/32 | 633 100% |
| 2804:3110:8008::/45 | No ROA | Nonecovered by 2804:3110::/32 | 632 99% |
| 170.84.20.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 170.84.22.0/23 | No ROA | Other IRR onlyRADB | 669 99% |
| 2804:3110::/33 | No ROA | Other IRR onlyRADB | 635 100% |
| 2804:3110::/32 | No ROA | Other IRR onlyRADB | 634 100% |
AS-SET
AS264990 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 20 are in fix.csv.
- ROA: none8
- Route object: none4
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 170.84.20.0/23 | No ROA covers it. Add a ROA for AS264990, maxLength 23. |
| Route object: none | 170.84.20.0/23 | No route object for it. A route object for 170.84.20.0/22 with origin AS264990 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264990 in the RIR database for the space. |
| ROA: none | 2804:3110:7ff8::/45 | No ROA covers it. Add a ROA for AS264990, maxLength 45. |
| Route object: none | 2804:3110:7ff8::/45 | No route object for it. A route object for 2804:3110::/33 with origin AS264990 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264990 in the RIR database for the space. |
| ROA: none | 2804:3110:8000::/33 | No ROA covers it. Add a ROA for AS264990, maxLength 33. |
| Route object: none | 2804:3110:8000::/33 | No route object for it. A route object for 2804:3110::/32 with origin AS264990 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264990 in the RIR database for the space. |
| ROA: none | 2804:3110:8008::/45 | No ROA covers it. Add a ROA for AS264990, maxLength 45. |
| Route object: none | 2804:3110:8008::/45 | No route object for it. A route object for 2804:3110::/32 with origin AS264990 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264990 in the RIR database for the space. |
| ROA: none | 170.84.20.0/22 | No ROA covers it. Add a ROA for AS264990, maxLength 22. |
| Route object: RIR | 170.84.20.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.84.22.0/23 | No ROA covers it. Add a ROA for AS264990, maxLength 23. |
| Route object: RIR | 170.84.22.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:3110::/33 | No ROA covers it. Add a ROA for AS264990, maxLength 33. |
| Route object: RIR | 2804:3110::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:3110::/32 | No ROA covers it. Add a ROA for AS264990, maxLength 32. |
| Route object: RIR | 2804:3110::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264990 whose prefix no peer sees AS264990 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.84.20.0/24 | RADB | No ROA |
| 170.84.21.0/24 | RADB | No ROA |
| 170.84.22.0/24 | RADB | No ROA |
| 170.84.23.0/24 | 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.