EMnify Outage History

EMnify is up right now

EMnify had 50 outages in the last 2 years totaling 1301h 27m of downtime — averaging 2.1 incidents per month.

There were 50 EMnify outages since June 18, 2025 totaling 1301h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.emnify.com

Minor June 4, 2026

Service Degradation - Orange (Guinea)

Detected by Pingoru
Jun 04, 2026, 01:48 PM UTC
Resolved
Jun 08, 2026, 01:30 PM UTC
Duration
3d 23h
Affected: Network Connectivity - Middle East & Africa
Timeline · 3 updates
  1. investigating Jun 04, 2026, 01:48 PM UTC

    Dear emnify Customers, We are currently investigating a connectivity issue affecting devices connected via the Orange network in Guinea. Customers may experience intermittent connectivity and service degradation. Our team is actively working with the network provider to identify the root cause and restore normal service as quickly as possible. We will continue to share updates as more information becomes available. Kind regards, emnify Support Team

  2. identified Jun 04, 2026, 01:58 PM UTC

    Dear emnify Customers, We have received confirmation from Orange that they are currently experiencing an incident within their network, which may be impacting service availability. We are actively coordinating with their team and monitoring the situation closely. We will provide further updates as soon as more information becomes available from the operator. Kind regards, emnify Support Team

  3. resolved Jun 08, 2026, 01:30 PM UTC

    We have confirmed that Orange Guinea connectivity is now fully operational. Services have recovered and traffic is processing normally.

Read the full incident report →

Minor June 3, 2026

Service Degradation - 4G Connectivity

Detected by Pingoru
Jun 03, 2026, 08:23 AM UTC
Resolved
Jun 03, 2026, 09:28 AM UTC
Duration
1h 5m
Affected: Mobile Core Network
Timeline · 4 updates
  1. investigating Jun 03, 2026, 08:23 AM UTC

    Dear emnify Customers, We are currently investigating a connectivity issue affecting devices connected via 4G networks. Customers may experience intermittent connectivity and service degradation. Our team is actively working to identify the root cause and restore normal service as quickly as possible. We will continue to share updates as more information becomes available. Kind regards, emnify Support Team

  2. monitoring Jun 03, 2026, 08:37 AM UTC

    Dear emnify Customers, We are now observing that 4G traffic has returned to normal levels, indicating that connectivity has stabilized and service performance has recovered. Our team will continue to actively monitor the network to ensure 4G services remain stable and continue to function as expected. Kind regards, emnify Support Team

  3. resolved Jun 03, 2026, 09:28 AM UTC

    Dear emnify Customers, The incident was caused by a global degradation affecting LTE signaling traffic within one of our signaling providers' networks, which impacted roaming services. The issue has since been resolved, and roaming connectivity has returned to normal. In case you are still having issues, please reach out to our Support Team via our Help Center. Kind regards, emnify Support Team

  4. postmortem Jun 11, 2026, 12:27 PM UTC

    ## Summary Due to a full outage of emnify’s LTE signalling carrier for the 90143XXX and 29509XXX IMSIs, customers were unable to attach to LTE networks during the impact duration of 29min. Due to static routing in 3GPP signalling systems, there is no failover to alternate carriers. Most devices were able to connect to alternative RAT types \(2G/3G\) or using alternate IMSIs. Existing data connections were not impacted. ## Timeline \(UTC\) | Time | Event | | --- | --- | | 07:47 | **>>>INCIDENT STARTS HERE>>INCIDENT STOPS HERE<<<** |

Read the full incident report →

Notice June 2, 2026

Service Degradation - Claro (Paraguay, Uruguay, Argentina)

Detected by Pingoru
Jun 02, 2026, 08:11 AM UTC
Resolved
Jun 02, 2026, 04:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 02, 2026, 08:11 AM UTC

    Dear emnify Customers, At approximately 04:30 UTC today, we observed service degradation affecting connectivity to the Claro network in Paraguay, Uruguay, and Argentina. During this period, devices attempting to connect via Claro may have experienced intermittent connectivity issues or service disruptions. Beginning around 07:30 UTC, we observed traffic levels returning to normal, with network performance remaining stable since that time. Based on our monitoring, the incident has been resolved and services have recovered. We are continuing to engage with Claro to better understand the underlying cause of the interruption and will review any findings made available by the operator. If you continue to experience connectivity issues, please contact our Support Team through the Help Center for further assistance. Kind regards, emnify Support Team

