EMnify Outage History

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.

EMnify experienced a signaling degradation in their Mobile Core Network that caused some devices to have intermittent connectivity issues and difficulties establishing sessions. The incident lasted 3.5 hours, during which the team worked to mitigate the impact while monitoring key signaling metrics that gradually improved. The issue was fully resolved with signaling metrics stabilizing at normal levels.

EMnify experienced a 3.7-hour service degradation affecting LTE and LTE-M connectivity on the Telstra Australia network, causing devices to experience intermittent connectivity issues or inability to attach to the network. The incident was caused by a fault with Telstra's signaling provider, while alternative LTE networks (Vodafone and Optus) remained available for fallback, though LTE-M connectivity was limited to Telstra only during the outage. The issue was resolved and network traffic returned to normal levels.

EMnify experienced a 3.5-hour degradation in processing portal and API events, causing outdated data reporting from 20:05 UTC and preventing the Data Streamer from delivering data. The Data Analytics component was affected, impacting device usage statistics and event processing across the platform. The issue was identified and fixed, with all data successfully backfilled once the incident was resolved.