Postmortem -
Read details
Oct 27, 14:18 UTC
Resolved -
Between 10:12 and 10:18 UTC a change to the way back-end resources are allocated led to a scenario whereby the services processing requests began being forcibly restarted.
This was caused by the services rapidly exceeding predefined resource limits and being taken out of service.
This resulted in a partial outage that affected a small number of requests.
Our internal monitoring alerted us to the issue and the changes were reverted.
We're continuing to monitor the situation but consider this incident resolved.
Full service was restored at 10:18 UTC.
Oct 23, 10:59 UTC
Investigating -
Customers using our Canadian data center may have experienced interruption of service when accessing both our API and application.
This was caused by a recent change and will have presented as HTTP 502 - Gateway Timeout statuses.
We have reverted the change and are in the process of assessing the exact scope of the issue.
Oct 23, 10:35 UTC