Read the full incident report →

Minor May 18, 2026

Service Degradation - Lonestar (Liberia)

Detected by Pingoru
May 18, 2026, 07:18 AM UTC
Resolved
May 20, 2026, 05:05 PM UTC
Duration
2d 9h
Affected: Network Connectivity - Middle East & Africa
Timeline · 5 updates
  1. investigating May 18, 2026, 07:18 AM UTC

    Dear emnify Customers, We are currently investigating a connectivity issue affecting devices connected via the Lonestar network in Liberia. Customers may experience intermittent connectivity and service degradation. Our team is actively working with the network provider to identify the root cause and restore normal service as quickly as possible. We will continue to share updates as more information becomes available. Kind regards, emnify Support Team

  2. investigating May 18, 2026, 07:33 AM UTC

    Dear emnify Customers, We have reached out to Lonestar Liberia and we are awaiting additional updates regarding the root cause and remediation efforts. As a temporary mitigation measure, connections to the Lonestar network have been blocked to prevent additional device attachments. Affected SIMs should continue to connect through alternative available network (Orange). We will provide another update as soon as more information becomes available. Kind regards, emnify Support Team

  3. identified May 18, 2026, 11:30 AM UTC

    Dear emnify Customers, We are continuing to follow up closely with Lonestar Liberia and are currently awaiting further updates from their team regarding the ongoing issue. In the meantime, the alternative network provider, Orange Liberia, continues to operate normally and remains available for affected devices. We will continue to keep you informed of any significant developments. Kind regards, emnify Support Team

  4. monitoring May 20, 2026, 04:15 PM UTC

    Dear emnify Customers, Our latest network tests toward Lonestar Liberia are now returning successful results, and the temporary network block has been lifted. At this time, devices should gradually resume normal network registration and connectivity. Our teams will continue to closely monitor the situation to ensure service stability and full restoration. Further updates will be provided as recovery progresses. Kind regards, emnify Support Team

  5. resolved May 20, 2026, 05:05 PM UTC

    Dear emnify Customers, This incident has been resolved. In case you are still having issues, please reach out to our Support Team via our Help Center. Kind regards, emnify Support Team

Read the full incident report →

Minor May 14, 2026

Service degradation - Play (Poland)

Detected by Pingoru
May 14, 2026, 06:02 PM UTC
Resolved
May 14, 2026, 09:16 PM UTC
Duration
3h 14m
Affected: Network Connectivity - Europe
Timeline · 4 updates
  1. investigating May 14, 2026, 06:02 PM UTC

    We are currently investigating connectivity issues affecting devices connected through the Play network in Poland. Customers may experience intermittent connectivity or service degradation. Our team is actively working to identify the root cause and restore normal service as quickly as possible. We will continue to provide updates as more information becomes available.

  2. identified May 14, 2026, 06:10 PM UTC

    We have identified the issue affecting connectivity on the Play network in Poland and are currently in contact with the operator to restore normal service. As a temporary mitigation measure, connectivity through the Play network has been temporarily restricted. Customers in Poland can continue using alternative available networks in the country, which are operating normally. We will continue to provide updates as more information becomes available.

  3. monitoring May 14, 2026, 08:29 PM UTC

    Connectivity on the Play network in Poland has been restored and services are operating normally again. We are continuing to monitor the situation closely to ensure service stability.

  4. resolved May 14, 2026, 09:16 PM UTC

    This incident has been resolved

Read the full incident report →

Minor May 11, 2026

Service degradation - MTN (Guinea-Bissau)

