NFON AG incident
Partial Service Disruption Affecting NFON Services
NFON AG experienced a major incident on July 31, 2026 affecting Business Telephony and SIP Trunk and 1 more component, lasting 1d 4h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 31, 2026, 06:45 AM UTC
We have identified an issue affecting NFON services. Both telephony and other related services may be impacted. Our technical teams are investigating the issue.
- investigating Jul 31, 2026, 07:03 AM UTC
We are making progress in resolving the issue and are beginning to see a gradual improvement in service availability. Our technical teams continue to monitor the situation closely and are working to fully restore all affected services.
- investigating Jul 31, 2026, 07:39 AM UTC
Core telephony services are generally available. A limited number of virtual PBXs hosted in FRA may be affected, and some CCHub systems are currently under investigation. Customers may also experience issues accessing voicemail and other related services. Our technical teams are continuing to investigate and restore full service availability.
- investigating Jul 31, 2026, 08:32 AM UTC
Core telephony services remain largely available. However, some customers may still experience intermittent issues when accessing Cloudya, contacts, the Admin Portal, and related backend services, including occasional 500, 502, or authentication errors. Our technical teams are continuing to stabilize the affected components. Reloading the application may temporarily restore access, but the incident is not yet fully resolved
- investigating Jul 31, 2026, 09:29 AM UTC
Core telephony services remain largely available, and the overall situation has continued to improve. However, some customers may still experience intermittent delays or errors when accessing Cloudya, contacts, device provisioning, SIP registration, and portal-related services. Our technical teams have identified performance issues affecting the Service Portal API and its database backend. Mitigation measures are showing positive results, and we continue to closely monitor and stabilize the affected components. The incident is not yet fully resolved.
- monitoring Jul 31, 2026, 10:31 AM UTC
The platform is stable again, and service availability has significantly improved. A small number of minor bottlenecks may still cause occasional delays in some backend-related functions. Our technical teams have implemented mitigation measures and are continuing to monitor the affected components closely. We are moving the incident to monitoring while we verify sustained stability.
- resolved Aug 01, 2026, 10:03 AM UTC
The general incident was resolved on 31 July 2026 at 11:45 CEST, when service was restored for most affected customers. However, during the monitoring phase, a small number of isolated service issues were identified. These issues have since been resolved.