Fuse2 Communications

Fuse2 · Communications

Status Page

https://status.fuse2.net/

View Fuse2 Status History & Stats

Last 30 Days

3 incidents

Current state: Operational

Recent incidents

SIP Registration: Called Number Format Improvement
Maintenance · 4 Nov 2026, 20:00 · resolved about 16 hours ago
- resolved4 Nov, 21:00
  The scheduled maintenance window ended at 4 Nov 2026, 21:00. Closed automatically by the status page.
- identified4 Nov, 13:48
  Components: Inbound Call Termination, SIP Trunks - SIP Registration Window: 2026-11-04T20:00:00+00:00 → 2026-11-04T21:00:00+00:00 ### Summary We have improved the way inbound calls are delivered to customer phone systems (PBXs) over our SIP registration service. The Called Number Format setting on each number present on this service will now control how the dialled number (the SIP “To” header) appears to your PBX when receiving inbound calls. ### Background Until now, our network always delivered the dialled number in full international format with a leading +, for example `+443300880333`. It did this whatever Called Number Format was configured on the number. ### Measures taken Before this change, we updated the Called Number Format on every existing number to **E164+**. This matches exactly what customer PBXs receive today. Inbound calls will keep routing as they do now, and we don't expect any regression. ### What this means for you You can now choose how the dialled number is presented to your PBX: | Called Number Format | Delivered as | |---|---| | E164+ (current setting) | `+443300880333` | | E164 | `443300880333` | | National | `03300880333` | Before you change this setting, make sure your PBX's inbound routing rules match the new format. If they don't, calls may not reach the right destination. New numbers added to your account will match the format of your existing numbers unless you ask for something different. ### Support For questions or help reviewing your settings, please contact support@fusee2.net
Security Upgrade Maintenance – SIP Registration Platform
Maintenance · 30 Oct 2026, 20:30 · resolved 6 days ago
- resolved31 Oct, 00:00
  The scheduled maintenance window ended at 31 Oct 2026, 00:00. Closed automatically by the status page.
- identified30 Oct, 17:28
  Components: Outbound Call Termination, Inbound Call Termination, SIP Trunks - SIP Registration Window: 2026-10-30T20:30:00+00:00 → 2026-10-31T00:00:00+00:00 ## What is being done We are conducting security upgrades on the SIP-Registration platform. This work is necessary to ensure that the platform continues to perform with high availability and integrity. ## Who will be affected Anyone using a SIP-Registration based SIP trunk may experience a very brief period (less than a minute in total) of inability to place outbound or receive inbound calls. If you experience any issue with placing or receiving calls, please wait 1 minute and attempt to call back. Anyone using the Orca portal to allocate a DID to a SIP-Registration based SIP trunk may experience errors during this brief moment. Ongoing calls will remain unaffected during this brief period. SIP Registers should remain unaffected throughout the period. ## Support If you have any questions surrounding this work, please reach out to our support team at support@fuse2.net, who will be more than happy to discuss this with you.
Notice to Customers - PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619)
Maintenance · 23 Oct 2026, 13:02 · resolved 13 days ago
- resolved23 Oct, 13:15
  The scheduled maintenance window ended at 23 Oct 2026, 13:03. Closed automatically by the status page.
- identified23 Oct, 13:11
  Components: MyPhones/Evonex, Hosted 3CX, Inbound Call Termination, ORCA Window: 2026-10-23T12:02:00+00:00 → 2026-10-23T12:03:00+00:00 Fuse 2 is aware of the two critical PHP vulnerabilities known as “PHP2Shell” (CVE-2026-109618 and CVE-2026-109619). The PHP project released a security fix for them on 21 October. These flaws let an attacker run code remotely on affected PHP installations, and they are being actively exploited. We have reviewed all of our products, services and internal systems. Most of them, including our hosted telephony platform, and supporting overlay products, do not use PHP and are not affected. Where an internal system does use PHP, we have applied the security update. If you have any questions, please contact our Support Team.
PHP Security Vulnerability
Major · 23 Oct 2026, 12:08 · resolved 7 days ago
- resolved29 Oct, 09:18
  Closed by an administrator.
- monitoring23 Oct, 12:08
  Components: ORCA On 21 October a critical security vulnerability was published in PHP, a widely used web software component. We reviewed every Fuse 2 system the same day. Where PHP was in use we applied the fixed version on 22 October. This covered the Orca portal and a small number of our internal monitoring and support systems. Each one was tested and health checked once the work was done. Our voice services don't rely on PHP, so calls carried on as normal throughout.
Upgrade work in our Manchester DC
Maintenance · 20 Oct 2026, 20:00 · resolved 16 days ago
- resolved23 Oct, 12:00
  The scheduled maintenance window ended at 20 Oct 2026, 23:00. Closed automatically by the status page.
