tag:status.sequel.io,2005:/historySequel Status - Incident History2024-03-29T05:23:47ZSequeltag:status.sequel.io,2005:Incident/175633432023-06-13T22:10:46Z2023-06-13T22:10:46ZAWS major outage affecting multiple services<p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>22:10</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved and all systems are fully operational.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>20:45</var> UTC</small><br><strong>Monitoring</strong> - The AWS team deployed a fix and our affected services are operational with minor degradation. We are monitoring to ensure a full recovery.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>19:44</var> UTC</small><br><strong>Identified</strong> - The issue is caused by a major AWS outage affecting AWS Lambda functions: https://health.aws.amazon.com/health/status. <br /><br />We are working closely with the AWS team to restore this as soon as possible.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>19:32</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating an issue with AWS in the us-east region affecting some customers to access the dashboard and go live.</p>tag:status.sequel.io,2005:Incident/164780232023-03-13T16:47:21Z2023-03-13T16:49:57ZAuth0 User Authentication major outage<p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>16:47</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved. This only affected some admin users trying to login to the Sequel dashboard. All other services including registration, event joining and participating to events were not impacted.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>16:35</var> UTC</small><br><strong>Monitoring</strong> - A fix was deployed from Auth0 and we are monitoring the results.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>16:27</var> UTC</small><br><strong>Identified</strong> - Our login provider, Auth0, is having a major outage and some users are unable to login and access the Sequel dashboard. We are working with Auth0 to provide an estimated fix. <br /><br />More information can be found here: https://status.auth0.com/incidents/41gk3rcgm9vg</p>tag:status.sequel.io,2005:Incident/109017102022-08-24T20:56:02Z2022-08-24T20:56:02ZCircle Recordings are not available<p><small>Aug <var data-var='date'>24</var>, <var data-var='time'>20:56</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>24</var>, <var data-var='time'>20:55</var> UTC</small><br><strong>Update</strong> - Circle Recordings are working.</p><p><small>Aug <var data-var='date'>24</var>, <var data-var='time'>16:47</var> UTC</small><br><strong>Identified</strong> - We are working to resolve this as soon as possible.</p>tag:status.sequel.io,2005:Incident/107109212022-07-28T19:17:34Z2022-07-28T19:53:30ZGoing live issues for some users<p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>19:17</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>18:11</var> UTC</small><br><strong>Monitoring</strong> - Our backup servers are fully deployed and the issue was resolved. Users are able to go live at any point. We are continuing to monitor the outage from AWS.</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>17:38</var> UTC</small><br><strong>Identified</strong> - This was caused by the AWS outage in us-east-2 where a few of our streaming servers are located. Our backup regions are now handling all the live requests and we are actively routing all traffic away from us-east-2.</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>17:24</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating an issue caused by the AWS outage in us-east-2. Some users might not be able to go live.</p>tag:status.sequel.io,2005:Incident/89045192021-12-20T16:27:04Z2022-06-08T17:13:03ZThis is an example incident<p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>16:27</var> UTC</small><br><strong>Resolved</strong> - Empathize with those affected and let them know everything is operating as normal.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>16:17</var> UTC</small><br><strong>Monitoring</strong> - Let your users know once a fix is in place, and keep communication clear and precise.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>16:23</var> UTC</small><br><strong>Identified</strong> - As you continue to work through the incident, update your customers frequently.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>16:53</var> UTC</small><br><strong>Investigating</strong> - When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.</p>