Detected by Pingoru
May 11, 2026, 03:24 PM UTC
Resolved
Jun 17, 2026, 08:35 AM UTC
Duration
36d 17h
Affected: Network Connectivity - Middle East & Africa
Timeline · 3 updates
  1. investigating May 11, 2026, 03:24 PM UTC

    We are currently investigating connectivity issues affecting devices connected through the MTN network in Guinea-Bissau. At this time, other mobile networks in the country are operating normally and are not impacted. Further updates will be provided as more information becomes available.

  2. identified May 11, 2026, 04:01 PM UTC

    We are currently in contact with the operator and working with them while they implement corrective actions on their side to restore normal service. Other mobile networks in Guinea-Bissau continue to operate normally and are not impacted. We will continue to provide updates as more information becomes available.

  3. resolved Jun 17, 2026, 08:35 AM UTC

    As the issue remains ongoing, we have temporarily removed MTN from the list of available networks in our data plans for Guinea-Bissau to minimize customer impact. Customers can continue to use alternative networks in Guinea-Bissau, which are operating normally. We will continue to monitor the situation closely and will re-enable MTN once the network demonstrates stable and reliable service.

Read the full incident report →

Minor April 27, 2026

Service Degradation - MTN Côte d'Ivoire

Detected by Pingoru
Apr 27, 2026, 02:30 PM UTC
Resolved
Apr 30, 2026, 01:06 PM UTC
Duration
2d 22h
Affected: Network Connectivity - Middle East & Africa
Timeline · 4 updates
  1. investigating Apr 27, 2026, 02:30 PM UTC

    Dear emnify Customers, We are currently investigating a service degradation impacting MTN Cote d’Ivoire. Devices attempting to connect to this network may encounter connectivity issues. Our team is in contact with the operator to determine the cause. We will provide further updates as they become available. Kind regards, emnify Support Team

  2. investigating Apr 27, 2026, 03:39 PM UTC

    We have temporarily blocked access to MTN Côte d'Ivoire to prevent further device attachments. Devices in the region can continue to connect through alternative available networks. We’re keeping a close watch and will update promptly with any new information.

  3. monitoring Apr 28, 2026, 08:02 AM UTC

    Our tests are now yielding partial success; thus, we have now enabled the network again for 2G and 3G, while LTE will remain blocked in the meantime. We will continue to work with the operator to ensure full restoration.

  4. resolved Apr 30, 2026, 01:06 PM UTC

    Dear emnify Customers, The incident has been resolved. Our monitoring and validation tests confirm that the operator MTN is now fully operational. In case you are still having issues, please reach out to our Support Team via our Help Center. Kind regards, emnify Support Team

Read the full incident report →

Minor April 27, 2026

Event display issues

Detected by Pingoru
Apr 27, 2026, 02:42 AM UTC
Resolved
Apr 27, 2026, 03:54 AM UTC
Duration
1h 12m
Affected: User InterfaceAPI
Timeline · 4 updates
  1. investigating Apr 27, 2026, 02:42 AM UTC

    We are currently investigating an issue affecting the display of events in the emnify Portal, as well as via the API and Data Streamer. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available

  2. identified Apr 27, 2026, 02:50 AM UTC

    We have identified the component where the issue affecting event display is occurring. Our team is actively working on resolving the issue and will provide further updates as progress is made.

  3. monitoring Apr 27, 2026, 03:33 AM UTC

    A fix has been implemented for the issue affecting event display, and we are currently monitoring the results. We will continue to observe the system to ensure stability and will provide further updates as needed.

  4. resolved Apr 27, 2026, 03:54 AM UTC

    The issue affecting event display has been resolved. If you continue to experience any problems or have questions, please do not hesitate to contact our support team.

Read the full incident report →

Minor April 22, 2026

Increased API error rates

Detected by Pingoru
Apr 22, 2026, 07:56 AM UTC
Resolved
Apr 22, 2026, 01:01 PM UTC
Duration
5h 4m
Affected: User InterfaceAPI
Timeline · 4 updates
  1. investigating Apr 22, 2026, 07:56 AM UTC

    Dear emnify Customers, We are currently investigating increased API rate errors, primarily affecting the portal endpoint stats and API. Further updates will be provided shortly. Kind regards, emnify Support Team

  2. identified Apr 22, 2026, 08:24 AM UTC

    Dear emnify Customers, We have identified the issue and have applied a fix. The errors have now significantly decreased and we are monitoring closely the situation. We’ll continue to share updates as soon as they become available. Kind regards, emnify Support Team

  3. monitoring Apr 22, 2026, 08:31 AM UTC

    Dear emnify Customers, Error rates have decreased, and the APIs are now functioning normally. We are actively monitoring the service to ensure continued stability and performance. We’ll continue to share updates as soon as they become available. Kind regards, emnify Support Team

  4. resolved Apr 22, 2026, 01:01 PM UTC

    Dear emnify Customers, The incident has been resolved, and all services are now fully operational. In case you are still having issues, please reach out to our Support Team via our Help Center. Kind regards, emnify Support Team

