Is Cumulocity IoT Down Right Now? Check if there is a current outage ongoing.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

See below for an important notice to all users of tenants on cumulocity.com As part of our continuous effort to improve our service, we will conduct maintenance of underlying infrastructure on the Cumulocity platform cumulocity.com environment on the 28th of May from 03:00 CEST to 09:00 CEST. This will be a background activity that will have little or no impact on your use of cumulocity.com; there is no anticipation of Platform unavailability or interruption. Agents and Microservices, including the Advanced Streaming Analytics module, will have to be restarted and unavailable during the restart procedure. We apologize for the inconvenience caused and assure you we shall keep any such interruptions to a minimum. Please make sure that all your relevant users of the Cumulocity IoT Platform are subscribed to our update services and are aware of the maintenance. We will provide you with an additional reminder one hour before the maintenance. We will inform you as we progress through the maintenance and in case there are any deviations from the communicated plan. If you have any questions or concerns, please do not hesitate to contact us.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

See below for an important notice to all users of tenants on emea.cumulocity.com As part of our continuous effort to improve our service, we will conduct maintenance of underlying infrastructure on the Cumulocity platform emea.cumulocity.com environment on the 26th of May from 03:00 CEST to 09:00 CEST. This will be a background activity that will have little or no impact on your use of emea.cumulocity.com; there is no anticipation of Platform unavailability or interruption. Agents and Microservices, including the Advanced Streaming Analytics module, will have to be restarted and unavailable during the restart procedure. We apologize for the inconvenience caused and assure you we shall keep any such interruptions to a minimum. Please make sure that all your relevant users of the Cumulocity IoT Platform are subscribed to our update services and are aware of the maintenance. We will provide you with an additional reminder one hour before the maintenance. We will inform you as we progress through the maintenance and in case there are any deviations from the communicated plan. If you have any questions or concerns, please do not hesitate to contact us. Thank you for your continued co-operation.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

See below for an important notice to all users of tenants on us.cumulocity.com As part of our continuous effort to improve our service, we will conduct maintenance of underlying infrastructure on the Cumulocity platform us.cumulocity.com environment on the 26th of May from 03:00 CEST to 09:00 CEST. This will be a background activity that will have little or no impact on your use of us.cumulocity.com; there is no anticipation of Platform unavailability or interruption. Agents and Microservices, including the Advanced Streaming Analytics module, will have to be restarted and unavailable during the restart procedure. We apologize for the inconvenience caused and assure you we shall keep any such interruptions to a minimum. Please make sure that all your relevant users of the Cumulocity IoT Platform are subscribed to our update services and are aware of the maintenance. We will provide you with an additional reminder one hour before the maintenance. We will inform you as we progress through the maintenance and in case there are any deviations from the communicated plan. If you have any questions or concerns, please do not hesitate to contact us. Thank you for your continued co-operation.

We have resolved the issue by a combination of hardware scale-up and flushing metadata that caused issues for the Dremio engine. Performance is back to normal.

We have observed a performance issue with DataHub on eu-latest.cumulocity.com. We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

We have not seen any further problematic symptoms and are confident that the applied fix solved the issue. We will inform you should any new issues arise. We again apologize for the inconvenience caused.

The maintenance has been completed successfully. We are now monitoring the service closely.

We observed an issue within the DataHub module of the Cumulocity platform on eu-latest.cumulocity.com. You may experience failing offloadings and slow queries on Dremio. We will perform emergency maintenance to mitigate the potential root cause. You may experience short service interruption of Dremio. We apologize for the inconvenience caused.

This incident has been resolved.

The maintenance has been finished. We are monitoring system before closing this issue. Thank you.

Dear Customers We identified potential issue and need to perform short maintenance. We apologize for inconvenience and short notice.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We observed a performance issue within the Cumulocity platform on emea.cumulocity.com We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

Our monitoring confirms that the issue has been resolved.

