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-08-02 13:16:50
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 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-18 23:23:35
Last updated 2026-03-17 10:56:53
Last updated 2026-07-27 12:54:32
Last updated 2026-03-16 17:29:18
Last updated 2026-03-17 18:42:19
Last updated 2026-03-17 18:42:00
Last updated 2026-03-16 17:29:13
There will be scheduled maintenance on the AIaaS Service. During this maintenance, infrastructure changes will be performed. Requests may experience temporary slowness or interruptions for up to 10 minutes.
We have not detected any further anomalies, and the incident is now considered to be resolved. If you are currently experiencing any issues, please contact our Support Team.
This issue and all of affected services are now operating normally and we are monitoring the situation.
Due to this incident, we are experiencing problems accessing the ArvanCloud panel, and network connectivity to the Goethe region is also affected from 12:31 PM. Our engineers are currently investigating the issue. Further updates will be posted in this thread.
We have detected an issue that is affecting CDN performance from international PoP sites to domestic origins , causing slow response times and increased latency. Our team is actively investigating the situation and will provide further updates as we gather more information.
The DNS resolution and sync has now been fully addressed and fixed.
DNS resolution has now been fixed. We are now monitoring the service. The only problem remaining at the moment is the DNS record sync between CDN PoPs.
The DNS Resolution Issue has now also occured at our Iranian PoPs. The problem is being addressed at the moment.
After recent changes, bandwidth in all our Iranian data centers has been restored to full functionality. We are now monitoring this matter.
This issue has affected our DNS Resolution from certain foreign destinations in Europe. We are working on a fix for the problem.
The issue affecting the CDN API has now been resolved.
An issue with a similar root cause has also affected the CDN API. That issue is now also under investigation.
We are experiencing network bandwidth issues across our services. We are now investigating this issue.
This issue is now resolved. If your service is still affected, please contact our support department.
The issue is now resolved. We are monitoring the situation.
We have detected a network issue in the Goethe datacenter (eu-west1-a), which is causing degraded bandwidth performance. We are investigating the issue and will provide further updates here.