Read the full incident report →

Minor April 17, 2026

Service degradation - MTN Uganda

Detected by Pingoru
Apr 17, 2026, 05:53 PM UTC
Resolved
Apr 17, 2026, 11:08 PM UTC
Duration
5h 15m
Affected: Network Connectivity - Middle East & Africa
Timeline · 4 updates
  1. investigating Apr 17, 2026, 05:53 PM UTC

    We are currently investigating a service degradation affecting connectivity in MTN Uganda. Our engineering team is actively working to identify the root cause and assess the impact. We will provide further updates as soon as more information becomes available.

  2. identified Apr 17, 2026, 06:02 PM UTC

    We have identified that the reported service degradation affecting connectivity in MTN Uganda is not originating from the emnify platform. We have engaged MTN and are working with them to resolve the issue. Connectivity on other networks in Uganda remains fully operational. We will continue to monitor the situation and provide updates as more information becomes available.

  3. monitoring Apr 17, 2026, 11:00 PM UTC

    Service connectivity in MTN Uganda has been restored. We are continuing to monitor the situation closely to ensure stability.

  4. resolved Apr 17, 2026, 11:08 PM UTC

    The issue affecting connectivity in MTN Uganda has been fully resolved. If you experience any further issues, please reach out to our support team.

Read the full incident report →

Minor April 17, 2026

OpenVPN authentication issues

Detected by Pingoru
Apr 17, 2026, 08:47 AM UTC
Resolved
Apr 17, 2026, 09:55 AM UTC
Duration
1h 8m
Affected: VPN services
Timeline · 3 updates
  1. identified Apr 17, 2026, 08:47 AM UTC

    Dear emnify Customers, We are currently investigating an issue with OpenVPN authentication affecting all breakout regions. We will provide an update shortly. Kind regards, emnify Support Team

  2. monitoring Apr 17, 2026, 09:10 AM UTC

    Our engineering team has identified the cause and has applied a fix. We are closely monitoring the results. Further updates to follow.

  3. resolved Apr 17, 2026, 09:55 AM UTC

    Dear emnify Customers, The incident has been resolved, and the OpenVPN service is fully operational again. In case you are still having issues, please reach out to our Support Team via our Help Center. Kind regards, emnify Support Team

Read the full incident report →

Minor April 8, 2026

Data Usage Statistics and Billing Preview Degradation

Detected by Pingoru
Apr 08, 2026, 04:17 PM UTC
Resolved
Apr 08, 2026, 07:12 PM UTC
Duration
2h 55m
Affected: APIData Analytics
Timeline · 4 updates
  1. investigating Apr 08, 2026, 04:17 PM UTC

    Dear emnify Customers, We are currently observing an issue affecting traffic data accuracy which may cause discrepancies in billing previews and usage statistics across the portal and APIs. Our team is actively investigating the issue and we will provide an update shortly. Kind regards, emnify Support Team

  2. identified Apr 08, 2026, 04:26 PM UTC

    Dear emnify Customers, Our team has identified the root cause of the issue and is currently working on implementing a fix. We will continue to provide updates as progress is made. Kind regards, emnify Support Team

  3. monitoring Apr 08, 2026, 07:00 PM UTC

    Dear emnify Customers, A fix has been successfully applied, and billing previews and usage statistics are now up to date. We will continue to closely monitor the system to ensure everything remains stable. Kind regards, emnify Support Team

  4. resolved Apr 08, 2026, 07:12 PM UTC

    Dear emnify Customers, The incident has been resolved. In case you are still having issues, please reach out to our Support Team via our Help Center. Kind regards, emnify Support Team

Read the full incident report →

Minor March 25, 2026

Signalling degradation

