Incidents and maintenance reported on status page for Curviate https://status.curviate.com/ https://d1lppblt9t2x15.cloudfront.net/logos/346d6ec3b448e59d9ed1132949a36e90.png https://status.curviate.com/ en https://status.curviate.com/incident/1097501 Wed, 21 Oct 2026 16:29:44 -0000 https://status.curviate.com/incident/1097501#73fc65f9d2eb14cc72fd00aebe7952f3d450aafdb3c32e81380d2c393a6b0a16 Incident Resolved 16:25 UTC: the API and dashboard are available again. Root cause: during a platform-wide incident at our cloud hosting provider, our application stopped completing live requests at about 12:00 UTC while its database and other services stayed healthy. The provider blocked restarts for most of its incident; once a restart went through at 16:24 UTC, service recovered immediately on the same release. No data was lost. We are reviewing how to detect and recover from this faster, and will follow up with the provider. We apologise for the disruption. https://status.curviate.com/incident/1097501 Wed, 21 Oct 2026 16:15:41 -0000 https://status.curviate.com/incident/1097501#7dc8ec56f1d3002ff39a01c9cbfabcc2c5b550e73c4cb129f1ec1d18ecef8512 Incident Update 16:15 UTC: the API and signed-in dashboard are still unavailable. Our hosting provider has not yet resolved its platform-wide incident, and it is still refusing the restart that restores our service. We retry every five minutes and have escalated directly with the provider. Our database remains healthy and your data is safe. Next update by 17:30 UTC, or sooner when service is restored. https://status.curviate.com/incident/1097501 Wed, 21 Oct 2026 15:26:28 -0000 https://status.curviate.com/incident/1097501#750432d9ddda305b15b331ebb6b4dfd9e2d26895e7ae716244f816762da8133d Incident Since 12:00 UTC today, the Curviate API and the signed-in dashboard are not responding. Requests time out, and connected tools and agents cannot reach the API. Our marketing site and documentation are not affected. Cause: our cloud hosting provider is in a major platform-wide incident that started at 07:24 UTC. Around 12:00 UTC our application lost the ability to complete live requests, even though our database and other services are healthy. Nothing was deployed or changed on our side. What we are doing: the fix is a restart of the application, and we have it ready. The provider is currently refusing restarts while their incident is ongoing. We are retrying every few minutes and have escalated directly with the provider. Your data is safe: our database is healthy and unaffected. Scheduled work resumes as soon as service is restored. Next update by 16:30 UTC, or sooner when service is restored.