Network · data from 2026-11-12
AS267876 AS267876 - RAMIREZ CABLE VISION SRL
Registry name: AS267876 - RAMIREZ CABLE VISION SRL, AR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267876, 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.103.231.0/24 | Invalid: origin | None | 1 0%low visibility |
| 45.178.8.0/23 | Valid | None | 670 100% |
| 45.178.10.0/23 | Valid | None | 670 100% |
AS-SET
AS267876 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 4 are in fix.csv.
- ROA: origin1
- Route object: none3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 190.103.231.0/24 | ROAs covering it name AS27983, not AS267876. If AS267876 should announce it, add a ROA for AS267876. |
| Route object: none | 190.103.231.0/24 | No route object for it. Add a route object with origin AS267876 in the RIR database for the space. |
| Route object: none | 45.178.8.0/23 | No route object for it. Add a route object with origin AS267876 in the RIR database for the space. |
| Route object: none | 45.178.10.0/23 | No route object for it. Add a route object with origin AS267876 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS267876 is announced.
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.