Digi.me Outage History

Digi.me had 4 outages in the last 2 years totaling 1h 27m of downtime — averaging 0.2 incidents per month.

There were 4 Digi.me outages since August 23, 2024 totaling 1h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.digi.com

Notice August 20, 2026

Performance Degradation - Resolved

Detected by Pingoru: Aug 20, 2026, 01:28 PM UTC
Resolved: Aug 20, 2026, 12:30 PM UTC
Duration: —

Timeline · 1 update

resolved Aug 20, 2026, 01:28 PM UTC

The Digi Cloud Operations Team encountered a performance degradation issue. The problem began on August 20, 2026 @ 10:00 UTC and was resolved by August 20, 2026 @ 12:15 UTC. During this time, Customers may have experienced high latency sending or receiving device data. Corrective measures have been successful; normal performance has been restored. Thank you for your continued business and patience during this incident.

Read the full incident report →

Minor August 7, 2026

Performance Degradation

Detected by Pingoru: Aug 07, 2026, 11:29 PM UTC
Resolved: Aug 07, 2026, 11:44 PM UTC
Duration: 14m

Affected: Application and UIWeb Services

Timeline · 2 updates

investigating Aug 07, 2026, 11:29 PM UTC

The Digi Cloud Operations Team has observed a performance degradation impacting the application tier and is currently working to resolve the issue. Updates will be provided to this page as more information becomes available. Thank you for your continued business and patience.
resolved Aug 07, 2026, 11:44 PM UTC

The Digi Cloud Operations Team has resolved the performance degradation issue and continues to monitor the application. The problem began on August 7, 2026 23:17 UTC and was resolved by August 7, 2026 23:30 UTC. During this time, Customers may have experienced high latency sending or receiving device data. Normal performance has been restored. Thank you for your continued business and patience during this incident.

Read the full incident report →

Major July 20, 2025

Service Disruption

Detected by Pingoru: Jul 20, 2025, 03:47 PM UTC
Resolved: Jul 20, 2025, 04:39 PM UTC
Duration: 52m

Affected: Application and UIWeb ServicesDevice Connections

Timeline · 5 updates

investigating Jul 20, 2025, 03:47 PM UTC

The Digi Cloud Operations Team has observed a service disruption impacting the entire application and is currently working to resolve the issue. Updates will be provided to this page as more information becomes available. Thank you for your continued business and patience.
investigating Jul 20, 2025, 03:54 PM UTC

We are continuing to investigate this issue.
identified Jul 20, 2025, 03:59 PM UTC

The issue has been identified. A fix is being implemented. Performance is degraded at the moment. The Digi Cloud Operations Team continues to monitor the situation.
monitoring Jul 20, 2025, 04:14 PM UTC

The application is returning to normal operation. The Digi Cloud Operations Team continues to monitor the application.
resolved Jul 20, 2025, 04:39 PM UTC

The performance issue has been resolved. The Digi Cloud Operations Team will continue monitoring the application and will post any escalations to this page in the future. Thank you for your continued business.

Read the full incident report →

Minor January 31, 2025

Problem with individual device settings in the UI

Detected by Pingoru: Jan 31, 2025, 07:00 PM UTC
Resolved: Jan 31, 2025, 07:20 PM UTC
Duration: 20m

Affected: Application and UI

Timeline · 2 updates

identified Jan 31, 2025, 07:00 PM UTC

The Digi Cloud Operations Team has observed an issue related to saving settings for devices in multiple product lines. A fix will be deployed shortly. In the meantime, we recommend you use the Templates feature if possible to change settings on devices. Information on the Templates feature can be found here: https://www.digi.com/resources/documentation/Digidocs/Templates_user_guide/home.htm/Templates_user_guide/Home.htm
resolved Jan 31, 2025, 07:20 PM UTC

A fix has been deployed and confirmed. Thank you for your business and patience.

Read the full incident report →