Postmortem -
Read details
Oct 21, 18:08 UTC
Resolved -
We're now moving to a resolved state as we have had multiple confirmations from our Support team as well as Clients. We appreciate all the patience while we worked through this issue. If you're happening to still have any intermittent issues or concerns please don't hesitate to reach out to the support team or the success team.
Oct 11, 22:48 UTC
Monitoring -
The Engineering team has identified the issue and put a fix into place. We are moving to a monitoring state as we make sure these issues are no longer causing issues with accessing the site. Please reach out to the support team to confirm. We will post an update at 4:55 CST.
Oct 11, 21:00 UTC
Update -
The investigation process is still continuing with our Engineering team. All resources are applied to get this resolved. Our sincerest apologies as we continue the efforts on this task. We will also update again in an hour at 3:55 CST.
Oct 11, 19:57 UTC
Update -
Our Engineering team is still investigating the issues at hand. We deeply apologize as we continue all our efforts into finding the resolution and get the site back online. We will still be doing updates every hour an our next is scheduled for 2:55 CST. Any questions or concerns you might have our Support team and Customer Success team are more than happy to assist on.
Oct 11, 18:58 UTC
Update -
Our Engineering team is making progress on the issues at hand and we are still in an investigation state. We will be updating again at 1:55 PM CST. Again, we do appreciate the patience as we put our continued efforts into getting the site back online.
Oct 11, 17:57 UTC
Update -
The Engineering team is still working diligently to find the source of the issue. We apologize for any inconveniences this may be causing. The next update will be at 12:55 PM CST.
Oct 11, 16:55 UTC
Investigating -
Hello, as of 10:55 AM CST we are noticing that production sites are unable to be accessed in their current state. Our Engineering team is actively looking into what could be causing this and we'll be posting an update at 11:55 AM CST. We greatly appreciate the patience as we investigate the issues at hand.
Oct 11, 16:04 UTC