Some systems are experiencing issues.
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-03-20 00:12:59
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-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 09:01:33
Last updated 2026-04-17 13:42:13
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
The issue was resolved.
We have identified and fixed the root cause. We are now monitoring the issue.
We have detected an issue with the cloud server creation process on Arvancloud's services, which results in failures when attempting to create virtual machines. We are investigating the situation and further updates will be posted in this thread.
The issue was resolved.
We have identified and fixed the root cause. We are now monitoring the issue.
We detected an issue affecting inbound traffic in the Tehran region for the CaaS service. Our engineers are investigating the cause of the problem.
The Log Forwarding service has recovered. No anomalies were detected during the monitoring period, and the issue was fully resolved at 2:54 PM.
We have detected an issue on Log Forwarding service. Our engineers are investigating the issue, and further updates will be posted in this thread.
The issue was resolved.
We have identified and fixed the root cause. We are now monitoring the issue.
There is an ongoing incident on Object Storage panel service. We are investigating the situation and further updates will be posted in this thread.
no further anomalies were detected. We now consider this incident to be resolved.
We have identified and fixed the root cause. We are now monitoring the issue.
We have recieved increased reports on domain resolution issues.
no further anomalies were detected. We now consider this incident to be resolved.
We have identified and fixed the root cause. We are now monitoring the issue.
We have detected an issue with Edge Computing api. We are investigating this matter further.
The issue was caused by incorrect changes that had been applied to the network configuration.
These changes have now been rolled back, and connectivity between the Forough datacenter and the Bamdad, Simin, and Shariar datacenters has been restored.
The incident is now resolved.
Starting at 19:00 Tehran time, we identified a network connectivity issue between the Forough datacenter and the Bamdad, Simin, and Shariar datacenters.
As a result, connectivity from the Forough datacenter toward the mentioned datacenters is currently unavailable. Likewise, connectivity from the Bamdad, Simin, and Shariar datacenters toward the Forough network is also unavailable.
Our engineering teams are actively investigating and working to resolve this incident. Further updates will be shared as soon as more information becomes available or connectivity is restored.
Thank you for your patience and understanding.