Network · data from 2026-11-12
AS271817 AS271817 - S.E.A. COMPUTACION SOLUCIONES TECNOLOGICAS SPA
Registry name: AS271817 - S.E.A. COMPUTACION SOLUCIONES TECNOLOGICAS SPA, CL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271817, 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.
| 2803:dbe0:1::/48 | Valid | Nonecovered by 2803:dbe0::/36 | 9 1%low visibility |
| 2803:dbe0:2::/48 | Valid | Nonecovered by 2803:dbe0::/36 | 9 1%low visibility |
| 2803:dbe0:3::/48 | Valid | Nonecovered by 2803:dbe0::/36 | 9 1%low visibility |
| 2803:dbe0:4::/48 | Valid | Nonecovered by 2803:dbe0::/36 | 9 1%low visibility |
| 2803:dbe0:5::/48 | Valid | Nonecovered by 2803:dbe0::/36 | 9 1%low visibility |
| 2803:dbe0:6::/48 | Valid | Nonecovered by 2803:dbe0::/36 | 9 1%low visibility |
| 179.51.168.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 179.51.169.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 179.51.170.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 179.51.171.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 179.51.168.0/22 | Valid | RIR databaseALTDB, LACNIC, RADB | 672 100% |
| 2803:dbe0::/36 | Valid | RIR databaseLACNIC | 634 100% |
AS-SET
AS271817 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 13 are in fix.csv.
- Route object: none6
- Route object: RIR4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:dbe0:1::/48 | No route object for it. A route object for 2803:dbe0::/36 with origin AS271817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271817 in the RIR database for the space. |
| Route object: none | 2803:dbe0:2::/48 | No route object for it. A route object for 2803:dbe0::/36 with origin AS271817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271817 in the RIR database for the space. |
| Route object: none | 2803:dbe0:3::/48 | No route object for it. A route object for 2803:dbe0::/36 with origin AS271817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271817 in the RIR database for the space. |
| Route object: none | 2803:dbe0:4::/48 | No route object for it. A route object for 2803:dbe0::/36 with origin AS271817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271817 in the RIR database for the space. |
| Route object: none | 2803:dbe0:5::/48 | No route object for it. A route object for 2803:dbe0::/36 with origin AS271817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271817 in the RIR database for the space. |
| Route object: none | 2803:dbe0:6::/48 | No route object for it. A route object for 2803:dbe0::/36 with origin AS271817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271817 in the RIR database for the space. |
| Route object: RIR | 179.51.168.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.51.169.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.51.170.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.51.171.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271817 whose prefix no peer sees AS271817 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.51.168.0/23 | RADB | Valid |
| 179.51.170.0/23 | RADB | Valid |
| 2803:dbe0::/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.