Our engineers have determined the root cause of this outage was a spike in traffic between internal APIs, which caused cyclic crashes between two services within Flow as one repeatedly overwhelmed the other. We will be prioritizing work to distribute our API's boot-time request volume to prevent this manor of failure in the future.
Oct 31, 18:05 UTC
All Flow services have returned to normal operation. We are still closely monitoring to ensure it stays that way, and will conduct a root cause analysis shortly. We appreciate your patience.
Oct 31, 17:11 UTC
Response times and error rates are returning to normal levels. We are closely monitoring the situation. Some notifications or chat messages may still be delayed as the backlog is processed.
Oct 31, 16:58 UTC
Traffic to Flow Chat and notifications processing is slowly resuming. A hosting provider outage is inhibiting our ability to mitigate this issue in a timely manner.
Oct 31, 16:44 UTC
Flow Chat and Notifications have been taken offline as we try and rectify the performance problems
Oct 31, 16:26 UTC
Flow is experiencing unusual load and some services may be slower to load than usual. We are investigating mitigations.
Oct 31, 15:54 UTC