Summary
- RIPE records DORIS as a Ukrainian LIR and AS8343 as assigned, with policy text naming upstreams, exchanges, customers and customer-controlled BGP communities.
- RIPEstat marked AS8343 unannounced and returned no prefixes or neighbours in the observed September 2026 window; its prefix result excludes routes with very low RIS visibility.
- These records answer different questions. The registry shows an administrative and policy surface; the observation shows what the selected collectors could see at a stated time.
- Buyers and counterparties should verify current origins, sessions, facilities, contacts and service responsibility before treating the registered policy as an operating topology.
The most striking thing about DORIS is not a traffic number. It is the gap between two forms of evidence. The RIPE aut-num object for AS8343 contains a detailed vocabulary for controlling routes. The RIPEstat AS overview, by contrast, marked the ASN as not announced at its 5 September 2026 observation time.
The administrative identity remains clear. The RIPE member page names Private joint-stock company (PrJSC) DORIS as a Ukrainian member. The organisation object identifies ORG-JcD1-RIPE with the same legal name, country code UA, LIR status and registration number 22000319. Its last-modified timestamp is 13 May 2026. Those are registry facts, not evidence of retail activity or traffic.
AS8343’s object is unusually useful because it exposes intended controls. It names AS13249 and AS35320 as upstreams. It includes policy references for UA-IX, DTEL-IX, DATA-IX and EUNIC-IX route sets. It also lists customer entries for AS39300, AS50576, AS50981, AS57025 and AS203430. A reader can therefore see how the registered policy distinguishes upstream, exchange and customer paths.
The community section goes further. The object documents values that change local preference, tag the source of customer routes, prepend toward either named upstream, prepend toward all upstreams or all exchanges, suppress selected announcements, and blackhole /32 routes with community 8343:666. This is a control vocabulary: it tells a customer what actions the policy claims to support. It does not show that the sessions, counterparties or controls are active now.
That limitation becomes material when the observation layer is added. The bounded RIPEstat prefix response returned no AS8343 prefixes for 22 August to 5 September 2026. The response also states that routes seen by fewer than ten RIS full-feed peers are excluded. The neighbour response returned zero observed neighbours at its 5 September timestamp.
Zero in these datasets is bounded evidence, not a corporate verdict. It does not establish that DORIS has ceased operating, that no customer can reach any service, or that no route exists in any collector or private interconnection. An origin may have changed; routes may sit below the visibility threshold; services may have migrated; or registry policy may simply be stale. The public sources reviewed here do not resolve those possibilities.
A second DORIS-linked object illustrates why timestamps matter. AS12933 is named Donbass-IX, is tied to the same organisation, and records an import from AS8343. Its last-modified timestamp is in 2017. That object establishes a registered relationship at the policy layer. It cannot establish the exchange’s present operating role.
For due diligence, the registered policy is still valuable. It provides a checklist: which ASN originates customer routes today; which upstream and exchange sessions are established; whether the documented communities are accepted; which organisation handles incidents; and whether customers were migrated to another origin. Current looking-glass output, route-collector coverage, session confirmation and direct operator documentation can answer those questions. The registry object tells investigators where to look, but not what they will find.
Sources
RIPE member record; RIPE organisation object; RIPE AS8343 object; RIPE AS12933 object; RIPEstat AS overview; RIPEstat bounded prefixes; RIPEstat neighbours.
Member Briefing
Deeper Profile Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock profile briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance
