Network · data from 2026-11-12
AS273829 AS273829 - VISION SATELITAL COMUNICACIONES S.A.S.
Registry name: AS273829 - VISION SATELITAL COMUNICACIONES S.A.S., CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS273829, 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.15.2.0/24 | Invalid: origin | None | 2 0%low visibility |
| 185.229.216.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2801:159::/44 | Valid | RIR databaseLACNIC, RADB | 635 100% |
AS-SET
AS273829 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 5 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 190.15.2.0/24 | ROAs covering it name AS27817, not AS273829. If AS273829 should announce it, add a ROA for AS273829. |
| Route object: none | 190.15.2.0/24 | No route object for it. Add a route object with origin AS273829 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS273829 whose prefix no peer sees AS273829 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 153.51.250.0/24 | RIPE | Valid |
| 190.15.3.0/24 | LACNIC | Valid |
| 2803:7150::/32 | RADB | 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.