Network · data from 2026-11-12
AS209800 ZEMAGG
Registry name: ZEMAGG Philippe Simon Pflug trading as Niesmann-Pflug ZEMA GbR, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209800, 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.
| 2.27.166.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 2a0e:97c0:c10::/44 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS209800: AS209800:AS-ZEMA. 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 (AS209800 isn't in the set, or no route object for AS209800 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 | AS209800 in it | Not covered |
|---|---|---|---|---|---|
| AS209800:AS-ZEMA | RIPE | 0 | 1 | No | 2 |
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 6 are in fix.csv.
- AS-SET: own ASN1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: own ASN | AS209800:AS-ZEMA | AS209800 isn't in AS209800:AS-ZEMA (RIPE) once expanded. Add AS209800 to it. |
Route objects not announced
Route objects with origin AS209800 whose prefix no peer sees AS209800 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 155.94.179.0/24 | ARIN | Valid |
| 162.222.194.0/24 | ARIN | Valid |
| 173.254.198.0/24 | ARIN | Valid |
| 192.161.179.0/24 | ARIN | Valid |
| 216.45.51.0/24 | ARIN | Invalid: origin |
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.