Network · data from 2026-11-12
AS209906 telegilena Fibrasur Operadores S.L.
Registry name: telegilena Fibrasur Operadores S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209906, 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.238.144.0/22 | Valid | Other origin only | 673 100% |
| 5.182.164.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 5.182.164.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.182.165.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.182.166.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.182.167.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.238.144.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.238.145.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.238.146.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.238.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS209906 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 1 are in fix.csv.
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.238.144.0/22 | Route objects for it name AS29119. Add a route object with origin AS209906 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS209906 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.