Detected by Pingoru
Mar 25, 2026, 09:35 AM UTC
Resolved
Mar 25, 2026, 10:51 AM UTC
Duration
1h 16m
Affected: Mobile Core Network
Timeline · 4 updates
  1. investigating Mar 25, 2026, 09:35 AM UTC

    We are currently investigating an issue causing signalling degradation. As a result, some devices may require multiple attempts to successfully connect to the network. Our team is actively working to identify the root cause and mitigate the impact. We will provide further updates as more information becomes available.

  2. identified Mar 25, 2026, 09:39 AM UTC

    The issue has been identified and began at approximately 09:05 UTC. We are currently applying a fix to resolve the signalling degradation. Our team is actively working on mitigation, and we will continue to provide updates as progress is made.

  3. monitoring Mar 25, 2026, 09:47 AM UTC

    The fix has been successfully applied, and the service is now restored and operating normally. Engineering teams are continuing to monitor the situation closely to ensure stability. We will provide further updates if any additional issues are observed.

  4. resolved Mar 25, 2026, 10:51 AM UTC

    The issue has been fully resolved, and all services are operating normally. If you continue to experience any issues, please reach out to support.

Read the full incident report →

Minor March 13, 2026

Events and Usage Data Processing Delay

Detected by Pingoru
Mar 13, 2026, 11:55 AM UTC
Resolved
Mar 13, 2026, 02:06 PM UTC
Duration
2h 11m
Affected: User InterfaceAPIData Analytics
Timeline · 3 updates
  1. identified Mar 13, 2026, 11:55 AM UTC

    Dear emnify Customers, We have identified an issue affecting the processing of events and usage data. As a result, some preview information may be delayed by up to 24 hours. We expect the system to fully recover within the next hour. We will provide further updates as soon as more information becomes available. Kind regards, emnify Support Team

  2. monitoring Mar 13, 2026, 12:04 PM UTC

    Dear emnify Customers, Our monitoring shows that event and usage data processing is recovering and services are gradually returning to normal. We will continue to monitor the system until full recovery is confirmed. Kind regards, emnify Support Team

  3. resolved Mar 13, 2026, 02:06 PM UTC

    Dear emnify Customers, The incident has been resolved. In case you are still having issues, please reach out to our Support Team via our Help Center. Kind regards, emnify Support Team

Read the full incident report →

Minor March 12, 2026

Increase in Diameter Signaling Traffic

Detected by Pingoru
Mar 12, 2026, 05:34 AM UTC
Resolved
Mar 12, 2026, 06:07 AM UTC
Duration
33m
Affected: Mobile Core Network
Timeline · 2 updates
  1. monitoring Mar 12, 2026, 05:34 AM UTC

    Dear emnify Customers, Earlier today, we observed elevated Diameter signaling traffic starting around 03:00 UTC. Signaling traffic levels have since decreased since 05:20 UTC and are returning to normal. Our team will keep monitoring the situation to ensure continued stability. Kind regards, emnify Support Team

  2. resolved Mar 12, 2026, 06:07 AM UTC

    Dear emnify Customers, The incident has been resolved, and Diameter signaling metrics have now returned to normal levels. The temporary increase observed earlier has been identified as a result of the signaling degradation incident that occurred yesterday. In case you are still having issues, please reach out to our Support Team via our Help Center. Kind regards, emnify Support Team

Read the full incident report →

Minor March 10, 2026

Service Degradation - Telstra Australia

Detected by Pingoru
Mar 10, 2026, 10:13 PM UTC
Resolved
Mar 11, 2026, 01:51 AM UTC
Duration
3h 38m
Affected: Network Connectivity - Asia-Pacific
Timeline · 4 updates
  1. investigating Mar 10, 2026, 10:13 PM UTC

    Dear emnify customers, We are currently investigating a service degradation affecting LTE and LTE-M connectivity on the Telstra Australia network. Devices attempting to connect may experience intermittent connectivity issues or may be unable to attach to the network. We will provide further updates as soon as more information becomes available. Kind regards, emnify Support team

  2. identified Mar 10, 2026, 10:33 PM UTC

    Dear emnify Customers, We have contacted Telstra Australia regarding the ongoing service degradation and are currently awaiting their feedback. Alternative LTE networks in Australia (Vodafone and Optus) remain available for connectivity fallback. Meanwhile, LTE-M connectivity in this region is currently provided via the Telstra network only and may therefore remain affected while the issue persists. We will provide further updates as additional information becomes available. Kind regards, emnify Support Team

  3. monitoring Mar 11, 2026, 12:16 AM UTC

    Dear emnify Customers, Telus has confirmed that a fault with their signaling provider caused the observed LTE and LTE-M service degradation. Our recent network tests are yielding successful results, and we are observing traffic towards the network beginning to recover. We will continue to monitor network performance and provide additional updates as needed. Kind regards, emnify Support Team

  4. resolved Mar 11, 2026, 01:51 AM UTC

    Dear emnify Customers, The incident has been resolved, and network traffic has returned to normal levels. In case you are still having issues, please reach out to our Support Team via our Help Center. Kind regards, emnify Support Team

