All systems are operational.
Last updated 2026-03-20 00:12:59
Last updated 2026-06-16 14:47:04
Last updated 2026-06-16 14:47:07
Last updated 2026-06-16 14:47:10
Last updated 2026-03-20 00:12:59
Last updated 2026-03-20 00:12:59
Last updated 2026-03-20 00:12:59
Last updated 2026-07-15 11:10:18
Last updated 2026-03-20 00:11:12
Last updated 2026-03-20 00:11:12
Last updated 2026-03-20 00:11:12
Last updated 2026-03-20 00:11:12
Last updated 2026-03-20 00:11:12
Last updated 2026-03-20 00:11:12
Last updated 2026-03-20 00:11:12
Last updated 2026-03-20 00:11:12
Last updated 2026-03-20 00:11:12
Last updated 2026-04-17 13:42:13
Last updated 2026-04-17 09:01:33
Last updated 2026-04-04 18:36:37
Last updated 2026-04-04 18:36:37
Last updated 2026-04-04 18:36:37
Last updated 2026-04-04 18:36:37
Last updated 2026-04-04 18:36:37
Last updated 2026-04-04 18:36:37
Last updated 2026-04-04 18:36:37
Last updated 2026-04-04 18:36:37
Last updated 2026-04-04 18:36:37
Last updated 2026-04-04 18:36:37
Last updated 2026-04-04 18:36:37
Last updated 2026-03-17 10:55:32
Last updated 2026-03-17 10:55:37
Last updated 2026-03-17 10:55:41
Last updated 2026-03-17 10:55:46
Last updated 2026-03-17 10:55:50
Last updated 2026-03-20 00:12:14
Last updated 2026-03-17 10:56:20
Last updated 2026-03-17 10:56:23
Last updated 2026-03-17 10:56:26
Last updated 2026-03-17 10:56:30
Last updated 2026-03-17 10:56:33
Last updated 2026-03-17 10:56:36
Last updated 2026-04-01 14:56:02
Last updated 2026-03-20 00:12:33
Last updated 2026-03-17 10:56:53
Last updated 2026-03-18 23:23:35
Last updated 2026-03-17 18:42:19
Last updated 2026-03-16 17:29:13
Last updated 2026-03-16 17:29:18
Last updated 2026-03-17 18:42:00
Following investigation, the root cause was identified and mitigated. A fix was deployed to resolve the A record resolution issues, and service has been restored to normal operation.
The issue considered to be resolved and we are watching for further actions.
We are currently investigating reports of A record resolution issues impacting a subset of domains. Efforts are ongoing to identify the underlying root cause.
The issue has been resolved.
We have identified the root cause of the issue and are currently applying a fix. We will provide additional updates as progress continues.
We have encountered an issue with the SSL configuration on some domains.
Our technical team is currently investigating the matter and working to resolve it.
The issue is resolved on 12:29 PM.
We have identified a service disruption affecting the AIaaS platform and its APIs. Our engineering team is actively investigating the issue and will provide updates in this thread as soon as more information becomes available.
The incident has now been fully resolved, and all affected services are operating normally. If you continue to experience any issues, please contact our Support Team for assistance.
The issue affecting WAF Log Forwarding and WAF Reports in the CDN Panel has also been resolved. We are closely monitoring the situation and will provide further updates as needed.
At 13:12, the issues affecting Error Log Forwarding and Domain Error Reports in the CDN Panel were resolved. WAF Log Forwarding and WAF Reports in the CDN Panel remain impacted. We will provide further updates soon.
We have identified an issue affecting CDN WAF and Error Log Forwarding, as well as Domain Reports in the CDN Panel. Our technical team is actively investigating the matter, and we will share further updates as soon as more information becomes available.
he connectivity issue has been fully resolved, and all services are operating normally. We have confirmed that the fix has been successfully applied and the service is stable. If you continue to experience any issues, please contact our support team for further assistance.
We have identified the root cause of the issue and are currently applying a fix. We will provide additional updates as progress continues.
We have detected a connectivity issue affecting our Object Storage service. Our team is actively investigating the root cause and working to restore normal connectivity as quickly as possible. We will provide further updates as more information becomes available.
The issue has been resolved and all affected servers have been successfully restored.
Solution has been applied and we are watching out the situation for further actions.
We have identified the root cause and we are working on the solution.
We have received reports of our cloud server (IaaS) accounting system causing servers to not be restored to Active state, and we are investigating this issue.