Network · data from 2026-11-12
AS56683 EXNESS (NZ)
Registry name: EXNESS-AS EXNESS LIMITED, NZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56683, 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.
| 102.211.233.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 31.56.60.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 61.15.236.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 193.194.116.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 45.40.117.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.114.188.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 45.133.132.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.133.133.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 151.243.233.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 103.72.103.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 193.194.117.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 193.194.118.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 193.194.119.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS56683: AS56683. 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 (AS56683 isn't in the set, or no route object for AS56683 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 | AS56683 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS56683 | A single AS number, not a set: AS56683 (this network), 18 route objects. | |||||
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.
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 102.211.233.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS56683 whose prefix no peer sees AS56683 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.133.134.0/24 | RIPE | No ROA |
| 82.25.11.0/24 | RIPE | Valid |
| 168.222.47.0/24 | RIPE | Valid |
| 193.194.116.0/24 | RADB, RIPE | Valid |
| 2001:470:560::/48 | ARIN | Valid |
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.