The platform is up and running again. We are still investigating the root cause. We are monitoring the system to make sure that the symptoms fully disappear. We will inform you once we have further information.

We observed an issue within the entire Cumulocity platform on cumulocity.com We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

Incident has been resolved.

We applied the fix and are monitoring recovered service.

We applied the fix and are monitoring recovered service.

We observed an issue within the LWM2M module of the Cumulocity platform on EMEA. We identified problem with LWM2M component and will proceed with emergency fix. We will inform you as soon as we have further information. We apologize for the inconvenience caused.

This incident has been resolved.

The fix is in place. We'll continue to closely monitor the platform.

We have identified the root cause and are implementing a fix. As of now the platform should be reachable already. However, as part of the fix you may still experience short connection issues. We apologize for this inconvenience.

During the planned maintenance we observed an unplanned outage of the entire Cumulocity platform on emea.cumulocity.com. We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

The service has recovered and is operating as expected. We again apologize for the inconvenience caused

Service recovered and should be up and running, we keep on monitoring.

We're currently monitoring recovered process startup.

We observed an issue within the DataHub module of the Cumulocity IoT platform on eu-latest.cumulocity.com. We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

While monitoring we have not seen any further problematic symptoms and are confident that the applied fix solved the issue. We will inform you in case new issues should arise. Additionally, we will perform a maintenance tomorrow to synchronize internal state within our backend components. We again apologize for the inconvenience caused.

We have applied a fix, the system is in a stable state. We will keep monitoring it. There is a need to apply further state synchronizations tomorrow - it will be announced separately.

We are applying the fix for the issue. Users may not be able to run jobs against Dremio.

We are continuing to work on a fix for this issue.

We observed an issue within the DataHub module of the Cumulocity IoT platform on eu-latest.cumulocity.com. Some offloadings may fail. We have identified a potential root cause and are working on a fix. There may be a short downtime of Dremio UI when we apply it. We apologize for the inconvenience caused.

The platform has been brought back up. We continue monitoring the stability 24/7.

We observed an issue within the entire Cumulocity IoT platform on cumulocity.com We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We observed a reduction in service quality within the Cumulocity IoT Platform on cumulocity.com. We are investigating the root cause and will inform you as soon as we have further information.

This incident has been resolved.

We have identified the issue and rectified the cause. Service is restored to nominal and we are monitoring the situation.

We are currently investigating performance issues that we detected and are working with urgency to find out the root cause and to restore services.

This incident has been resolved.

We have identified the issue and rectified the cause. Service is restored to nominal and we are monitoring the situation.

The issue has been identified and a fix is being implemented.

We are currently investigating performance issues that we detected and are working with urgency to find out the root cause and to restore services.

The issue has been resolved by implementing multiple changes to hardware and software configurations. Thank you for your patience.

The change has been implemented successfully. We are continuing to monitor the situation.

We have applied several recommendations of the third-party vendor, however every time the system went back to unstable state. We will now implement further recommendations, which require full downtime of Dremio. The expected downtime is about one hour.

The hotfix did not work as planned and Dremio is still unstable. We have escalated with the third-party vendor and are following up with them.

The hotfix version has been deployed. We are monitoring the environment.

After testing in staging environments, a hotfix version of DataHub is ready. We will deploy it shortly.

Users may experience instability and unavailability of the service. We have identified the issue, a hotfix is being tested in our staging environment.

This incident has been resolved.

We have identified the issue and rectified the cause. Service is restored to nominal and we are monitoring the situation.

We are currently investigating performance issues that we detected and are working with urgency to find out the root cause and to restore services.

The issue has been resolved.

A fix is in place, the service is healthy again. We will keep monitoring it.

Users may experience instability and unavailability of the service. We are currently addressing the issue.

This incident has been resolved

This incident has been resolved. We're monitoring for the time being.

Cumulocity IoT DataHub (CDH) for emea.cumulocity.com feature is experiencing issues again. We are investigating it.

