Network · data from 2026-11-12
AS270652 AS270652 - H.l informatica e telecon Ltda me
Registry name: AS270652 - H.l informatica e telecon Ltda me, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270652, 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.
| 190.11.208.0/24 | Valid | Nonecovered by 190.11.208.0/22 | 670 100% |
| 190.11.209.0/24 | Valid | Nonecovered by 190.11.208.0/22 | 670 100% |
| 190.11.210.0/23 | Valid | Nonecovered by 190.11.208.0/22 | 669 99% |
| 190.11.210.0/24 | Valid | Nonecovered by 190.11.208.0/22 | 669 99% |
| 2804:6f50::/40 | Valid | Nonecovered by 2804:6f50::/32 | 636 100% |
| 2804:6f50:100::/40 | Valid | Nonecovered by 2804:6f50::/32 | 634 100% |
| 190.11.211.0/24 | Valid | Nonecovered by 190.11.208.0/22 | 2 0%low visibility |
| 2804:6f50::/32 | Valid | Other IRR onlyRADB, TC | 636 100% |
AS-SET
AS270652 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 9 are in fix.csv.
- Route object: none7
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.11.208.0/24 | No route object for it. A route object for 190.11.208.0/22 with origin AS270652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270652 in the RIR database for the space. |
| Route object: none | 190.11.209.0/24 | No route object for it. A route object for 190.11.208.0/22 with origin AS270652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270652 in the RIR database for the space. |
| Route object: none | 190.11.210.0/23 | No route object for it. A route object for 190.11.208.0/22 with origin AS270652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270652 in the RIR database for the space. |
| Route object: none | 190.11.210.0/24 | No route object for it. A route object for 190.11.208.0/22 with origin AS270652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270652 in the RIR database for the space. |
| Route object: none | 2804:6f50::/40 | No route object for it. A route object for 2804:6f50::/32 with origin AS270652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270652 in the RIR database for the space. |
| Route object: none | 2804:6f50:100::/40 | No route object for it. A route object for 2804:6f50::/32 with origin AS270652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270652 in the RIR database for the space. |
| Route object: none | 190.11.211.0/24 | No route object for it. A route object for 190.11.208.0/22 with origin AS270652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270652 in the RIR database for the space. |
| Route object: RIR | 2804:6f50::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270652 whose prefix no peer sees AS270652 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.11.208.0/22 | RADB, 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.