Oneflow incident

Service interruption due to database failure

Resolved after 1 minute, affecting Current status by service (Platform (API)) and Current status by service (Platform (Application)), on November 9, 2026.

investigating Nov 09, 2026, 11:04 AM UTC

Our primary database on AWS unexpectedly failed, triggering an automatic switch to our standby database in a separate data centre. The switch took approximately 60 seconds, during which some users may have experienced errors or interruptions. No data was lost. Thank you for your understanding and please reach out if you have any additional problems.

Started
Nov 09, 2026, 11:04 AM UTC
Resolved
Nov 09, 2026, 11:05 AM UTC
Duration
1m
Detected by Pingoru
Nov 09, 2026, 11:04 AM UTC

Affected components

Current status by service (Platform (API))Current status by service (Platform (Application))

Update timeline

  1. investigating Nov 09, 2026, 11:04 AM UTC

    Our primary database on AWS unexpectedly failed, triggering an automatic switch to our standby database in a separate data centre. The switch took approximately 60 seconds, during which some users may have experienced errors or interruptions. No data was lost. Thank you for your understanding and please reach out if you have any additional problems.

  2. resolved Nov 09, 2026, 11:05 AM UTC

    All systems are back to normal

Your product runs on more than Oneflow

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →