Blog on Perstat

Evidence behind DORA incident reporting deadlines

Tue, 21 Jul 2026 00:00:00 +0200

It is 02:40 UTC. One of Perstat’s 11 regional check types reports a failure against your payments API from Frankfurt. Further plan-selected regions report the same result, and the configured regional policy confirms the incident.

That confirmation creates an operational timestamp. It does not classify the incident under DORA. If your organization classifies it as a major ICT-related incident, DORA’s reporting deadlines apply.

The hard part is not only writing the reports but assembling their inputs while the clock runs. A monitoring record can contribute detection, confirmation, and recovery times. By itself, it cannot supply legal classification, customer or transaction impact, root cause, or the reporting decision.

Leave Opsgenie before 5 April 2027

Tue, 21 Jul 2026 00:00:00 +0200

If you run on-call in Opsgenie, you have a fixed date on the calendar and one decision to make before it.

The guidance below is vendor-neutral and covers four topics:

what leaves with the product
what to inventory
the order that keeps you covered while you move
how to size the effort

Perstat appears at the end, under the consolidation question, not as the premise.

Two dates set your timeline

Atlassian ended new sales on 4 June 2025 and will end support on 5 April 2027. Existing customers can add seats until 5 April 2027 and renew only if the term ends before that date, according to the licensing page.

Three questions that test SLA reports

Tue, 21 Jul 2026 00:00:00 +0200

The number at the top of an SLA report is a claim: 99.95%, this quarter, on the record. A customer, procurement reviewer, auditor, or regulator may ask a harder question: how do you know? Their required evidence and conclusion depend on their scope.

That question matters in regulated work. DORA has applied since 17 January 2025, and NIS2 sets incident-reporting duties for entities within its scope.