This incident has been resolved. We're monitoring for the time being.

Cumulocity IoT DataHub (CDH) for emea.cumulocity.com feature is experiencing issues now. We are investigating it.

This incident has been resolved.

Cumulocity IoT DataHub (CDH) for emea.cumulocity.com feature is experiencing issues now. We are investigating it.

This incident has been resolved.

We stabilized the situation and are monitoring the service closely.

We observed an issue with the Loriot Agent on the Cumulocity IoT platform on cumulocity.com We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

The issue has been resolved, all versions are available again on npmjs.com.

We are currently facing issues with our NPM releases. Nearly all old versions of the @c8y/ngx-components package have been removed. This issue has no impact on any running application. However, it does affect developers of web applications: Building applications using the Web SDK @c8y/ngx-components might result in errors, as NPM might not find the version you are using. There are currently two workarounds: 1. If you are using a version higher than 1017.0.0, you can update to the latest fix version of the package. For these releases, we are able to publish new fix versions and you can update to this version by adding the ~ (tilde) in front of all @c8y packages in your package.json. 2. You can switch to versions before 1017.0.0 from our resources server. Simply replace the @c8y/ngx-components version with the following URL: https://resources.cumulocity.com/webapps/ui-releases/c8y-ngx-components-1013.0.111.tgz (replace the version string, “1013.0.111” in the example URL with your currently used GA version.) We are sorry for the inconvenience and are working hard on a solution together with NPM.

We have not observed any problematic symptoms while monitoring the Cumulocity IoT platform on cumulocity.com. We apologize for any inconvenience caused.

We are continuing to monitor for any further issues.

In order to fix another issue identified in relation to the state of the platform, we perform some config changes for the data broker functionality. No service interruption is expected. We apologize for the inconvenience caused and assure you we shall keep any such interruptions to a minimum.

We have applied a fix for the performance issue within the Cumulocity IoT platform on cumulocity.com We are monitoring the system to ensure the implemented measures take long-term effect. We will inform you once we have further information.

We identified a component that slows down the response of the platform. Mitigation requires a restart some services which will result in a short connection interruption. Impact will be that devices subscribed to real-time notifications (long-polling connection) or connected via MQTT will need to reconnect.

We found some indications about a possible reason. The mitigation requires a restart of some services. We apologize for the inconvenience caused and assure you we shall keep any such interruptions to a minimum.

We observed a performance issue within the Cumulocity IoT platform on cumulocity.com We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

This incident has been resolved.

We observed a reduction in service quality within the Cumulocity IoT Platform on emea.cumulocity.com. We are investigating the root cause and will inform you as soon as we have further information.

This incident has been resolved.

We have identified the issue and rectified the cause. Service is restored to nominal and we are monitoring the situation.

We are currently investigating performance issues that we detected and are working with urgency to find out the root cause and to restore services.

Please be informed that we observed sporadic slowness on the emea.cumulocity.com Cumulocity IoT Platform starting at 13:51 CET on the 21st of February 2024. Since the 22nd of February at 14:22 CET, we haven't seen any further occurrence of the issue. This may have caused temporary performance issues within the Cumulocity IoT platform on emea.cumulocity.com We are still investigating the root cause and monitoring the platform. We apologize for the inconvenience caused.

While monitoring the Cumulocity IoT platform on emea.cumulocity.com we have not seen any further problematic symptoms and are confident that the applied fix solved the issue. We will inform you in case new issues should arise. We again apologize for the inconvenience caused.

We are seeing an issue within the entire Cumulocity IoT Platform on emea.cumulocity.com. The root cause has been identified and the issue corrected. We are closely monitoring the situation, services are working normal currently.

The replication lag has been solved. Database is healthy again.