Read the full incident report →

Notice March 5, 2026

SMS service interruption

Detected by Pingoru
Mar 05, 2026, 03:24 PM UTC
Resolved
Mar 05, 2026, 09:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Mar 05, 2026, 03:24 PM UTC

    Dear emnify Customers, Earlier today, we observed a temporary degradation in the SMS services. Upon investigation, it was determined that A2P SMS-MT, or SMS messages sent from the portal/API to emnify devices, were affected. After applying a fix, we immediately started to see SMS-MT being processed as normal. All SMS services are now fully operational as of writing.

Read the full incident report →

Minor March 4, 2026

Degradation in processing of portal/data streamer events and device usage statistics

Detected by Pingoru
Mar 04, 2026, 09:24 PM UTC
Resolved
Mar 05, 2026, 12:53 AM UTC
Duration
3h 28m
Affected: Data Analytics
Timeline · 4 updates
  1. investigating Mar 04, 2026, 09:24 PM UTC

    Dear emnify Customers, We are investigating an issue related to the processing of events and usage data. As a result, the portal and API report outdated data from 20:05 UTC. Also, the emnify Data Streamer is currently unable to deliver data. We are working on resolving the issue, and an update will be provided shortly. Kind regards, emnify Support Team

  2. identified Mar 04, 2026, 09:32 PM UTC

    We have identified the issue and implemented a fix. We are now seeing new events being delivered. We will continue to monitor closely.

  3. monitoring Mar 04, 2026, 09:58 PM UTC

    We continue to see that the events data and usage statistics are finally catching up. We expect all data to be backfilled within the next 2 hours. We will continue to monitor closely.

  4. resolved Mar 05, 2026, 12:53 AM UTC

    This incident has been resolved and all data has been successfully backfilled. If you continue to experience any issues, please contact our Customer Support team via the help center.

Read the full incident report →

Minor February 17, 2026

Portal Service Degradation

Detected by Pingoru
Feb 17, 2026, 08:39 AM UTC
Resolved
Feb 17, 2026, 03:37 PM UTC
Duration
6h 57m
Affected: User InterfaceAPIData Analytics
Timeline · 3 updates
  1. investigating Feb 17, 2026, 08:39 AM UTC

    We are currently experiencing temporary issues with our portal. Our team is actively investigating and working to resolve the issue as quickly as possible. Further updates will be provided shortly.

  2. identified Feb 17, 2026, 11:16 AM UTC

    The portal issue has been mitigated and core access has been restored. Some portal functionalities may still be temporarily unavailable. Our team is currently working on restoring full API data accuracy. Further updates will follow as progress continues.

  3. resolved Feb 17, 2026, 03:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 4, 2026

Service Degradation - Tigo Panama

Detected by Pingoru
Feb 04, 2026, 08:56 PM UTC
Resolved
Feb 04, 2026, 09:33 PM UTC
Duration
37m
Affected: Network Connectivity - Central and South America & Caribbean
Timeline · 3 updates
  1. investigating Feb 04, 2026, 08:56 PM UTC

    We are currently investigating reports of service degradation impacting 2G connectivity on the Tigo Panama network. Further updates will be provided as more information becomes available.

  2. identified Feb 04, 2026, 09:13 PM UTC

    We have contacted Tigo Panama regarding the ongoing 2G service degradation and are currently awaiting their response. In the meantime, please note: -3G and 4G services with Tigo Panama remain available and are operating normally -Alternative mobile networks in Panama are also available for connectivity fallback Our team continues to monitor the situation closely and will provide further updates as soon as we receive additional information from the operator.

  3. resolved Feb 04, 2026, 09:33 PM UTC

    Tigo Panama has confirmed that their 2G service has been permanently sunsetted. As a result, 2G connectivity is no longer available on the Tigo Panama network. -Other radio access types with Tigo Panama remain available and are operating normally -2G service is still available in Panama through alternative mobile network If you have any questions, please contact our Customer Support team.

