65 recorded Azion incidents since December 2024, with official updates, affected components, duration and resolution information.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating reports of increased latency for domains using ANAME records at the zone apex. Affected requests may be served from edge locations outside the expected region. Other DNS record types are not impacted and all edge locations are operating normally. We will post an update as soon as we have more information.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently under performance issues on our Orchestration platform. During this period, operations such as adding, removing, or editing Azion products via Console, CLI or API may take longer than usual, or return errors. All services that are accessible to end-users remain fully active and 100% functional. The impact is limited solely to the processing of new changes.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating increased propagation time for configuration changes to edge nodes. Content delivery is not affected and existing configurations continue to be served normally. We will provide an update shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating reports of intermittent DNS resolution failures affecting the Object Storage endpoint s3.us-east-005.azionstorage.net. Some clients may receive "host not found" errors (e.g., ENOTFOUND) when trying to connect, depending on the DNS resolver in use.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating degraded performance on Object Storage. Users may experience intermittent errors.
We are continuing to work on a fix for this issue.
We have identified the cause of the degraded performance on Object Storage as elevated latency in an upstream storage component. Users may experience slower uploads, timeouts, and intermittent errors when uploading or retrieving objects. Our team is working on mitigation and closely monitoring the situation. We will provide another update as soon as possible.
We are continuously working to mitigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We've identified an issue affecting Data Stream and are actively working to resolve it. During this time, you may experience delays in Data Stream processing.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with the Azion Console and Data Services. Our team is actively working to restore services. We will provide another update as soon as we have more information.
We have identified an issue with our Network Links
We are continuing to work on a fix for this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue with the Azion Console. Our team is actively working to restore services. We will provide another update as soon as we have more information.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are currently investigating an issue with the Azion Console where Edge Functions are not being displayed in the listing view. When customers open the Edge Functions list, existing functions may not appear on screen. This is a display-only issue and does not affect your functions. All Edge Functions remain deployed and continue to execute normally, with no impact to traffic or production workloads — they are simply not being shown in the Console listing at this time. Our team is actively working to restore full listing functionality. We will provide another update as soon as we have more information. We apologize for any inconvenience.
We've identified that this issue also affects the API, not only the Console — impacting the Edge Functions listing on both. Edge Functions themselves continue to operate normally, with no impact to execution or traffic. Only the listing is affected. Our team remains engaged and we'll share more as soon as we have an update.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are seeing an issue in our CDN services. Customers may experience degraded performance in this region.
We are continuing to work on a fix for this issue.
Our team has identified the issue and is currently applying a fix. Estimated time to recovery is 10 minutes.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are seeing an issue in our CDN services located in São Paulo, Brazil. Customers may experience degraded performance in this region.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue affecting Real Time Events. Our team is working to restore normal functionality as quickly as possible.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
On July 7, between 14:30 and 15:30 UTC (11:30–12:30 BRT), we experienced a critical network issue in our Ashburn, USA (IAD) datacenter. Users may have experienced DNS resolution failures, or 5xx errors when accessing the Console, APIs, and content delivery services. Our engineering team identified and mitigated the issue, and all services have been fully restored. We are monitoring closely to ensure stability.
We are currently experiencing delays in data updates within Data Services, impacting the Data Stream, Real-Time Events, and Real-Time Metrics products. Users may notice delayed data processing and slower propagation of updates. Our team is actively investigating and working on mitigation.
The issue has been identified and a fix is being implemented.
A fix has been implemented and data processing has resumed. A backlog accumulated during the incident is still being processed, so delays in data processing and update propagation are still expected while the queues drain. We continue to actively monitor the recovery until processing fully catches up.
The fix remains in place and data processing continues to recover. We are still working through the backlog that built up during the incident, so some delay in data processing and update propagation may persist while the queues drain. Our team continues to monitor progress closely and will provide further updates as the backlog clears.
The fix remains in place and the backlog has started to decrease. Data processing is steadily catching up, though some delay in data processing and update propagation may still be observed until the queues are fully drained. Our team continues to monitor the recovery closely and will provide further updates as processing returns to normal.
A fix has been implemented and data processing has fully caught up. The backlog that accumulated during the incident has been drained, and data processing and update propagation have returned to normal levels. We are now monitoring the affected services to ensure stability before marking this incident as resolved.
We have identified a recurrence of processing delays affecting Data Services. Our team has identified the cause and is actively working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently under performance issues on our Orchestration platform. During this period, operations such as adding, removing, or editing Azion products via Console, CLI or API may take longer than usual, or return errors. All services that are accessible to end-users remain fully active and 100% functional. The impact is limited solely to the processing of new changes.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating connectivity issues affecting Object Storage. Some users may experience failures or timeouts.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating degraded performance affecting object uploads to Object Storage. Users may experience intermittent 5xx errors during upload attempts.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating a critical network-related issue affecting our Miami, USA datacenter. Most services have already been redirected to other regions and are operating normally. However, data services and live streaming are still experiencing instability and are currently in the process of being rerouted. Our engineering teams are actively working with our datacenter provider to identify the root cause and fully restore connectivity as quickly as possible.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
