Network · data from 2026-11-12
AS206281 Vimexx
Registry name: AS-ZXCS Stichting DIGI NL, NL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206281, 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.
| 2a02:f5c0::/32 | No ROA | Nonecovered by 2a02:f5c0::/29 | 635 100% |
| 185.220.173.0/24 | Valid | Nonecovered by 185.220.172.0/22 | 673 100% |
| 185.220.174.0/24 | Valid | Nonecovered by 185.220.172.0/22 | 673 100% |
| 2a0a:4f80::/32 | Valid | Nonecovered by 2a0a:4f80::/29 | 635 100% |
| 185.104.28.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.104.29.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.104.30.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.104.31.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.177.144.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.220.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.220.175.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a06:2ec0::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS206281: AS-ZXCS. 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 (AS206281 isn't in the set, or no route object for AS206281 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 | AS206281 in it | Not covered |
|---|---|---|---|---|---|
| AS-ZXCS | RIPE | 2 | 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 10 are in fix.csv.
- ROA: none1
- Route object: none4
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a02:f5c0::/32 | No ROA covers it. Add a ROA for AS206281, maxLength 32. |
| Route object: none | 2a02:f5c0::/32 | No route object for it. A route object for 2a02:f5c0::/29 with origin AS206281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206281 in the RIR database for the space. |
| Route object: none | 185.220.173.0/24 | No route object for it. A route object for 185.220.172.0/22 with origin AS206281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206281 in the RIR database for the space. |
| Route object: none | 185.220.174.0/24 | No route object for it. A route object for 185.220.172.0/22 with origin AS206281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206281 in the RIR database for the space. |
| Route object: none | 2a0a:4f80::/32 | No route object for it. A route object for 2a0a:4f80::/29 with origin AS206281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206281 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206281 whose prefix no peer sees AS206281 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.177.144.0/22 | RIPE | Valid |
| 185.220.172.0/22 | RIPE | No ROA |
| 2a02:f5c0::/29 | RIPE | No ROA |
| 2a0a:4f80::/29 | RIPE | No ROA |
| 2a0c:5e40::/29 | 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.