Flow public status
All systems stable · Tenant: global · Senast uppdaterad 17 juni 2026 07:28
Public status recovery path
When customers check the public page, the next step should be the incident history, monthly report or reliability console without any extra hunting.
Keep uptime, ETA and incident context together.
Open the incident lane or trust center directly.
Move to the report pack once the signal is stable.
Public recovery path
This gives people one place to see what is happening, what the recovery timeline is and where the next update will land.
Open the live incident history if something is active.
Share the current ETA and the next update time.
Export the status pack when the situation is stable.
Status strip
Give customers one calm place to see what is affected, what is recovering and when the next update lands.
All systems stable
stable
17 juni 2026 11:28
All systems stable
Public page for customers and stakeholders.
stable
Next update at 17 juni 2026 11:28.
68%
Flow execution progress and platform readiness.
Work next
Stable status can be shared as a customer-facing history pack.
Export status pack
Public trust should always point customers to the next useful record: an incident, a report or an export pack.
Status strip
Give customers one calm place to see what is affected, what is recovering and when the next update lands.
All systems stable
stable
17 juni 2026 11:28
A short customer-facing explanation of what is happening now.
| Lane | Impact | Status | Recovery ETA | Open |
|---|---|---|---|---|
| Runtime | No known runtime impact | ok | stable | Open |
| Queue pressure | 0 pending / 0 failed / 0 retrying | ok | stable | Open |
| Payments | 0 pending / 0 failed / 0 mismatches | ok | stable | Open |
| Trust and security | 0 critical / 0 open findings | ok | stable | Open |
If an issue is active, the next update time and recovery ETA are shown here.
Customer-impacting failures in payments or support queues are handled before any less urgent work.
The incident history page keeps a readable timeline of what happened and what was recovered.
High-level commitments that customers can use without asking support.
| Commitment | Current | Status | Note |
|---|---|---|---|
| Uptime | 8h 46m | ok | Public status is updated from live runtime health. |
| p95 latency | 440 ms | ok | Measured from current probe snapshots. |
| Recovery ETA | stable | ok | Estimated from queue, payments and trust signals. |
| Incident history | No active incident | ok | Full timeline available on the incident history page. |
Monthly report, incident history and public export packs now tell the same story so customers do not have to chase support.
We post recovery notes, not technical noise, and keep the readable history pack aligned with what the customer actually sees.
17 juni 2026 11:28