An issue with the Cumulocity database occurred in the early morning hours of 21.08.2023. This may have caused caused temporary device disconnects, failed queries or performance issues on some tenants. As of approx. 06:55 AM CEST the platform is responsive again. We are monitoring the system to make sure that the symptoms fully disappear. We will inform you once we have further information.

As of 18:00 PM CEST on 05.07, the incident has been resolved by Azure. Response times are back to normal.

We are currently experiencing a performance issue within the Cumulocity IoT platform hosted on Azure West Europe. According to Azure preliminary information, there is an issue with the Azure network resulting in packet drops, timeouts and increased latencies. As a result, the response time from the Cumulocity IoT platform may be less than anticipated or suboptimal until Azure resolves the problem. The latest information about the ongoing performance degradation can be tracked on the Azure status page: https://azure.status.microsoft/en-us/status . We apologize for the inconvenience caused.

This incident has been resolved.

We are continuing to work on a fix for this issue.

The root cause of the issue within the Single Sign-on service of the Cumulocity IoT platform on cumulocity.com has been identified. We are working on a fix and have to therefore perform an emergency rolling restart of the system. Please be informed that the rolling restart will not impact system usage, API availability or device connectivity whatsoever. The rolling restart maintenance activity is planned between 09:00 AM CET - 12:00 PM CET on 23.05.2023.

This incident has been resolved.

We have identified the issue and implemented mitigation measures. Services have been restored, and we are now monitoring the stability of the Platform. We again apologize for the inconvenience caused.

We observed a reduction in service quality within the Cumulocity IoT Platform on cumulocity.com. We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

This incident has been resolved.

We have identified the issue and rectified the cause. Service is restored to normal, and we are monitoring the situation. We again apologize for the inconvenience caused.

We again see a reduced service quality within the Cumulocity IoT Platform on cumulocity.com where API's might become temporarily unavailable. We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

We have identified the issue and rectified the cause. Service is restored to nominal and we are monitoring the situation. We again apologize for the inconvenience caused.

We are seeing a reduction of service quality within the Cumulocity IoT Platform on cumulocity.com where API's might become temporarily unavailable. We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

We have not seen any further problematic symptoms and are confident that the applied fix solved the issue. We apologize for the inconvenience caused.

A fix has been implemented and we are monitoring the results.

The issue has been identified, and a fix is being implemented.

We are seeing a reduction of service quality within the Cumulocity IoT Platform on eu-latest.cumulocity.com. We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

This issue is resolved as of release 10.15.0.218

Please be informed that we are experiencing an issue with UI Web SDK address search boxes. As of a change in the Mapquest API (an API used by Cumulocity UIs to resolve geo locations for addresses), all address search boxes are currently not working. Custom applications built with the Web SDK that use the address search need to follow the guide: https://cumulocity.com/guides/web/upgrade/#update-to-an-newer-version Also, the Content Security Policy (CSP) needs to be aligned for fix updates. The fix will be delivered soon. We are sorry for the inconvenience caused

The issue has been resolved. Please see the last update from Microsoft: Summary of Impact: Between 07:05 UTC and 09:45 UTC on 25 January 2023, customers experienced issues with networking connectivity, manifesting as network latency and/or timeouts when attempting to connect to Azure resources in Public Azure regions, as well as other Microsoft services including M365 and PowerBI. Preliminary Root Cause: We determined that a change made to the Microsoft Wide Area Network (WAN) impacted connectivity between clients on the internet to Azure, connectivity between services within regions, as well as ExpressRoute connections. Mitigation: We identified a recent change to WAN as the underlying cause and have rolled back this change. Networking telemetry shows recovery from 09:00 UTC onwards across all regions and services, with the final networking equipment recovering at 09:35 UTC. Most impacted Microsoft services automatically recovered once network connectivity was restored, and we worked to recover the remaining impacted services. We are sorry for the inconvenience caused.

Please find update from Microsoft Azure: Most customers should now see full recovery as WAN networking has recovered fully. We are working to monitor and ensure full recovery for services that were impacted. The next update will be in 30 minutes or as soon as we have further information.