- identified14 Oct, 17:02
  Components: ORCA Window: 2026-10-20T19:00:00+00:00 → 2026-10-20T22:00:00+00:00 ### What is being done We are conducting upgrade work within our Manchester DC to improve our network security, resiliency and availability. ### Who will be affected The Orca Platform may experience drops in connectivity for a short period during the maintenance. All voice traffic will remain unaffected throughout the maintenance. ### Support If you have any questions surrounding this work, please reach out to our support team at support@fuse2.net, who will be more than happy to discuss this with you.
- identified6 Oct, 14:13
  Components: ORCA Window: 2026-10-15T19:00:00+00:00 → 2026-10-15T22:00:00+00:00 ### What is being done We are conducting upgrade work within our Manchester DC to improve our network security, resiliency and availability. ### Who will be affected The Orca Platform may experience drops in connectivity for a short period during the maintenance. All voice traffic will remain unaffected throughout the maintenance. ### Support If you have any questions surrounding this work, please reach out to our support team at support@fuse2.net, who will be more than happy to discuss this with you.
SIP Registration Interruption
Major · 20 Oct 2026, 10:57 · resolved 7 days ago
- resolved29 Oct, 09:18
  Closed by an administrator.
- monitoring20 Oct, 10:57
  Components: SIP Trunks - SIP Registration At approximately 10:17 BST today, some customers saw their SIP trunk registrations drop for around 45 seconds before recovering automatically. Inbound and outbound calls may have failed during this time. Service has been stable since then. Our engineering team is investigating the cause. We apologise for any disruption. Action may be needed: If you use 3CX Free, or a PBX that doesn’t automatically re-register, your trunk may still be unregistered. Please check your trunk status and re-register it manually if needed. If you’re still having problems, please contact our support team.
Disruption to a some SIPREG trunks
Major · 14 Oct 2026, 00:41 · resolved 7 days ago
- resolved29 Oct, 09:17
  Closed by an administrator.
- monitoring14 Oct, 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.
Upgrade work on the SIP Registration Platform
Maintenance · 13 Oct 2026, 22:00 · resolved 22 days ago
- resolved23 Oct, 12:00
  The scheduled maintenance window ended at 14 Oct 2026, 02:00. Closed automatically by the status page.
- identified1 Oct, 15:20
  Components: SIP Trunks - SIP Registration Window: 2026-10-13T21:00:00+00:00 → 2026-10-14T01:00:00+00:00 Fuse 2 are planning to conduct upgrade work on our SIP Registration Platform on the 13th of October, 2026 at 22:00 BST. This work is to support our future plans for new product development. We do not expect any impact to service during this maintenance window. Please feel free to reach out to our support team at support@fuse2.net if you would like any further information.
Planned Maintenance: Carrier Platform Update
Maintenance · 13 Oct 2026, 08:00 · resolved 23 days ago
- resolved23 Oct, 12:00
  The scheduled maintenance window ended at 13 Oct 2026, 09:00. Closed automatically by the status page.
- identified12 Oct, 16:46
  Components: Inbound Call Termination Window: 2026-10-13T07:00:00+00:00 → 2026-10-13T08:00:00+00:00 ## Summary BT, one of our carriers handling a large share of inbound calls to the Fuse 2 network, is migrating to a new platform. ## What's changing and why - **When:** Tuesday 13 October 2026, 08:00 (BST) - **Why:** BT's current inbound platform is nearing end of life and is being replaced with upgraded, modern infrastructure. ## Who is affected Inbound calls routed via BT. This covers several Fuse 2 Ofcom number ranges and ported-in numbers across the network. ## Expected impact We don't expect any impact on call traffic. We've tested the new platform with BT and have carried out migrations like this before. ## Action required > No action is required. If you notice any problems with calls after the change, such as failed, dropped or poor-quality inbound calls, please email **support@fuse2.net**. For urgent issues, call **+44 330 088 0333**. ## Need help? Contact support@fuse2.net and quote this notice.
Routine Maintenance: EMEA POP SBC Certificate Renewal.
Maintenance · 8 Oct 2026, 21:00 · resolved 28 days ago
- resolved23 Oct, 12:00
  The scheduled maintenance window ended at 8 Oct 2026, 22:00. Closed automatically by the status page.
- identified7 Oct, 15:00
  Components: Microsoft Teams Direct Routing Window: 2026-10-08T20:00:00+00:00 → 2026-10-08T21:00:00+00:00 We're renewing the security certificate used for Microsoft Teams connections across our Oracle EMEA (*.uk1/*.uk2) SBC infrastructure. This is routine maintenance to ensure continued service for customers in the region.
- identified14 Sept, 10:21
  Components: Microsoft Teams Direct Routing Window: 2026-10-07T20:00:00+00:00 → 2026-10-07T21:00:00+00:00 We're renewing the security certificate used for Microsoft Teams connections across our Oracle EMEA (*.uk1/*.uk2) SBC infrastructure. This is routine maintenance to ensure continued service for customers in the region.