Sanity Status - Incident Historyhttp://status.sanity.io
StatuspageThu, 08 Mar 2018 10:37:42 +0100Indexes offline
<p><small>Jan 31, 13:23 CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan 31, 11:59 CET</small><br><strong>Monitoring</strong> - All indexes have been regenerated, and the ElasticSearch cluster is back in normal operation. We will double-check that all indexes are fully in sync, and examine the underlying cause for the outage.</p><p><small>Jan 31, 11:38 CET</small><br><strong>Update</strong> - An ElasticSearch failure led to index corruption, we are regenerating the affected indexes. No data has been lost. Projects will be coming back online as indexes are regenerated, we expect this to be fully resolved for all projects within 20-30 minutes.</p><p><small>Jan 31, 11:35 CET</small><br><strong>Identified</strong> - We have a temporary service outage affecting our indexes.</p> Wed, 31 Jan 2018 13:23:15 +0100http://status.sanity.io/incidents/l7h8dvg8dbxr
http://status.sanity.io/incidents/l7h8dvg8dbxrIntermittent API timeouts
<p><small>Sep 29, 11:27 CEST</small><br><strong>Resolved</strong> - The intermittent API timeouts were caused by a node crash due to a bug in the Linux kernel's CFS scheduler. A kernel upgrade has been scheduled and will be carried out within the next week. This affected roughly 1.5% of requests within the given time period.</p><p><small>Sep 29, 10:57 CEST</small><br><strong>Monitoring</strong> - Users may have experienced intermittent API timeouts from about 08:42 to 08:48 UTC, possibly due to network issues. We are monitoring the situation and investigating the underlying cause.</p> Fri, 29 Sep 2017 11:27:00 +0200http://status.sanity.io/incidents/f7m3gp8mgnd7
http://status.sanity.io/incidents/f7m3gp8mgnd7Management login not working
<p><small>Sep 19, 18:19 CEST</small><br><strong>Resolved</strong> - The dashboard login issues have now been resolved, they were caused by a code change deployed at 14:38 UTC.</p><p><small>Sep 19, 18:04 CEST</small><br><strong>Investigating</strong> - Users are experiencing problems logging into the management dashboard at https://sanity.io/manage - we are investigating.</p> Tue, 19 Sep 2017 18:19:02 +0200http://status.sanity.io/incidents/gh2rzr2sq2zn
http://status.sanity.io/incidents/gh2rzr2sq2znIntermittent request timeouts in Scandinavia
<p><small>Sep 8, 18:27 CEST</small><br><strong>Resolved</strong> - There are no further indications of performance issues in Scandinavia since 15:25.</p><p><small>Sep 8, 17:47 CEST</small><br><strong>Monitoring</strong> - Users in Scandinavia have again experienced intermittent slow requests and timeouts, from about 15:00 to 15:25 UTC, caused by issues in the Google Cloud Platform edge network. There are no indications of degraded performance elsewhere. We are monitoring the situation.</p> Fri, 08 Sep 2017 18:27:50 +0200http://status.sanity.io/incidents/lkyk0vwv861k
http://status.sanity.io/incidents/lkyk0vwv861kScandinavia edge network disruptions
<p>Sanity API users in Scandinavia experienced intermittent slow responses, low transfer speeds, and request timeouts from 19:40 to 20:40 UTC. This was caused by network/load-balancing/cache issues in the Google Cloud Platform edge, and was fully resolved by 20:40 UTC.</p> Thu, 07 Sep 2017 14:00:00 +0200http://status.sanity.io/incidents/r7xs38182qm6
http://status.sanity.io/incidents/r7xs38182qm6