Please find update from Microsoft Azure: We've determined the network connectivity issue is occurring with devices across the Microsoft Wide Area Network (WAN). This impacts connectivity between clients on the internet to Azure, as well as connectivity between services in datacenters, as well as ExpressRoute connections. The issue is causing impact in waves, peaking approximately every 30 minutes. We have identified a recent WAN update as the likely underlying cause, and have taken steps to roll back this update. Our latest telemetry shows signs of recovery across multiple regions and services, and we are continuing to actively monitor the situation.

Please find the update from Microsoft Azure: Azure Networking - Multiple regions - Investigating Starting at 07:05 UTC on 25 January 2023, customers may experience issues with networking connectivity, manifesting as network latency and/or timeouts when attempting to connect to Azure resources in multiple regions, as well as other Microsoft services. We are actively investigating and will share updates as soon as more is known.

We are currently experiencing issues with all Cumulocity platforms that are hosted on Microsoft Azure that are having it's root cause based on issues in the Microsoft infrastructure. We will inform you about any changes in that matter in due course.

After analysing the vulnerability, we consider current releases of Cumulocity IoT Platform are not affected. However, if your microservices leverage vulnerable OpenSSL versions for the outbound TLS connections, it is advised to upgrade OpenSSL library to version 3.0.7. Once we have further details, we will analyse the impact of the vulnerability in the context of the Cumulocity IoT Platform and take the necessary actions if required. Thank you for your continued co-operation.

OpenSSL - X.509 Email Address 4-byte Buffer Overflow and X.509 Email Address Variable Length Buffer Overflow. CVE: CVE-2022-3786, CVE-2022-3602 CVSS Score: N/A Vulnerability Details: A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. An attacker can craft a malicious email address in the certificates to create a buffer overflow that could result in a crash (causing a denial of service) or potentially remote code execution. Severity: High Reference: https://mta.openssl.org/pipermail/openssl-announce/2022-October/000238.html • OpenSSL versions 3.0.0 to 3.0.6 are vulnerable to this issue. • OpenSSL 3.0 users should upgrade to OpenSSL 3.0.7. • OpenSSL 1.1.1 and 1.0.2 are not affected by this issue. The details published in the CVE are analysed in the context of Cumulocity IoT cloud and Cumulocity IoT Edge. After analysing the vulnerability, we consider current releases of Cumulocity IoT Platform are not affected. However, if your microservices leverage vulnerable OpenSSL versions for the outbound TLS connections, it is advised to upgrade OpenSSL library to version 3.0.7 as recommended above. For updates regarding public Cumulocity IoT platforms that we operate, refer to the status page - https://status.cumulocity.com/. Change log: 31st October 2022 - Initial Publication 02nd November 2022 – Advisory updated after CVE details were available.

Latest updates are available from https://www.openssl.org/news/secadv/20221101.txt https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/ https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3786

Please be informed that OpenSSL has made an announcement about their forthcoming release of their next version, which will be released on Tuesday (1st Nov, 2022). This release is expected to include a fix for a HIGH security vulnerability. CVE: unknown CVSS Score: unknown Vulnerability Details: unknown Severity: High Reference: https://mta.openssl.org/pipermail/openssl-announce/2022-October/000238.html Versions that are vulnerable: - OpenSSL versions 3.0 and above. - OpenSSL version 3.0.7 is expected to be released on Tuesday (1st Nov, 2022) with the fix for this vulnerability. From our current analysis, the vulnerability does NOT impact the current GA versions of Cumulocity IoT Public Clouds, and Edge deployments, as the affected versions are not used in the Cumulocity platform. Once we have further details, we will analyse the impact of the vulnerability in the context of the Cumulocity IoT Platform and take the necessary actions if required. Please watch out for updates on the status page - https://status.cumulocity.com/

