Network · data from 2026-11-12
AS260 GTT Communications (AS260)
Registry name: GTT-DXB - GTT Americas, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS260, 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.78.161.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 185.78.163.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2605:4380::/32 | No ROA | Other IRR onlyRADB | 636 100% |
| 89.42.169.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 185.19.102.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 2a04:1123::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 78.40.204.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS260: RADB::AS-GTTDXB. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS260 isn't in the set, or no route object for AS260 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS260 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS-GTTDXB | RADB | 44 | 3 | Yes | 0 |
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.
- ROA: none6
- Route object: RIR3
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.78.161.0/24 | No ROA covers it. Add a ROA for AS260, maxLength 24. |
| Route object: RIR | 185.78.161.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 185.78.163.0/24 | No ROA covers it. Add a ROA for AS260, maxLength 24. |
| Route object: RIR | 185.78.163.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2605:4380::/32 | No ROA covers it. Add a ROA for AS260, maxLength 32. |
| Route object: RIR | 2605:4380::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 89.42.169.0/24 | No ROA covers it. Add a ROA for AS260, maxLength 24. |
| ROA: none | 185.19.102.0/24 | No ROA covers it. Add a ROA for AS260, maxLength 24. |
| ROA: none | 2a04:1123::/32 | No ROA covers it. Add a ROA for AS260, maxLength 32. |
Route objects not announced
Route objects with origin AS260 whose prefix no peer sees AS260 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.83.96.0/24 | RIPE | Invalid: origin |
| 89.42.168.0/22 | RADB | No ROA |
| 91.208.241.0/24 | RIPE | No ROA |
| 185.19.100.0/22 | RADB | No ROA |
| 185.19.100.0/23 | RIPE | No ROA |
| 185.56.88.0/22 | RADB | No ROA |
| 185.78.160.0/22 | RADB, RIPE | No ROA |
| 185.78.160.0/24 | RADB | No ROA |
| 193.223.100.0/24 | NTTCOM, RADB | 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.