Elements.cloud Outage History
Elements.cloud is up right nowPingoru has recorded 11 incidents for Elements.cloud: 1 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 19 (0%) |
Incidents, newest first
Notice September 16, 2026 Sync failures due to Salesforce outage 5h 48m
Started Sep 16, 2026, 11:23 AM UTC· resolved Sep 16, 2026, 05:12 PM UTC
- monitoring Sep 16, 2026, 11:23 AM UTC
We are currently observing numerous sync failures in Production due to an ongoing issue on Salesforce's side. Salesforce is returning HTTP 503 (service unavailable / maintenance) errors, which is causing our integrations to fail. This is a Salesforce-side outage, confirmed by widespread reports on Downdetector. Our team is actively monitoring the situation. No action is required from your side — syncs will resume automatically once Salesforce restores service. Sorry for the inconvenience. We'll post an update as soon as we have more information.
- resolved Sep 16, 2026, 05:12 PM UTC
This incident has been resolved.
Notice October 20, 2025 AWS network outage impacting Org Sync 2h 51m
Started Oct 20, 2025, 10:07 AM UTC· resolved Oct 20, 2025, 12:58 PM UTC
- identified Oct 20, 2025, 10:07 AM UTC
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.
- resolved Oct 20, 2025, 12:58 PM UTC
This incident has been resolved.
Notice September 5, 2025 False emails about Refresh Token 23m
Started Sep 05, 2025, 09:18 AM UTC· resolved Sep 05, 2025, 09:42 AM UTC
- investigating Sep 05, 2025, 09:18 AM UTC
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.
- identified Sep 05, 2025, 09:19 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Sep 05, 2025, 09:42 AM UTC
This incident has been resolved.
Notice July 16, 2025 S3 Data Access Performance Issues 15h 36m
Started Jul 16, 2025, 04:32 PM UTC· resolved Jul 17, 2025, 08:08 AM UTC
- identified Jul 16, 2025, 04:32 PM UTC
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.
- monitoring Jul 16, 2025, 06:03 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 17, 2025, 08:08 AM UTC
This incident has been resolved.
Notice June 12, 2025 Diagram Editor Outage 14h 15m
Started Jun 12, 2025, 06:38 PM UTC· resolved Jun 13, 2025, 08:53 AM UTC
- investigating Jun 12, 2025, 06:38 PM UTC
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/
- investigating Jun 12, 2025, 06:38 PM UTC
We are continuing to investigate this issue.
- monitoring Jun 12, 2025, 06:53 PM UTC
Firebase Outage is over, we are monitoring the situation
- resolved Jun 13, 2025, 08:53 AM UTC
This incident has been resolved.
Notice May 12, 2025 Synchronization failures 1d
Started May 12, 2025, 11:36 AM UTC· resolved May 13, 2025, 11:58 AM UTC
- identified May 12, 2025, 11:36 AM UTC
Synchronization failures detected in Sandbox Organisations due to Salesforce server errors
- resolved May 13, 2025, 11:58 AM UTC
This incident has been resolved.
Notice April 21, 2025 Salesforce Hyperforce Migration Disruption Impacting Elements Sync 2d 19h
Started Apr 21, 2025, 02:43 PM UTC· resolved Apr 24, 2025, 09:45 AM UTC
- identified Apr 21, 2025, 02:43 PM UTC
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.
- resolved Apr 24, 2025, 09:45 AM UTC
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.
Notice January 8, 2025 Synchronization failures detected in Sandbox organisations due to Salesforce server errors 11d 23h
Started Jan 08, 2025, 11:24 AM UTC· resolved Jan 20, 2025, 10:30 AM UTC
- monitoring Jan 08, 2025, 11:24 AM UTC
We are currently monitoring this issue.
- resolved Jan 20, 2025, 10:30 AM UTC
This incident has been resolved.
Notice November 15, 2024 Salesforce servers unavailable for some customers 3d 3h
Started Nov 15, 2024, 09:53 AM UTC· resolved Nov 18, 2024, 01:44 PM UTC
- monitoring Nov 15, 2024, 09:53 AM UTC
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.
- resolved Nov 18, 2024, 01:44 PM UTC
This incident has been resolved.
Notice November 7, 2024 Salesforce connectivity issues causing sync failures for some customers 4h 26m
Started Nov 07, 2024, 11:26 AM UTC· resolved Nov 07, 2024, 03:52 PM UTC
- identified Nov 07, 2024, 11:26 AM UTC
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.
- resolved Nov 07, 2024, 03:52 PM UTC
We are pleased to let you know that the sync issues have been fixed. Apologies for any inconvenience caused.