Today some API endpoints experienced increased response times and intermittent timeout errors (504).

The incident was caused by a sudden threefold increase in incoming traffic, which led to higher-than-expected concurrent request processing and temporary resource saturation.

Mitigation steps:
We adjusted internal concurrency limits and optimized request handling to better absorb traffic spikes and prevent cascading timeouts under load.

Current status:
All services are now operating normally and stably. No ongoing impact has been observed.

We apologize for any inconvenience caused and will continue to closely monitor the system.

app-staging.flowconnect.cloud went down.

app-staging.flowconnect.cloud recovered.

app.flowconnect.cloud recovered.

app.flowconnect.cloud went down.

app.flowconnect.cloud recovered.

app-staging.flowconnect.cloud went down.

app.flowconnect.cloud went down.

app.flowconnect.cloud recovered.

app.flowconnect.cloud went down.

app.flowconnect.cloud recovered.

app.flowconnect.cloud went down.

app.flowconnect.cloud recovered.

app.flowconnect.cloud went down.

app.flowconnect.cloud recovered.

app.flowconnect.cloud went down.

app.flowconnect.cloud recovered.

app.flowconnect.cloud went down.

app.flowconnect.cloud recovered.

app.flowconnect.cloud went down.

app.flowconnect.cloud recovered.

app.flowconnect.cloud went down.

app.flowconnect.cloud recovered.

app.flowconnect.cloud went down.