All Systems Operational
Portal, API & Data Analytics Operational
User Interface Operational
API Operational
Data Analytics Operational
Network Connectivity Operational
Network Connectivity - North America Operational
Network Connectivity - Europe Operational
Network Connectivity - Asia-Pacific Operational
Network Connectivity - Central and South America & Caribbean Operational
Network Connectivity - Middle East & Africa Operational
Mobile Core Network Operational
SMS Connectivity Operational
VPN services Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
API Uptime
Fetching
Past Incidents
May 26, 2022

No incidents reported today.

May 25, 2022
Portal usability degraded
Resolved - Dear customers,

We have released a new portal version containing a fix for the error messages appearing when using Mozilla Firefox.

Please update to the latest portal version in case you see a prompt appearing shortly after loading https://portal.emnify.com. Alternatively, clear your browser cache and reload the portal.

We will continue to monitor whether errors are reported in our automated error tracking system also with the new version. In case you are still experiencing issues after using clearing browser caches, please try the private browsing mode. If the issue still persists, please contact our Customer Support team.
May 25, 17:21 UTC
Identified - We have been able to replicate the issues when using Mozilla Firefox. While we continue investigating, please use alternative browsers.
May 25, 17:08 UTC
Investigating - Dear EMnify customer,

We are currently observing usability issues when performing certain actions in the portal. This is currently being investigated and we will post a new update shortly.
May 25, 15:58 UTC
May 24, 2022

No incidents reported.

May 23, 2022

No incidents reported.

May 22, 2022

No incidents reported.

May 21, 2022

No incidents reported.

May 20, 2022

No incidents reported.

May 19, 2022
Data Connectivity Issues in Asia-Pacific Breakout
Resolved - This incident has been resolved.
May 19, 19:04 UTC
Monitoring - Dear Customer,

We have experienced data connectivity issues in Asia-Pacific breakout region from 17:04 UTC to 17:22 UTC.

Services are stable at the moment, please reach out to our support in case you're seeing any issues.

Thanks a lot
EMnify Support
May 19, 17:28 UTC
May 18, 2022

No incidents reported.

May 17, 2022

No incidents reported.

May 16, 2022

No incidents reported.

May 15, 2022
Service degradation - Claro / Colombia
Resolved - The incident has been resolved and the service is now operational.

In case you are still experiencing issues, please submit a request to our Customer Support team.
May 15, 00:54 UTC
Monitoring - We are already starting to see traffic again. Claro Colombia confirmed the issue in their network and they are working on mitigating it.

We will be monitoring this closely, and update the status accordingly.
May 14, 23:13 UTC
Identified - We confirm that Claro Colombia is having network connectivity issues, affecting devices roaming across their network.

In the meantime, we would like to remind you the availability of alternative networks; Movistar and Tigo.
May 14, 19:57 UTC
Investigating - Dear EMnify customer,

We are currently investigating a service degradation in Claro Colombia. Devices that attempt to connect to this network may experience issues.

We will publish a new update shortly.
May 14, 19:31 UTC
May 14, 2022
May 13, 2022

No incidents reported.

May 12, 2022
Devices incorrectly blocked from opening data sessions
Postmortem - Read details
May 13, 16:49 UTC
Resolved - Between 12:11 to 12:43 UTC we mistakenly blocked devices from opening data sessions. This affected some customers that have a traffic limit configured. Customers that have no traffic limit configured were not affected by the incident. The incident was triggered by our application reprocessing traffic limit configuration.

The issue is now resolved and we will further investigate the root cause of the problem.

We are sorry for any inconvenience caused.
May 12, 12:30 UTC
← Incident History Powered by Atlassian Statuspage