Network · data from 2026-11-12
AS269709 AS269709 - FIBERNET ESPECIALIZADOS EM INTERNET LTDA
Registry name: AS269709 - FIBERNET ESPECIALIZADOS EM INTERNET LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269709, 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.112.144.0/23 | Valid | Nonecovered by 190.112.144.0/22 | 670 100% |
| 190.112.144.0/24 | Valid | Nonecovered by 190.112.144.0/22 | 670 100% |
| 190.112.145.0/24 | Valid | Nonecovered by 190.112.144.0/22 | 670 100% |
| 190.112.146.0/24 | Valid | Nonecovered by 190.112.144.0/22 | 670 100% |
| 190.112.147.0/24 | Valid | Nonecovered by 190.112.144.0/22 | 668 99% |
| 2804:68b0::/32 | Valid | Other IRR onlyRADB | 632 99% |
AS-SET
AS269709 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: none5
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.112.144.0/23 | No route object for it. A route object for 190.112.144.0/22 with origin AS269709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269709 in the RIR database for the space. |
| Route object: none | 190.112.144.0/24 | No route object for it. A route object for 190.112.144.0/22 with origin AS269709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269709 in the RIR database for the space. |
| Route object: none | 190.112.145.0/24 | No route object for it. A route object for 190.112.144.0/22 with origin AS269709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269709 in the RIR database for the space. |
| Route object: none | 190.112.146.0/24 | No route object for it. A route object for 190.112.144.0/22 with origin AS269709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269709 in the RIR database for the space. |
| Route object: none | 190.112.147.0/24 | No route object for it. A route object for 190.112.144.0/22 with origin AS269709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269709 in the RIR database for the space. |
| Route object: RIR | 2804:68b0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269709 whose prefix no peer sees AS269709 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.112.144.0/22 | RADB | Valid |
| 2804:68b0::/33 | RADB | Valid |
| 2804:68b0:8000::/33 | RADB | 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.