Network · data from 2026-11-12
AS209824 GS Webservices
Registry name: GS Georg Kroeber, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209824, 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.
| 154.197.70.0/24 | Invalid: origin | RIR databaseAFRINIC | 2 0%low visibility |
| 5.231.72.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.231.226.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.209.52.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.209.53.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.209.54.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.209.55.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.221.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.113.54.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 77.90.1.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.90.29.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a09:9340::/30 | Valid | RIR databaseRIPE | 634 100% |
| 2a09:9344::/30 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:e700::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS209824: AS-GS. 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 (AS209824 isn't in the set, or no route object for AS209824 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 | AS209824 in it | Not covered |
|---|---|---|---|---|---|
| AS-GS | RIPE1 member set in no database: AS215110:AS-CUSTOMERS | 20 | 11 | 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 8 are in fix.csv.
- ROA: origin1
- AS-SET: missing member1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 154.197.70.0/24 | ROAs covering it name AS17561, not AS209824. If AS209824 should announce it, add a ROA for AS209824. |
| AS-SET: missing member | AS-GS | AS-GS (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS209824 whose prefix no peer sees AS209824 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.90.37.0/24 | RIPE | Invalid: origin |
| 85.209.52.0/22 | RIPE | No ROA |
| 217.113.54.0/23 | RIPE | Valid |
| 2a09:9340::/29 | RIPE | No ROA |
| 2a09:9344:0:500::/56 | RIPE | Valid |
| 2a13:e700::/56 | 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.