Cloud Tree Logo

Live Service Status

Hosting

DNS Name Servers

operational

VPS21

operational

VPS22

operational

VPS23

operational

VPS24

operational

VPS25

operational

Web Hosting

operational

Communication

4G Data SIM

operational

Broadband

operational

CT-VoIP Phone Service

operational

Leased Line

operational

Mobile SIMS

operational

SIP Trunks

operational

Teams Direct Routing

operational

Internal

CloudTree Support Services

operational

MyCloudTree

operational

Other

Advanced Email Protection

operational

API Gateway

operational

CT-Prepare Backup Services

operational

Email Service

operational

Microsoft 365

operational

Active Events

Resolved Events

Cloud-Tree Inbound email

2025-08-05 08:28

An update to one of our own DNS records caused an email routing issue meaning that emails to us were not delivered over the last 24 hours. If you contacted support during this period and did not receive a ticket number, please assume we did not receive your email and send us a new email again.
Services to our email systems has been working again since 09:30 5/8/25

Updates:

Resolved
2025-08-05 08:38

Emails are again being delivered normally

Outbound calling issue

2025-07-24 11:11

We’re currently investigating an issue affecting outbound calls routed through a certain carrier. Calls are failing with a 408 Request Timeout response.

We’ve engaged with the carrier, and they are actively investigating the issue on their upstream systems.

We apologise for the disruption and will provide an update within the next 30 minutes.

Updates:

Update - Investigating
2025-07-24 11:27

The carrier is still investigating the issue affecting outbound calls, which continue to return a 408 Request Timeout response. We remain in contact with their support team and have escalated the case for further investigation.

Update - Investigating
2025-07-24 13:45

We have not yet received a further update regarding the ongoing incident affecting calls to EE & some BT numbers. The carrier has confirmed that EE is actively working to resolve the issue on their network, and we are continuing to monitor the situation closely.

Carrier Update
2025-07-24 14:11

We have not yet received a further update regarding the ongoing incident affecting calls to EE & other networks such as BT, Three and Vodafone are impacted. They are actively working to resolve the issue on their network, and we are continuing to monitor the situation closely.

Update - In Progress
2025-07-24 15:42

The Carrier has confirmed they are working to resolve this P1 incident on their network.

Ongoing
2025-07-24 19:16

Following on from our previous updates, we still await updates on the fault calling mobile numbers but we continue to monitor. The situation is now being updated in mainstream media so we will not send further updates this evening. We will provide a further update tomorrow morning. We apologise for the inconvenience caused.

Update-Services returning
2025-07-24 19:18

We are starting to see services returning to normal. We will continue to monitor until we receive official notification from the mobile operator.

Resolved
2025-07-28 07:11

We have been monitoring EE services for voice over the weekend and now see services running as normal. Please contact support if you continue to have any issues.

Loss of Service on Broadband Connections

2025-07-15 08:19

We are currently aware of an issue affecting broadband connectivity for a subset of our customers whose services route through one of our upstream carriers, Virgin Media. Their Network Engineering and Systems teams are actively investigating and working to identify the root cause.

We sincerely apologise for the inconvenience this may be causing and appreciate your patience while the matter is being addressed.

Updates:

Incident resolved
2025-07-15 08:42

We can now confirm that broadband services affected by the earlier issue with our upstream carrier, Virgin Media, have been fully restored. We sincerely apologise for the disruption this may have caused and appreciate your patience while the issue was being resolved.