Network · data from 2026-11-12
AS207656 Ukrainian Data Network
Registry name: EPINATURA Epinatura LLC, UA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207656, 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.
| 193.218.118.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.218.119.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a0f:e586::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS207656: AS-UKDANE. 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 (AS207656 isn't in the set, or no route object for AS207656 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 | AS207656 in it | Not covered |
|---|---|---|---|---|---|
| AS-UKDANE | RIPElists itself further down19 member sets in no database: AS-AIRSPROJECT, AS-IPV6GO, AS-MNG, AS-PIXOOF, AS-SERVOSPHERE … | 1,443 | 252 | 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 21 are in fix.csv.
- AS-SET: missing member19
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-AIRSPROJECT; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-IPV6GO; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-MNG; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-PIXOOF; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-SERVOSPHERE; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-SHIZUKUGLOBAL-EUROPE; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-SVINE; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-THINCO; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-TIS; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-VERSADC; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS-ZH-NET; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS200372:AS-DORFHOSTER-SET; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS212178:AS-SANTIAGO; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS214543:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS215364:AS-KKC-NETWORK; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS216324:AS-HN-NET; no IRR database read has it. |
| AS-SET: missing member | AS-UKDANE | AS-UKDANE (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it. |
Route objects not announced
Route objects with origin AS207656 whose prefix no peer sees AS207656 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.218.118.0/23 | RIPE | No ROA |
| 2a0f:e580:a::/48 | 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.