Disruption to a some SIPREG trunks

resolved · 29 Oct 2026, 09:17

Closed by an administrator.

monitoring · 14 Oct 2026, 00:41

**What's happening** Following this evening's planned network maintenance, a number of PBXs registering to our SIP Registration service experienced degraded service, including failed registrations through parts of the window. Trunks using a continuous REGISTER method have automatically recovered and require no action. **Resolution** Maintenance windows have now closed, and no further impact is expected to any customer PBX that has continued to Register throughout the evening. Due to the registration and authentication challenges used on this platform, outbound calls will likely be unaffected on unregistered systems; however, inbound calls will fail to reach the customer PBX until registration is restored. It is recommended to check and re-register from the services outlined below. Fuse 2 will complete further a further review into the maintenance work to ensure that root cause is understood and consider for future planned works. **Scope** 3CX SMB/StartUp customers, and those self-hosting a 3CX Multi-Tenant deployment, may need to manually re-register their Fuse 2 SIP Trunk. Licensing and system configuration on these editions limits automatic re-registration behaviour. We have raised a list of known connections that appear to be unregistered with 3CX to re-register affected trunks on their hosting side where possible, but recommend you also confirm your system has re-registered manually. Yeastar PBX customers should also check registration status and manually re-register if the trunk has not reconnected.