Synthflow AI Outage History

Synthflow AI is up right now

Synthflow AI had 3 outages in the last 2 years totaling 2h 27m of downtime, averaging 0.1 incidents per month.

There were 3 Synthflow AI outages since August 7, 2026 totaling 2h 27m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.synthflow.ai

Minor September 7, 2026

Login issue affecting white-label workspaces

Detected by Pingoru
Sep 07, 2026, 01:15 PM UTC
Resolved
Sep 07, 2026, 03:42 PM UTC
Duration
2h 27m
Affected: Synthflow Dashboard
Timeline · 2 updates
  1. investigating Sep 07, 2026, 01:15 PM UTC

    Status: Investigating We are aware of an issue preventing end users from logging in to white-label workspaces, those configured with a customer’s own domain and branding. This issue is limited to custom-domain workspaces. All other services are operating normally. Affected components Synthflow Dashboard (Degraded performance)

  2. resolved Sep 07, 2026, 03:42 PM UTC

    Status: Resolved This issue is now resolved. RCA: Impact: Users were unable to log in to white-label workspaces using custom domains. Standard workspaces were unaffected. Root cause: A change introduced during an internal migration caused an expected issue affecting only custom domain workspaces. Resolution: We have applied the fix, and introduced enhanced QA processes specific for custom domain workspaces We apologise for the disruption. Affected components Synthflow Dashboard (Operational)

Read the full incident report →

Minor August 17, 2026

Call failures and degraded performance on call transfers

Detected by Pingoru
Aug 17, 2026, 08:17 AM UTC
Resolved
Aug 17, 2026, 08:17 AM UTC
Duration
–
Timeline · 1 update
  1. resolved Aug 17, 2026, 08:17 AM UTC

    Status: Resolved What happened A change to our internal telephony configuration was rolled out to production and introduced an unexpected fault in call routing. What was affected • EU region: calls failed from 10:32–10:44 UTC (12:32–12:44 CEST) — 12 minutes. • US region: calls failed from 10:33–10:42 UTC (12:33–12:42 CEST) — 9 minutes. • All regions: warm transfers failed intermittently from 07:00–10:42 UTC (09:00–12:42 CEST) — 3 hours 42 minutes. All services were fully restored by 10:44 UTC. No customer data was affected. What we're doing next We have rolled back the change and added a pre-deployment check to catch this class of routing fault before it reaches production. A full root cause analysis will be published here shortly. We're sorry for the disruption.

Read the full incident report →