The incident report (post mortem) is available from our support team at support@invers.com.
Posted Jul 03, 2025 - 09:04 UTC
Resolved
Our monitoring shows that connections have been stable since the last update. This incident has been resolved.
Posted Jul 01, 2025 - 07:27 UTC
Update
Almost all connections have now been restored. The restoration was carried out in blocks so as not to overload the system when hundreds of thousands of devices reconnect and then all want to send their stored data.
The process is now complete, we are continuing to monitor it and are working with our partners to find out exactly what went wrong and how this can be prevented in the future.
We apologize for the connectivity restrictions on 3G and 4G EU devices.
If the system remains stable, we will close the incident in the morning European time.
Posted Jul 01, 2025 - 02:41 UTC
Update
The connections are now almost all restored.
Posted Jul 01, 2025 - 02:32 UTC
Update
The restoration process is still ongoing. To prevent peak loads and thus renewed instability and a collapse of the service, connections will be gradually reactivated. Unfortunately, this will take some time, so we are unable to give a final restoration time.
Posted Jul 01, 2025 - 02:19 UTC
Monitoring
The restoration of connections is still ongoing, but not all connections are available yet.
Posted Jul 01, 2025 - 01:31 UTC
Update
Some mobile phone providers in the countries are already fully available again, and the process is continuing with a clear positive trend.
Posted Jul 01, 2025 - 00:59 UTC
Update
We see an improvement and a sustained positive trend in our graphs.
Posted Jul 01, 2025 - 00:53 UTC
Update
Reconnecting the data sessions is taking longer than expected. We are in contact with our partners and will post updates here.
Posted Jul 01, 2025 - 00:37 UTC
Update
We are continuing to work on a fix for this issue.
Posted Jul 01, 2025 - 00:05 UTC
Update
Our partners report that the error has been found and is currently being fixed. We should see an improvement soon. However, we cannot confirm this in our logs at this time. We are on it.
Posted Jun 30, 2025 - 23:58 UTC
Update
We are in contact with our connectivity partners. The current status is that only CloudBoxx 4G and CloudBoxx 3G devices are affected. Type 1020 devices, including the entire North American market, are NOT affected. There is currently no information on when the error will be fixed, but we are in constant contact with our partners' emergency teams, who are working hard to find a solution.
Posted Jun 30, 2025 - 23:23 UTC
Update
Our connectivity providers are continuing to work on a fix, but not ETA, yet.
Posted Jun 30, 2025 - 23:05 UTC
Update
We are still experiencing the issues and are waiting for updates from our connectivity provider.
Posted Jun 30, 2025 - 22:17 UTC
Identified
One of our connectivity partners is reporting degraded performance in the EU region.
Posted Jun 30, 2025 - 21:56 UTC
Investigating
We currently experience cellular connectivity issues. We are investigating.