Network · data from 2026-11-12
AS58327 GLOBE-OPERATOR-TELECOM FIBERGREEN TECNOLOGICAS S.L.
Registry name: GLOBE-OPERATOR-TELECOM FIBERGREEN TECNOLOGICAS S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58327, 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.
| 154.58.212.0/22 | No ROA | None | 672 100% |
| 38.137.168.0/21 | No ROA | None | 91 14% |
| 5.252.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 81.172.40.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 81.172.88.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 81.172.104.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 81.172.104.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 81.172.120.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.150.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.150.37.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.150.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.150.42.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.120.168.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.74.193.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.74.194.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.74.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.194.25.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.221.191.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.224.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.224.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.226.228.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.230.144.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.232.135.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.239.4.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 188.212.32.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.242.188.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 81.172.103.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.172.108.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 94.101.124.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 2a09:4e40::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS58327 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 49 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced45
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.58.212.0/22 | No ROA covers it. Add a ROA for AS58327, maxLength 22. |
| Route object: none | 154.58.212.0/22 | No route object for it. Add a route object with origin AS58327 in the RIR database for the space. |
| ROA: none | 38.137.168.0/21 | No ROA covers it. Add a ROA for AS58327, maxLength 21. |
| Route object: none | 38.137.168.0/21 | No route object for it. Add a route object with origin AS58327 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58327 whose prefix no peer sees AS58327 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.252.252.0/24 | RIPE | Valid |
| 5.252.253.0/24 | RIPE | Valid |
| 5.252.254.0/24 | RIPE | Valid |
| 5.252.255.0/24 | RIPE | Valid |
| 81.172.40.0/23 | RIPE | Valid |
| 81.172.40.0/24 | RIPE | Valid |
| 81.172.41.0/24 | RIPE | Valid |
| 81.172.42.0/23 | RIPE | Valid |
| 81.172.42.0/24 | RIPE | Valid |
| 81.172.43.0/24 | RIPE | Valid |
| 81.172.88.0/22 | RIPE | Valid |
| 81.172.88.0/24 | RIPE | Valid |
| 81.172.89.0/24 | RIPE | Valid |
| 81.172.90.0/24 | RIPE | Valid |
| 81.172.91.0/24 | RIPE | Valid |
| 81.172.92.0/22 | RIPE | Valid |
| 81.172.92.0/24 | RIPE | Valid |
| 81.172.93.0/24 | RIPE | Valid |
| 81.172.94.0/24 | RIPE | Valid |
| 81.172.95.0/24 | RIPE | Valid |
| 81.172.104.0/24 | RIPE | Valid |
| 81.172.105.0/24 | RIPE | Valid |
| 81.172.106.0/24 | RIPE | Valid |
| 81.172.107.0/24 | RIPE | Valid |
| 81.172.108.0/24 | RIPE | Valid |
| 81.172.109.0/24 | RIPE | Valid |
| 81.172.110.0/24 | RIPE | Valid |
| 81.172.111.0/24 | RIPE | Valid |
| 81.172.120.0/22 | RIPE | Valid |
| 81.172.120.0/24 | RIPE | Valid |
| 81.172.121.0/24 | RIPE | Valid |
| 81.172.122.0/24 | RIPE | Valid |
| 81.172.123.0/24 | RIPE | Valid |
| 81.172.124.0/22 | RIPE | Valid |
| 81.172.124.0/24 | RIPE | Valid |
| 81.172.125.0/24 | RIPE | Valid |
| 81.172.126.0/24 | RIPE | Valid |
| 81.172.127.0/24 | RIPE | Valid |
| 94.101.124.0/24 | RIPE | Valid |
| 94.101.125.0/24 | RIPE | Valid |
| 94.101.126.0/24 | RIPE | Valid |
| 94.101.127.0/24 | RIPE | Valid |
| 185.74.194.0/23 | RIPE | Valid |
| 185.224.94.0/23 | RIPE | Valid |
| 185.224.95.0/24 | RIPE | Valid |
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.