Network · data from 2026-11-12
AS36483 GT.net
Registry name: GOSSAMERTHREADS - Gossamer Threads Inc., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36483, 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.
| 172.255.54.0/24 | No ROA | None | 671 100% |
| 172.255.48.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 172.255.52.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 199.10.28.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 204.187.12.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 208.70.244.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS36483: AS-GTI. 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 (AS36483 isn't in the set, or no route object for AS36483 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 | AS36483 in it | Not covered |
|---|---|---|---|---|---|
| AS-GTI | RADB | 1 | 1 | No | 6 |
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 24 are in fix.csv.
- ROA: none6
- Route object: none1
- Route object: RIR5
- AS-SET: own ASN1
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 172.255.54.0/24 | No ROA covers it. Add a ROA for AS36483, maxLength 24. |
| Route object: none | 172.255.54.0/24 | No route object for it. Add a route object with origin AS36483 in the RIR database for the space. |
| ROA: none | 172.255.48.0/22 | No ROA covers it. Add a ROA for AS36483, maxLength 22. |
| Route object: RIR | 172.255.48.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 172.255.52.0/23 | No ROA covers it. Add a ROA for AS36483, maxLength 23. |
| Route object: RIR | 172.255.52.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.10.28.0/22 | No ROA covers it. Add a ROA for AS36483, maxLength 22. |
| Route object: RIR | 199.10.28.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 204.187.12.0/22 | No ROA covers it. Add a ROA for AS36483, maxLength 22. |
| Route object: RIR | 204.187.12.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.70.244.0/22 | No ROA covers it. Add a ROA for AS36483, maxLength 22. |
| Route object: RIR | 208.70.244.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS-GTI | AS36483 isn't in AS-GTI (RADB) once expanded. Add AS36483 to it. |
Route objects not announced
Route objects with origin AS36483 whose prefix no peer sees AS36483 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 74.3.186.0/24 | RADB | No ROA |
| 162.245.240.0/21 | RADB | No ROA |
| 162.245.240.0/23 | RADB | No ROA |
| 172.255.56.0/23 | RADB | No ROA |
| 172.255.58.0/24 | RADB | No ROA |
| 172.255.60.0/22 | RADB | No ROA |
| 192.214.103.0/24 | RADB | No ROA |
| 2607:fcc0::/35 | RADB | No ROA |
| 2607:fcc0:2000::/35 | RADB | No ROA |
| 2607:fcc0:4000::/35 | RADB | No ROA |
| 2607:fcc0:8000::/35 | 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.