Duration: 2 minutes

Affected Components: , ,

May 27, 05:22:00 GMT+0
Resolved - The issue was caused by an automated failover that occurred in our KV infrastructure hosted on AWS, which led to temporary increase in 5XX errors. The system detected an issue with primary nodes and automatically promoted replicas to maintain service continuity. The failover completed automatically, and all systems recovered without manual intervention..

May 27, 05:20:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 3 minutes

Affected Components:

Mar 26, 14:33:47 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Mar 26, 14:30:56 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 2 minutes

Affected Components: ,

Dec 30, 11:36:00 GMT+0
Resolved - One of our database writer instances based out of AWS Mumbai DC had a hardware failure. AWS tried to automatically failover the instance to a healthy one, but from the logs we could see that the failover got stuck and hence delayed, causing an intermittent spike in latencies, affecting a small portion of our overall volume. We are working with AWS to understand why the process was stuck and delayed..

Dec 30, 11:34:00 GMT+0
Identified - Initial analysis indicates hardware failure of one our AWS database writer instances resulting in 504s and timeouts of our APIs..

Duration: 10 minutes

Affected Components:

Sep 17, 05:29:47 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Sep 17, 05:19:44 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 11 minutes

Affected Components:

Sep 17, 04:54:42 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Sep 17, 04:43:44 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 4 minutes

Affected Components:

Sep 16, 19:41:44 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Sep 16, 19:37:43 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 3 minutes

Affected Components:

Sep 16, 19:31:41 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Sep 16, 19:28:43 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 4 minutes

Affected Components:

Sep 16, 19:19:45 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Sep 16, 19:15:46 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 2 minutes

Affected Components:

Sep 16, 18:09:42 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Sep 16, 18:07:47 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 4 minutes

Affected Components:

Sep 16, 18:02:59 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Sep 16, 17:58:43 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 2 minutes

Affected Components:

Sep 16, 17:54:41 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Sep 16, 17:52:46 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 2 hours and 17 minutes

Affected Components:

Jun 4, 13:21:42 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Jun 4, 13:19:25 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 20 minutes

Affected Components:

May 6, 10:10:00 GMT+0
Resolved - Some of our APIs had experienced spike in latency due to high DB load. This incident has been resolved..

May 6, 09:50:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 hour

Affected Components:

May 5, 14:15:00 GMT+0
Resolved - Some of our APIs had experienced spike in latency due to high DB load. This incident has been resolved..

May 5, 13:20:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 8 hours and 14 minutes

Affected Components:

Jan 21, 08:34:24 GMT+0
Resolved - API is now operational! This update was created by an automated monitoring service..

Jan 21, 08:26:10 GMT+0
Investigating - API cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 7 hours and 59 minutes

Affected Components:

Nov 22, 12:33:43 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Nov 22, 12:25:45 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 3 hours and 2 minutes

Affected Components:

Sep 2, 09:58:49 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Sep 2, 09:55:47 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 59 minutes

Affected Components:

Aug 17, 14:20:40 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Aug 17, 14:19:42 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 9 minutes

Affected Components:

Aug 15, 04:13:07 GMT+0
Resolved - API is now operational! This update was created by an automated monitoring service..

Aug 15, 04:12:59 GMT+0
Investigating - API cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 9 minutes

Affected Components:

Aug 6, 15:49:00 GMT+0
Resolved - This incident has been resolved. We are root causing the issue at the moment. Thank you for your patience. .

Aug 6, 15:36:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 7 minutes

Affected Components:

Aug 6, 15:25:00 GMT+0
Resolved - This incident has been resolved..

Aug 6, 15:18:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 2 days, 10 hours and 4 minutes

Affected Components:

Jul 25, 13:41:48 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Jul 25, 12:43:45 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 24 minutes

Affected Components:

Jul 24, 16:30:00 GMT+0
Resolved - This incident has been resolved. We are monitoring the health of the APIs. .

Jul 24, 16:15:00 GMT+0
Identified - We are continuing to work on a fix for this incident. There seems to be high connections to our transactions database. We are trying to reduce the connections. .

Jul 24, 16:09:00 GMT+0
Investigating - We are experiencing intermittent fluctuations in some of our core APIs. We are root causing at the moment. .

Duration: 1 day, 1 hour and 16 minutes

Affected Components:

Apr 29, 09:13:57 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Apr 29, 08:48:42 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 5 days, 11 hours and 41 minutes

Affected Components:

Feb 2, 18:13:44 GMT+0
Resolved - Sandbox is now operational! This update was created by an automated monitoring service..

Feb 2, 16:02:04 GMT+0
Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..