We have not seen any further problematic symptoms and are confident that the applied fix solved the issue. We apologize for the inconvenience caused.

We have applied a fix for the Cumulociy IoT DataHub (CDH) issue on emea.cumulocity.com. We are monitoring the system to make sure that the symptoms entirely disappear. We will inform you once we have further information.

The issue has been identified, and a fix is being implemented.

We are investigating stability issues with Cumulocity IoT DataHub (CDH) on emea.cumulocity.com. We will update this ticket once we have identified the cause of the instabilities. We apologize for the inconvenience caused.

The platform is running stable at the moment and we are closing the incident. In case of further issues a new incident will be opened in due course. Again, we apologize for the inconvenience caused.

The root cause has been identified with some REST API calls causing excessive resource usage. Mitigation measure for this specific issue been put into place and it is worked on a permanent fix. We are closely monitoring the situation, services are working normal currently. we apologize for the inconvenience caused.

We are still experiencing issues with stability of the platform and are continuing to investigate the root cause. We will update this ticket asap once we have identified the cause of the instabilities.

The root cause of the issue on emea.cumulocity.com has not yet been identified. We are working on a fix and will inform you as soon as we have further information.

We are seeing an issue within the entire Cumulocity IoT Platform on emea.cumulocity.com We are investigating the root cause and will inform you as soon as we have further information. We apologize for the inconvenience caused.

This incident has been resolved.

The platform is now fully functional again.

During increase of resources on the platform, an unplanned reboot of all nodes was triggered.

After increasing resources the system has been stable.

More resources has been added to the platform and is now performing as expected again. We are closely monitoring the envirnment.

Root cause of the slowness is multiple deletions going on towards the DB, which sets down the performance of the whole platform.

We are currently investigating slow connection issues that we detected on emea.cumulocity.com. We will update shortly when we have identified the problem.

This incident has been resolved.

Problem has been identified within our infrastructure and rectified, we are now monitoring the situation

We are currently investigating issues with us.cumulocity.com where tenants might be having problems with accessing their microservices. We'll update shortly when we have identified the problem.

This incident has been resolved.

Issue has been identified and corrected

We are investigating an issue for apj.cumulocity.com where microservices are not accessible for some tenants and will update once we identified the root cause

Marking the incident as completed now, as all the Cumulocity IoT Platforms are fully functional. - apj.cumulocity.com - cumulocity.com - us.cumulocity.com - emea.cumulocity.com - eu-latest.cumulocity.com In case of any issues observed, kindly requesting to report a support ticket as usual. Thank you so much again for your continued support!

All of our Cumulocity IoT Platforms are brought back to service and fully functional now. - apj.cumulocity.com - cumulocity.com - us.cumulocity.com - emea.cumulocity.com - eu-latest.cumulocity.com In case of any issues observed, kindly requesting to raise a Support ticket as usual. We keep the incident in the observation for a couple of days to monitor how the system is performing. Once again apologies for the interruption of our services happened and sincerely thank you so much for all your support and standing with us to with stand this entire Internet world exploit.

We have applied the patch fix to the following Cumulocity IoT Platforms also. - us.cumulocity.com - emea.cumulocity.com - eu-latest.cumulocity.com So, all of our IoT Platforms are working and fully functional now. Thank you so much for your continued support and understanding.

We have applied the patch fix to the following Cumulocity IoT Platforms. - apj.cumulocity.com - cumulocity.com We continue working on bringing the other Platforms also safely. We will keep you updated soon. Thank you for your continued support.

Thank you again for your continued support and understanding. We are applying the tested patches and working on safely bringing back our IoT Platforms to live. We keep you updated again once fully functional soon. Apologies for the inconvenience caused.

Thank you for your continued support, understanding and patience. We are continuing on the investigations and also testing the workarounds. We are working on bringing all the systems live in a safe manner.

We are continuing to investigate this issue.

