Network · data from 2026-11-12
AS20932 SIG Telecom
Registry name: SIG-ST Services Industriels de Geneve, CH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20932, 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.68.204.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.11.221.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.169.128.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 217.169.144.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 2001:41e0::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS20932: AS-SIG-TELECOM. 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 (AS20932 isn't in the set, or no route object for AS20932 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 | AS20932 in it | Not covered |
|---|---|---|---|---|---|
| AS-SIG-TELECOM | RIPE | 12 | 2 | Yes | 0 |
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS20932 is announced.
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.