Network · data from 2026-11-12
AS264621 AS264621 - BLUE SAT SERVICIOS ADMINISTRADOS DE TELECOMUNICACIONES SA
Registry name: AS264621 - BLUE SAT SERVICIOS ADMINISTRADOS DE TELECOMUNICACIONES SA, CR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264621, 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.
| 143.0.160.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 143.0.161.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 143.0.162.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 143.0.163.0/24 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
AS264621 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.
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 143.0.160.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 143.0.161.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 143.0.162.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 143.0.163.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS264621 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.