EMnify Outage History

EMnify experienced connectivity issues affecting devices using the Play network in Poland, causing intermittent connectivity and service degradation for customers in that region. The team identified the root cause, coordinated with the network operator, and temporarily restricted Play network access while customers could use alternative networks in Poland. The incident was resolved after 3.3 hours with full connectivity restored and normal service operations resumed.

EMnify experienced a service degradation affecting MTN Côte d'Ivoire network connectivity, causing devices to encounter connection issues when attempting to connect to this operator. The incident impacted network connectivity in the Middle East & Africa region and lasted 9 minutes. The team worked with the operator to investigate and resolve the connectivity problems.

EMnify experienced an issue affecting event display functionality in both the Portal user interface and API for 1.3 hours. The problem prevented users from properly viewing events through these channels. The team identified the problematic component, implemented a fix, and resolved the issue after monitoring to ensure system stability.

EMnify experienced increased API error rates that primarily affected portal endpoint statistics and API functionality for 5.1 hours. The incident impacted both the API and user interface components, preventing normal access to portal services. The issue was identified and resolved with a fix, after which error rates decreased and all services returned to full operational status.

EMnify experienced a 5.3-hour service degradation affecting network connectivity on MTN Uganda, while other networks in the region remained operational. The issue was identified as originating from MTN's infrastructure rather than EMnify's platform, and EMnify worked with MTN to resolve the connectivity problems. Service was fully restored after monitoring confirmed stability.

EMnify experienced OpenVPN authentication issues that affected VPN services across all breakout regions for 1.2 hours. The engineering team identified the root cause and applied a fix, with monitoring confirming the resolution. The OpenVPN service was restored to full operational status.

EMnify experienced a 3-hour incident where traffic data accuracy issues caused discrepancies in billing previews and usage statistics across both the portal and APIs. The team identified the root cause and successfully applied a fix to restore accurate billing previews and usage statistics. The incident was resolved after a monitoring period to ensure system stability.

EMnify experienced signalling degradation in their Mobile Core Network that caused some devices to require multiple connection attempts to successfully connect to the network. The issue was identified, fixed, and fully resolved within 1.3 hours with normal service operations restored.

EMnify experienced a processing issue that delayed events and usage data by up to 24 hours, affecting preview information displayed in the User Interface, API, and Data Analytics components. The incident lasted 2.2 hours, with services gradually recovering as data processing resumed normal operation. The issue was fully resolved with all systems returning to normal functionality.

EMnify experienced elevated Diameter signaling traffic in their Mobile Core Network starting around 03:00 UTC, which was identified as a result of a previous day's signaling degradation incident. The signaling traffic levels began decreasing around 05:20 UTC and returned to normal by 06:07 UTC, with the incident fully resolved after monitoring confirmed system stability.