Network · data from 2026-11-12
AS213954 GTS-AS Global Transit Systems LLC
Registry name: GTS-AS Global Transit Systems LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213954, 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.
| 102.64.120.0/24 | No ROA | RIR databaseAFRINIC | 671 100% |
| 45.133.112.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.133.113.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.133.114.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.133.115.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.147.8.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.147.9.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.147.10.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.147.11.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.159.23.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 77.95.172.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 104.245.240.0/22 | Valid | RIR databaseARIN | 671 100% |
| 157.22.16.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.17.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.18.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.19.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.44.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.45.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.46.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.47.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.72.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.73.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.74.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.75.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.100.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.101.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.102.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.103.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.124.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.125.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.126.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.22.127.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 172.83.252.0/22 | Valid | RIR databaseARIN | 671 100% |
| 176.126.111.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.168.28.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.168.30.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.201.136.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.201.138.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 193.31.127.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.142.36.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.142.37.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.142.38.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.142.39.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 216.40.72.0/22 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS213954 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 6 are in fix.csv.
- ROA: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 102.64.120.0/24 | No ROA covers it. Add a ROA for AS213954, maxLength 24. |
Route objects not announced
Route objects with origin AS213954 whose prefix no peer sees AS213954 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 146.19.39.0/24 | RIPE | Valid |
| 146.19.39.0/25 | RIPE | Invalid: maxLength |
| 146.19.39.128/25 | RIPE | Invalid: maxLength |
| 176.126.111.0/25 | RIPE | Invalid: maxLength |
| 176.126.111.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.