Resolved -
[2025-07-14 10:50:49] - Incident status was updated to "resolved".
Summary: The incident has been resolved. A Root Cause Analysis will be conducted and shared with affected customers who logged tickets.
Jul 14, 11:00 UTC
Update -
[2025-07-11 08:37:43] - Incident status was updated to "monitoring".
Summary: The affected mobile core location has been restored and is fully operational since 03:00 CET. A final step to revert the workaround for impacted customers is underway, which will be completed without further disruption. A final update will be provided once this process is finished.
Jul 11, 08:40 UTC
Monitoring -
[2025-07-10 08:19:33] - Incident status was updated to "monitoring".
Summary: The incident impact has subsided since yesterday morning. A temporary workaround has been implemented for affected customers. The mobile core location is expected to be restored by 15:00 CET today, resuming normal operations. The situation continues to be monitored closely.
Jul 10, 08:20 UTC
Update -
[2025-07-09 19:17:28] - Incident status was updated to "identified".
Summary: A mobile core location remains partially non-operational. Teams are actively working on the issue. Full service restoration is estimated for tomorrow after 10:00 CET, following the reinstallation of all applications.
Jul 9, 19:20 UTC
Update -
[2025-07-09 16:47:04] - Incident status was updated to "identified".
Summary: A mobile core location remains partially non-operational. Teams are actively working on resolving the issue. Full service restoration is estimated after 20:00 CET.
Jul 9, 17:00 UTC
Update -
[2025-07-09 13:25:15] - Incident status was updated to "identified".
Summary: A mobile core location issue persists, with full service restoration expected between 17:00 and 18:00 CET. A temporary workaround has been implemented to mitigate impact on affected customers. The provider continues to work on resolving the problem.
Jul 9, 13:40 UTC
Update -
[2025-07-09 08:31:31] - Incident status was updated to "identified".
Summary: The ongoing issue is taking longer to resolve than expected. Full resolution is now anticipated by 15:00 CET when the affected mobile core location will be restored. A workaround is available for affected customers. Some impact may persist until the full resolution is implemented.
Jul 9, 08:40 UTC
Update -
[2025-07-09 07:15:50] - Incident status was updated to "identified".
Summary: The provider is actively working on resolving the ongoing issue. No specific timeline or additional details have been provided at this time.
Jul 9, 07:20 UTC
Update -
[2025-07-09 06:53:16] - Incident status was updated to "identified".
Summary: Engineers and vendors are working to fix an affected mobile core location. Resolution is expected within 1 hour, but could take up to 11:00.
Jul 9, 07:00 UTC
Update -
[2025-07-09 04:23:43] - Incident status was updated to "identified".
Summary: Service is gradually being restored for affected customers through a temporary workaround. The underlying issue is expected to be fully resolved later this morning.
Jul 9, 04:40 UTC
Update -
[2025-07-09 03:57:30] - Incident status was updated to "identified".
Summary: A cooling issue at a mobile core location caused IP address shortages for some customers. The problem has been mitigated for those who reported it. A restart of the affected core location is planned to fully resolve the underlying issue.
Jul 9, 04:00 UTC
Identified -
Mobile core cooling issues causing IP address shortage and service degradation for M2M connections. Restart planned to resolve the root cause.
Affected countries: NL
Jul 9, 04:00 UTC