Network · data from 2026-11-12
AS267292 AS267292 - live.connection me ltda
Registry name: AS267292 - live.connection me ltda, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267292, 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.233.42.0/24 | No ROA | Other IRR onlyALTDB | 667 99% |
| 45.233.41.0/24 | No ROA | Other IRR onlyALTDB | 666 99% |
| 45.233.43.0/24 | No ROA | Other IRR onlyALTDB | 666 99% |
AS-SET
AS267292 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 10 are in fix.csv.
- ROA: none3
- Route object: RIR3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.233.42.0/24 | No ROA covers it. Add a ROA for AS267292, maxLength 24. |
| Route object: RIR | 45.233.42.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 45.233.41.0/24 | No ROA covers it. Add a ROA for AS267292, maxLength 24. |
| Route object: RIR | 45.233.41.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 45.233.43.0/24 | No ROA covers it. Add a ROA for AS267292, maxLength 24. |
| Route object: RIR | 45.233.43.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267292 whose prefix no peer sees AS267292 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.233.40.0/22 | ALTDB, NTTCOM, RADB, TC | No ROA |
| 45.233.40.0/24 | ALTDB, RADB | No ROA |
| 143.202.7.0/24 | RADB | No ROA |
| 2804:4b3c::/32 | ALTDB, RADB, TC | 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.