Network · data from 2026-11-12
AS49318 ARC-AS-UK Telefonica Tech UK Limited
Registry name: ARC-AS-UK Telefonica Tech UK Limited, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49318, 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.
| 194.110.130.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 188.93.176.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 188.93.178.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 188.93.180.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 188.93.182.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.110.124.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.110.124.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.28.248.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.248.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.248.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.249.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.250.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.250.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.251.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.252.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.253.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.254.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.254.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.255.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.93.176.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 188.93.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.93.177.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.93.178.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.93.179.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.93.180.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.93.181.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.93.182.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.93.183.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.110.125.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS49318 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 9 are in fix.csv.
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 194.110.130.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49318 whose prefix no peer sees AS49318 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.28.248.0/22 | RIPE | Invalid: maxLength |
| 46.28.252.0/22 | RIPE | Invalid: maxLength |
| 188.93.176.0/22 | RIPE | Invalid: maxLength |
| 188.93.180.0/22 | RIPE | Invalid: maxLength |
| 194.110.124.0/25 | RIPE | Invalid: maxLength |
| 194.110.124.128/25 | RIPE | Invalid: maxLength |
| 194.110.125.0/25 | RIPE | Invalid: maxLength |
| 194.110.125.128/25 | RIPE | Invalid: maxLength |
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.