Wcześniej
Pierwsza informacja władz regionalnych
Początkowo zgłoszono pożar rafinerii i pięciu rannych.
Żywa karta wydarzenia
Pożar rafinerii Ilsky
ZaktualizowanePożar ugaszono, a liczba rannych wzrosła do sześciu; wpływu na moce produkcyjne nie opublikowano.
Teraz
Późniejsza aktualizacja gaszenia i ofiar
Pożar ugaszono, a liczba rannych wzrosła do sześciu; wpływu na moce produkcyjne nie opublikowano.
Obserwacja
Czy operator lub władze opublikują harmonogram produkcji i napraw?
Pytanie uznaje się za rozwiązane, gdyPoziom produkcji wskazanego operatora i końcowe oficjalne dane o szkodach.
Dlaczego to ma znaczenie?
Pożar i ofiary zostały potwierdzone, natomiast ewentualna utrata mocy handlowych pozostała otwarta.
Co obserwujemy dalej?
Czy operator lub władze opublikują harmonogram produkcji i napraw?
Pytanie uznaje się za rozwiązane, gdyPoziom produkcji wskazanego operatora i końcowe oficjalne dane o szkodach.
Impact chain
What actually followed from the event
Each stage separates a verified consequence from an open question.
Drone-related fire at the refinery
Official records from opposing sides support the event, while the exact strike mechanism remained open.
Resolved when: The exact mechanism is established by reliable technical or official evidence. Otwórz dowody →Fire and six people wounded
The fire was confirmed and the reported wounded count rose from five to six.
Resolved when: Authorities provide a closing casualty count and the condition of those wounded. Otwórz dowody →No production-capacity loss was published
The verified record does not yet show whether production stopped or the scale of any capacity effect.
Resolved when: The operator or authorities publish the production level or a bounded capacity effect.The fire was extinguished
A later regional-authority update reported that extinguishing operations had ended.
Resolved when: This stage reopens only if the fire reignites or the response status changes. Otwórz dowody →Fire response ended; operational recovery remains open
Extinguishing the fire partially closes the physical emergency, but there is no evidence of production recovery.
Resolved when: A named operator reports resumed production and a repair timetable. Otwórz dowody →No downstream supply or market effect can yet be established
There was insufficient evidence in the report window for a transport, insurance or market effect.
Resolved when: A named company, operator or market record establishes a concrete downstream consequence.Campaign and comparison context
Bounded 7/30-day comparison
This section does not verify the event. It places the event in time and remains separate from impact-chain evidence.
The comparison is bounded to Brief Delta's own 7/30-day publication archive and to events in the same commercial-infrastructure / civilian-impact product lane. It does not add evidence about Ilsky's mechanism, capacity effect or market consequence.
The context uses only selected claim clusters from published daily reports and the living event record's current state; party campaign claims remain separate from event-level verification.
2–9 Aug editions where commercial or energy-related infrastructure passed the product selection gate.
The week included other infrastructure hits and disruptions, but the published archive does not form a unified refinery-campaign metric.
Ilsky adds a separate refinery-fire case to the week: extinguishing was established while production and supply effects remained open.
This can only be read cautiously as campaign context: the event belongs to the same infrastructure-pressure period, while its impact chain is still resolved by its own evidence.
16 Jul–9 Aug archive, the available published validation and production period.
The month contains multiple civilian and infrastructure impacts, but not a sufficient time series of refinery-capacity changes.
Ilsky is material because it joins an established physical incident with an unresolved capacity question in one dossier.
The 30-day context supports follow-up value, not a conclusion about market or supply-chain effects.
Source origin and corrections
Where the record came from and what changed
This section describes origin, republication, conflicts and corrections. It is not an impact-chain evidence stage or a 7/30-day trend interpretation.
The chain covers only the published claim's source origin, independent support, republications, conflict check and visible corrections. It does not resolve production capacity, market impact or the 7/30-day campaign interpretation.
Regional authorities opened the fire and initial casualty record
Publications traced to the Krasnodar operations-headquarters family described the refinery fire and five wounded.
The primary origin family gives the starting point, but does not by itself close mechanism or capacity impact.Opposing-side and Reuters-family support confirmed the narrow event
The Reuters-origin report placed the Russian official record beside Ukraine's separate General Staff claim of a strike.
Independent support raises confidence in the fire event, while not turning a party claim into an exact technical mechanism.Editorial chronologies preserved the origin trail
7x7 and Kommersant acted as republications whose value is preserving the origin link and chronology, not adding a new independent origin.
Republications improve auditability, but are not counted as separate confirmations.No active counter-source was present, while mechanism stayed bounded
The published claim had no contradicting source, but party records were insufficient to verify the exact strike method or production consequence.
The conflict lane tells the reader that an open question is not the same as a verified counter-claim.The casualty count moved from five to six and extinguishment was added
A later regional/district-level update corrected the reader-facing state: the fire was extinguished and six wounded were recorded.
The correction stays visible so the initial count and later closing record are not collapsed.Eksport statyczny
Pobierz dane audytu tego wydarzenia
Pliki są statycznymi artefaktami JSON/CSV. Publiczne dynamiczne API nie jest aktywne.
Zweryfikowana oś czasu
Początkowo zgłoszono pożar rafinerii i pięciu rannych.
Pożar ugaszono, a liczba rannych wzrosła do sześciu; wpływu na moce produkcyjne nie opublikowano.
Rodziny źródeł dla tej aktualizacji: Krasnodar operations headquarters · Reuters · Seversky district authority
Otwórz dowody dnia →