Resolved -
After extensive monitoring, we have confirmed that the system is running as expected.
Jun 5, 14:36 EDT
Monitoring -
A fix has been implemented and our team is monitoring the results to ensure all functionality is working as expected.
Jun 5, 07:27 EDT
Update -
Access to the application has been restored, but we are continuing to address residual issues involving UI performance, Email, and SMS sending. We are actively working to restore full functionality and will provide further updates here as soon as we have them.
Jun 4, 20:13 EDT
Identified -
We've identified the issue and are working to restore service.
Jun 4, 16:58 EDT
Update -
Our engineering team is continuing to actively investigate the root cause of the 504 Gateway Timeout errors preventing access to the platform. We are treating this issue with the highest priority and are working diligently to resolve it as quickly as possible.
We will provide regular progress updates on this page as the investigation continues.
If you have an urgent message that cannot wait until the system is fully restored, we have an alternative platform available to send it on your behalf.
To initiate this, the request must come directly from an Account Admin (Super User Top)
Please contact our support team with the following:
-Message Details: Provide the exact message content and your desired delivery channels (SMS, Email, etc.).
-Recipient File: Email us a file containing the recipient addresses (phone/SMS numbers or email addresses).
-Data Security: For your security, please send this file as a password-protected .zip file.
-File Password: Provide the password for the .zip file to our support team by phone so we can securely access it and queue your message.
Thank you for your continued patience and understanding while we work through this.
Jun 4, 14:40 EDT
Investigating -
We are currently experiencing a 504 Gateway Timeout error, which is preventing some users from accessing the site. Our engineering team is actively investigating the root cause. We sincerely apologize for the disruption and will provide another update as soon as we have more information.
Jun 4, 13:11 EDT