Previous incidents

This incident has been resolved which was the result of a technical anomaly identified by our monitoring systems starting from 06:55 AM UTC and during this period, some clients experienced general slowness and timeouts.

Immediate action was needed to resolve this incident, which required us to put our application in unplanned maintenance from 7:20 AM UTC to 8:05 AM UTC.

We have identified the root cause of the issue and we’ve taken the necessary precautions to prevent similar incidents ...

Following an elevated amount of 500 errors on our platform, we identified an infrastructure issue requiring our application to be put in maintenance mode.

This incident was a result of a technical anomaly that our monitoring systems have detected, and immediate action was needed to resolve it, which required us to put our application in maintenance mode and during this period, our services were going through maintenance downtime.

We have identified the root cause of the issue and we’ve ...

Resolved - Due to a network hardware issue caused by our vendor which affected a portion of our infrastructure, we have experienced a high latency accompanied with a server timeout for 4 minutes between 16:16:00 and 16:19:00 UTC. This was mitigated and the incident has been resolved.