Network · data from 2026-11-12
AS268669 AS268669 - Bruno e Lemes LTDA
Registry name: AS268669 - Bruno e Lemes LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268669, 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.
| 45.164.100.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 2804:54c4::/32 | Valid | Other IRR onlyRADB, TC | 636 100% |
| 45.164.102.0/23 | Valid | Other IRR onlyTC | 206 31% |
| 45.164.100.0/23 | Valid | Other IRR onlyTC | 205 30% |
AS-SET
AS268669 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: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.164.100.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:54c4::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.164.102.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.164.100.0/23 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS268669 whose prefix no peer sees AS268669 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.164.100.0/24 | TC | Valid |
| 45.164.101.0/24 | TC | Valid |
| 45.164.102.0/24 | TC | Valid |
| 45.164.103.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.