Network · data from 2026-11-12
AS206866 Gartel
Registry name: Gartel GARTEL, TELEFONIA Y COMUNICACION, S.L., ES · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206866, 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.
| 157.97.88.0/24 | Valid | Nonecovered by 157.97.88.0/21 | 672 100% |
| 157.97.93.0/24 | Valid | Nonecovered by 157.97.88.0/21 | 672 100% |
| 157.97.94.0/24 | Valid | Nonecovered by 157.97.88.0/21 | 672 100% |
| 157.97.95.0/24 | Valid | Nonecovered by 157.97.88.0/21 | 672 100% |
| 176.98.216.0/23 | Valid | Nonecovered by 176.98.216.0/22 | 672 100% |
| 185.56.180.0/24 | Valid | Nonecovered by 185.56.180.0/23 | 672 100% |
| 185.56.181.0/24 | Valid | Nonecovered by 185.56.180.0/23 | 672 100% |
| 157.97.89.0/24 | Valid | Nonecovered by 157.97.88.0/21 | 1 0%low visibility |
| 84.232.40.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 185.56.182.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 2a02:52e0::/32 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS206866's PeeringDB record names no 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 18 are in fix.csv.
- Route object: none8
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 157.97.88.0/24 | No route object for it. A route object for 157.97.88.0/21 with origin AS206866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206866 in the RIR database for the space. |
| Route object: none | 157.97.93.0/24 | No route object for it. A route object for 157.97.88.0/21 with origin AS206866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206866 in the RIR database for the space. |
| Route object: none | 157.97.94.0/24 | No route object for it. A route object for 157.97.88.0/21 with origin AS206866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206866 in the RIR database for the space. |
| Route object: none | 157.97.95.0/24 | No route object for it. A route object for 157.97.88.0/21 with origin AS206866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206866 in the RIR database for the space. |
| Route object: none | 176.98.216.0/23 | No route object for it. A route object for 176.98.216.0/22 with origin AS206866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206866 in the RIR database for the space. |
| Route object: none | 185.56.180.0/24 | No route object for it. A route object for 185.56.180.0/23 with origin AS206866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206866 in the RIR database for the space. |
| Route object: none | 185.56.181.0/24 | No route object for it. A route object for 185.56.180.0/23 with origin AS206866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206866 in the RIR database for the space. |
| Route object: none | 157.97.89.0/24 | No route object for it. A route object for 157.97.88.0/21 with origin AS206866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206866 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206866 whose prefix no peer sees AS206866 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 84.232.122.0/23 | RIPE | Valid |
| 94.24.44.0/23 | RIPE | Valid |
| 149.100.0.0/24 | RADB | No ROA |
| 149.100.1.0/24 | RADB | No ROA |
| 154.48.177.0/24 | RADB | No ROA |
| 154.61.116.0/24 | RADB | No ROA |
| 157.97.88.0/21 | RIPE | No ROA |
| 176.98.216.0/22 | RIPE | No ROA |
| 185.56.180.0/22 | RIPE | No ROA |
| 185.56.180.0/23 | RIPE | 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.