Dear all, we have been impacted by exploit for java log4j Links: https://www.bleepingcomputer.com/news/security/new-zero-day-exploit-for-log4j-java-library-is-an-enterprise-nightmare/ https://www.zdnet.com/article/security-warning-new-zero-day-in-the-log4j-java-library-is-already-being-exploited/ As matter of precaution, we have stopped platforms in order to identify if they have been compromised. Sorry for any inconvenience caused.

This incident has been resolved.

The service has been restored and we will monitor the service for stability

We are continuing to investigate this issue.

We are experiencing problems in accessing the platform and are investigating the issue. We will update you as soon as possible.

SWe're back to normal performance of the platform.

We are currently seeing very high load on our Cumulocity IoT Platform at cumulocity.com The high load is on the database which will impact everyone using the platform - you can see 502 errors when logging in, or your microservices not responding in time. We have located the source of the high load and applied request limits. Further actions might still be needed. We are continuously monitoring the Platform and will keep you updated with further information. Apologies for the inconvenience caused.

The apj.cumulocity.com environment now has a rollback in place regarding removal of support for weak ciphers. The same fix will be applied to *.cumulocity.com by the end of the week.

We are continuing to work on a fix for this issue.

With the 10.10 release, the cipher suite was updated and weak cyphers were excluded to make the platform more secure. This was announced latest in the 10.9 release notes, but because a lot of active devices are still using old ciphers, we are looking for a possible solution supporting older ciphers. There are two separated paths here based on protocol: * HTTP - it is already possible to configure ciphers per instance, for now on all environments (emea, eu-latest, apj and us) we decided to use configuration from version 10.9, exception is our cloud instance where TLSv1 was disabled. The main point here is that we are quite flexible in this field and we can change those configuration with low effort. * MQTT - with version 10.10 platform was moved to containerised core environment, where mqtts traffic is terminated, which makes the ciphers configuration a little bit more complex. We are investigating possible solutions here. Also note that MQTT devices with old version of the paho library will not be able to connect using TLS v1.3

Problems have been resolved by the cloud provider and we are checking the infrastructure for service impacts. So far all has been found normal.

We have been notified that there is an issue with one of our cloud providers which hosts the following platforms: - cumulocity.com - eu-latest.cumulocity.com Which might lead to slower behaviour or access errors. The cloud provider has identified the issue and is working to provide a solution. We will update shortly when new information gets available.

All core nodes of the cluster were unavailable for a limited amount of time. Two out of four core nodes were added back within minutes, two others required a reboot in order to regain full functionality.

Cumulocity IoT platform degradation for the microservices at cumulocity.com environment between 10.June.2021 22:30 CEST and 11.June.2021 09:49 CEST due to the underlying Hyper Scaler problem. More details about AWS issue and RCA at https://status.aws.amazon.com/#EU_block. A short summary here: 6:54 PM PDT Starting at 1:18 PM PDT we experienced connectivity issues to some EC2 instances, increased API errors rates, and degraded performance for some EBS volumes within a single Availability Zone in the EU-CENTRAL-1 Region. At 4:26 PM PDT, network connectivity was restored and the majority of affected instances and EBS volumes began to recover. At 4:33 PM PDT, increased API error rates and latencies had also returned to normal levels. The issue has been resolved and the service is operating normally. The root cause of this issue was a failure of a control system which disabled multiple air handlers in the affected Availability Zone.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified the issue with the underlying database and have restarted the service which restored services. Please expect some slowdown for some time as all customers devices will need to catch up.

We are currently a problem with cumulocity.com hosted tenants as there seems no traffic be possible. We will update you as soon as we have new information available.

We have identified an issue with hosted microservices infrastructure which is currently been worked on. Problem has been rectified and solved at around 7:50 AM CET.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are partially experiencing issues in our platform for some of the services. In case if you happened to notice some new tenant creation or microservice deployment issues, then we are working on it already. Apologies for the inconvenience caused.