Elements.cloud had 9 outages in the last 2 years totaling 491h 52m of downtime — averaging 0.4 incidents per month.
There were 9 Elements.cloud outages since November 7, 2024 totaling 491h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are seeing elevated failures in the Organization Sync feature due to an external network outage at AWS. Other Elements services remain operational. Impact: Sync jobs may be delayed or fail. No data loss is expected; failed jobs will automatically retry once connectivity stabilizes.
This incident has been resolved.
Many of our EU customers may have received an email stating that a sync failed due to an expired token. This was caused by a system error that incorrectly triggered the notification and sent it out to most users. The issue has been fixed, and no further false emails are being sent. We apologize for the inconvenience.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating reports of degraded performance when accessing S3 data. Users may experience slow reads and writes, or intermittent failures when attempting to access or modify data stored in S3. Our team is actively working to identify the root cause and will provide updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Status: Investigating Started: June 12, 2025 Impact: Diagram Editor is currently unavailable We’re currently experiencing an outage in the Diagram Editor due to a broader Google Cloud / Firebase incident. This issue originates on Google’s side and affects authentication, database access, and real-time syncing features required for the editor to function. We are monitoring the situation and will provide updates as Google resolves the issue. You can follow their status here: https://downdetector.ie/
We are continuing to investigate this issue.
Firebase Outage is over, we are monitoring the situation
This incident has been resolved.
Synchronization failures detected in Sandbox Organisations due to Salesforce server errors
This incident has been resolved.
Apologies for the inconvenience. Our understanding is that Salesforce are conducting upgrade and Hyperforce migration activities over the weekend. As a result, many in-progress Elements sync processes may have been disrupted. This should be a temporary issue, and you can resync manually or wait until the next automated sync. Please let us know if this does not resolve your issue. If you see a "Click to refresh ..." link, please be aware that your Salesforce account should be logged in only on the org for which you are refreshing the authentication token.
This issue has been resolved, this was caused by a DNS resolution issue out of Elements Control. Please accept our sincere apologies for the inconvenience caused.
We are currently monitoring this issue.
This incident has been resolved.
Due to Salesforce connectivity issues and multiple instances offline, some of our customers might experience sync issues. This results in sync failures. We are aware of the issue, and are in contact with Salesforce, waiting for their team to bring those orgs back online.
This incident has been resolved.
Due to Salesforce connectivity issues and multiple SF instances offline, some of our customers might experience sync issues. This results in sync failures. We are aware of the issue, and are in contact with Salesforce, waiting for their team to bring those orgs back online.
We are pleased to let you know that the sync issues have been fixed. Apologies for any inconvenience caused.