Read the full incident report →

Minor January 30, 2026

Service degradation - Telcel Mexico

Detected by Pingoru
Jan 30, 2026, 08:03 PM UTC
Resolved
Jan 30, 2026, 09:27 PM UTC
Duration
1h 24m
Affected: Network Connectivity - North America
Timeline · 4 updates
  1. investigating Jan 30, 2026, 08:03 PM UTC

    We are currently investigating a service degradation impacting Telcel connectivity in Mexico. We will provide an update shortly.

  2. identified Jan 30, 2026, 08:14 PM UTC

    We have contacted Telcel Mexico and are currently awaiting their response. In the meantime, we have temporarily blocked connections to the Telcel network to prevent further attachments, allowing affected SIMs to connect via alternative networks like Movistar or AT&T. We will share another update as soon as more information becomes available.

  3. monitoring Jan 30, 2026, 08:35 PM UTC

    We are seeing traffic returning to normal levels. As a result, we have unblocked the Telcel network and service is recovering. We will continue to monitor the situation closely

  4. resolved Jan 30, 2026, 09:27 PM UTC

    This incident has been resolved. If you continue to experience any issues, please contact our Customer Support team

Read the full incident report →

Minor January 28, 2026

Downgraded Performance – Embedded Dashboards & Stats API

Detected by Pingoru
Jan 28, 2026, 05:40 PM UTC
Resolved
Jan 28, 2026, 09:23 PM UTC
Duration
3h 42m
Affected: APIData Analytics
Timeline · 4 updates
  1. investigating Jan 28, 2026, 05:40 PM UTC

    We are currently investigating reports of degraded performance affecting the embedded dashboards in the portal and the Stats API. Our team is working to identify the root cause and will provide updates as more information becomes available.

  2. identified Jan 28, 2026, 05:47 PM UTC

    We have identified that the degraded performance is caused by an issue with our infrastructure provider. We are working closely with them to restore normal service as quickly as possible and will provide further updates soon

  3. monitoring Jan 28, 2026, 08:06 PM UTC

    The issue affecting has been resolved. Services are operating normally again, and we are continuing to monitor the situation closely to ensure stability

  4. resolved Jan 28, 2026, 09:23 PM UTC

    This incident has been resolved. If you continue to experience any issues, please contact our Customer Support team for further assistance.

Read the full incident report →

Minor January 16, 2026

Service Degradation - Claro Puerto Rico

Detected by Pingoru
Jan 16, 2026, 09:54 PM UTC
Resolved
Jan 17, 2026, 02:47 AM UTC
Duration
4h 52m
Affected: Network Connectivity - North America
Timeline · 4 updates
  1. investigating Jan 16, 2026, 09:54 PM UTC

    Dear emnify customers, We are currently investigating a service degradation affecting Claro Puerto Rico. Devices attempting to connect to this network may experience connectivity issues. Alternative networks are operating as expected. We will share an update as soon as more information becomes available. Kind regards, emnify Support team

  2. identified Jan 16, 2026, 10:14 PM UTC

    Dear emnify Customers, Our team has reached out to Claro to better understand the cause and expected resolution. In the meantime, we have proactively blocked the affected network to prevent further device attachment attempts, while alternative networks in the country remain available. We are keeping a close watch and will update promptly with any new information. Kind regards, emnify Support Team

  3. monitoring Jan 17, 2026, 02:15 AM UTC

    Dear emnify Customers, Our latest tests are returning successful results and the network block has now been lifted. We’re also seeing signs of traffic recovery. We will continue to monitor the situation to ensure service is fully restored and will share further updates as recovery progresses. Kind regards, emnify Support Team

  4. resolved Jan 17, 2026, 02:47 AM UTC

    Dear emnify Customers, The incident has been resolved, and all services are now fully operational. In case you are still having issues, please reach out to our Support Team via our Help Center. Kind regards, emnify Support Team

Read the full incident report →