Previous incidents

Our platform team is currently investigating an issue caused by a spike in traffic to one of our mail servers. This may result in slower connections when accessing email via apps/clients or webmail.

DDoS protection measures have been activated, and our SRE team is actively working to mitigate the impact while systems adjust to the increased traffic.

We apologise for any inconvenience and will provide further updates as they become available.

Update - The issue has now been resolved, and everything should be back to normal. We wiill continue to monitor things from our side.

The incident was caused by a sudden spike in traffic to the server, which triggered our DDoS protection and traffic filtering systems.

Cluster 56 (web197, 198, 199, 200) recovered.

Shared cPanel - Server 3 recovered.

Cluster 26 (web110, 111, 112, 113) recovered.

Cluster 24 (web100, 101, 102, 103) recovered.

Cluster 24 (web100, 101, 102, 103) recovered.

Shared cPanel - Server 3 recovered.

Cluster 24 (web100, 101, 102, 103) recovered.

Cluster 24 (web100, 101, 102, 103) recovered.

Cluster 35 (web150, 151, 152) recovered.

Shared cPanel - Server 3 recovered.

Cluster 25 (web105, 106, 107, 108) recovered.

Cluster 13 (web47, 48, 49, 50) recovered.

Cluster 13 (web47, 48, 49, 50) recovered.

Cluster 51 (web62, 63, 64, 65) recovered.

We are aware of some connectivity issues across a small number of servers our SRE team are working on this as a top priority, we will update again once further information is available.

Update 11.13 - the issue has now been resolved and services are returning to normal.

Cluster 10 (web32, 33, 34, 35, 36) recovered.

Cluster 10 (web32, 33, 34, 35, 36) recovered.

Cluster 13 (web47, 48, 49, 50) recovered.

Test concluded.

Cluster 26 (web110, 111, 112, 113) recovered.

Cluster 26 (web110, 111, 112, 113) recovered.

We are currently aware of an issue affecting a small number of emails passing through our forwarding servers. In these cases, emails are not being correctly forwarded to their intended destination and may be delayed or remain undelivered.

Our team has identified the behaviour and is actively working with our forwarding platform partner to investigate the root cause and implement a fix as a priority. At this stage, the issue appears to be limited in scope and is not impacting all forwarding t...

Cluster 26 (web110, 111, 112, 113) recovered.

Cluster 26 (web110, 111, 112, 113) recovered.

Cluster 26 (web110, 111, 112, 113) recovered.

Cluster 31 (web135, 136, 137, 138) recovered.