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 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.
After an extensive monitoring period, no further anomalies were detected. We now consider this incident to be resolved.
A fix has been implemented. The Issue is being watched closely.
The issue has returned. We are investigating the matter further.
The issue has been addressed. We are now monitoring the situation.
We have received increased reports on issues with the CDN API.
Outage in Cloud container has been resolved successfully and services are ready to use.
Cloud container services are now up and being watched.
Outage in Cloud server has been resolved successfully and services are ready to use.
Outage in ojbect storage and arvan drive has been resolved successfully and services are ready to use.
Managed database services are now up and being watched.
Cloud server and IaaS services are now up and being watched.
Outage on Object storage and Drive resolved and further actions being watched.
We have detected cooling anomaly on the Simin (ir-central1-b) data center. Our engineers are actively investigating the issue.