Network · data from 2026-11-12
AS62104 CSISP Computer Service Internet Service Provider S.L.
Registry name: CSISP Computer Service Internet Service Provider S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62104, 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.
| 185.47.212.0/24 | Valid | Nonecovered by 185.47.212.0/22 | 673 100% |
| 185.47.213.0/24 | Valid | Nonecovered by 185.47.212.0/22 | 673 100% |
| 185.47.214.0/24 | Valid | Nonecovered by 185.47.212.0/22 | 672 100% |
| 185.47.215.0/24 | Valid | Nonecovered by 185.47.212.0/22 | 672 100% |
| 185.67.76.0/24 | Valid | Nonecovered by 185.67.76.0/22 | 672 100% |
| 185.67.77.0/24 | Valid | Nonecovered by 185.67.76.0/22 | 672 100% |
| 185.67.78.0/24 | Valid | Nonecovered by 185.67.76.0/22 | 672 100% |
| 185.47.212.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.67.76.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2a01:91e0::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS62104 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 7 are in fix.csv.
- Route object: none7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.47.212.0/24 | No route object for it. A route object for 185.47.212.0/22 with origin AS62104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62104 in the RIR database for the space. |
| Route object: none | 185.47.213.0/24 | No route object for it. A route object for 185.47.212.0/22 with origin AS62104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62104 in the RIR database for the space. |
| Route object: none | 185.47.214.0/24 | No route object for it. A route object for 185.47.212.0/22 with origin AS62104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62104 in the RIR database for the space. |
| Route object: none | 185.47.215.0/24 | No route object for it. A route object for 185.47.212.0/22 with origin AS62104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62104 in the RIR database for the space. |
| Route object: none | 185.67.76.0/24 | No route object for it. A route object for 185.67.76.0/22 with origin AS62104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62104 in the RIR database for the space. |
| Route object: none | 185.67.77.0/24 | No route object for it. A route object for 185.67.76.0/22 with origin AS62104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62104 in the RIR database for the space. |
| Route object: none | 185.67.78.0/24 | No route object for it. A route object for 185.67.76.0/22 with origin AS62104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62104 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS62104 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.