Network · data from 2026-11-12
AS205917 SAS Global Communications
Registry name: sas_glcom Fluidone Ltd., GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205917, 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.
| 5.53.64.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 5.53.86.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 5.53.95.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.91.84.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.91.84.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.91.86.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.91.86.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.233.108.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.233.108.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.233.109.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS205917: AS-SAS. 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 (AS205917 isn't in the set, or no route object for AS205917 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 | AS205917 in it | Not covered |
|---|---|---|---|---|---|
| AS-SAS | RIPE | 1 | 1 | 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 13 are in fix.csv.
- ROA: none10
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.53.64.0/19 | No ROA covers it. Add a ROA for AS205917, maxLength 19. |
| ROA: none | 5.53.86.0/23 | No ROA covers it. Add a ROA for AS205917, maxLength 23. |
| ROA: none | 5.53.95.0/24 | No ROA covers it. Add a ROA for AS205917, maxLength 24. |
| ROA: none | 185.91.84.0/22 | No ROA covers it. Add a ROA for AS205917, maxLength 22. |
| ROA: none | 185.91.84.0/23 | No ROA covers it. Add a ROA for AS205917, maxLength 23. |
| ROA: none | 185.91.86.0/23 | No ROA covers it. Add a ROA for AS205917, maxLength 23. |
| ROA: none | 185.91.86.0/24 | No ROA covers it. Add a ROA for AS205917, maxLength 24. |
| ROA: none | 185.233.108.0/23 | No ROA covers it. Add a ROA for AS205917, maxLength 23. |
| ROA: none | 185.233.108.0/24 | No ROA covers it. Add a ROA for AS205917, maxLength 24. |
| ROA: none | 185.233.109.0/24 | No ROA covers it. Add a ROA for AS205917, maxLength 24. |
Route objects not announced
Route objects with origin AS205917 whose prefix no peer sees AS205917 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.53.84.0/23 | RIPE | No ROA |
| 185.233.108.0/22 | RIPE | No ROA |
| 2a00:f0c0::/32 | RIPE | 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.