Azion Outage History

Azion partial outage View live status →

Pingoru has recorded 54 incidents for Azion: 53 in the last 12 months and 11 in the last 90 days.

Source: status.azion.com

54incidents recorded
53last 12 months
11last 90 days
7 hourstypical duration
Incidents per month
0510AprMayJunJulAugSepOct6
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct5%
Pingoru began tracking Azion in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20269122 of 720 (17%)
May 2026873 of 744 (10%)
June 2026230 of 720 (4%)
July 2026425 of 744 (3%)
August 202622 of 744 (0%)
September 202626 of 720 (1%)
October 2026626 of 513 (5%)

Incidents, newest first

Minor October 15, 2026 Errors loading WAF Events in Console 54m Web Application Firewall

Started Oct 15, 2026, 02:23 PM UTC· resolved Oct 15, 2026, 03:17 PM UTC

  1. investigating Oct 15, 2026, 02:23 PM UTC

    We are currently investigating this issue.

  2. identified Oct 15, 2026, 02:29 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 15, 2026, 02:54 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 15, 2026, 03:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 10, 2026 Increased latency for some domains using ANAME records 3h 4m Edge DNS

Started Oct 10, 2026, 09:26 PM UTC· resolved Oct 11, 2026, 12:30 AM UTC

  1. investigating Oct 10, 2026, 09:26 PM UTC

    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.

  2. identified Oct 10, 2026, 10:02 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 11, 2026, 12:15 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 11, 2026, 12:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 8, 2026 Performance Issues in Edge Orchestration 1h 51m Orchestrator

Started Oct 08, 2026, 05:49 PM UTC· resolved Oct 08, 2026, 07:40 PM UTC

  1. investigating Oct 08, 2026, 05:49 PM UTC

    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.

  2. identified Oct 08, 2026, 05:49 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 08, 2026, 07:11 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 08, 2026, 07:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 5, 2026 Delayed configuration propagation to edge nodes 1h 18m Orchestrator

Started Oct 05, 2026, 07:46 PM UTC· resolved Oct 05, 2026, 09:05 PM UTC

  1. investigating Oct 05, 2026, 07:46 PM UTC

    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.

  2. identified Oct 05, 2026, 07:53 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 05, 2026, 07:57 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 05, 2026, 09:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 3, 2026 Intermittent DNS resolution failures for Object Storage endpoint (us-east-005) 3h 12m Object Storage

Started Oct 03, 2026, 02:40 PM UTC· resolved Oct 03, 2026, 05:52 PM UTC

  1. investigating Oct 03, 2026, 02:40 PM UTC

    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.

  2. identified Oct 03, 2026, 02:55 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 03, 2026, 03:11 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 03, 2026, 05:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 2, 2026 Performance Issues on Object Storage 15h 59m Object Storage

Started Oct 02, 2026, 07:47 PM UTC· resolved Oct 03, 2026, 11:47 AM UTC

  1. identified Oct 02, 2026, 07:47 PM UTC

    We are investigating degraded performance on Object Storage. Users may experience intermittent errors.

  2. identified Oct 02, 2026, 07:51 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Oct 02, 2026, 07:58 PM UTC

    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.

  4. identified Oct 02, 2026, 11:57 PM UTC

    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.

  5. identified Oct 03, 2026, 12:32 AM UTC

    We are continuously working to mitigate this issue.

  6. identified Oct 03, 2026, 02:51 AM UTC

    We are continuously working to mitigate this issue.

  7. identified Oct 03, 2026, 06:09 AM UTC

    We are continuously working to mitigate this issue.

  8. monitoring Oct 03, 2026, 10:01 AM UTC

    A fix has been implemented and we are monitoring the results.

  9. resolved Oct 03, 2026, 11:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 23, 2026 Performance issues on Data Stream 14m Data Stream

Started Sep 23, 2026, 07:09 PM UTC· resolved Sep 23, 2026, 07:24 PM UTC

  1. investigating Sep 23, 2026, 07:09 PM UTC

    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.

  2. identified Sep 23, 2026, 07:12 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Sep 23, 2026, 07:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 23, 2026, 07:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 2, 2026 Performance Issues on Azion Console, APIs, Application Performance and Application Observability. 5h 53m APIs, Data Stream, Applications, Application Accelerator and 4 more

Started Sep 02, 2026, 04:11 PM UTC· resolved Sep 02, 2026, 10:05 PM UTC

  1. investigating Sep 02, 2026, 04:11 PM UTC

    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.

  2. identified Sep 02, 2026, 04:23 PM UTC

    We have identified an issue with our Network Links

  3. identified Sep 02, 2026, 05:07 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Sep 02, 2026, 06:27 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. identified Sep 02, 2026, 08:33 PM UTC

    The issue has been identified and a fix is being implemented.

  6. monitoring Sep 02, 2026, 09:01 PM UTC

    A fix has been implemented and we are monitoring the results.

  7. monitoring Sep 02, 2026, 09:01 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved Sep 02, 2026, 10:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 17, 2026 Performance Issues on Console 53m Azion Console

Started Aug 17, 2026, 05:05 PM UTC· resolved Aug 17, 2026, 05:58 PM UTC

  1. investigating Aug 17, 2026, 05:05 PM UTC

    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.

  2. identified Aug 17, 2026, 05:22 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 17, 2026, 05:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 17, 2026, 05:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 14, 2026 Performance issues on Console 41m APIs, Azion Console

Started Aug 14, 2026, 04:23 PM UTC· resolved Aug 14, 2026, 05:05 PM UTC

  1. investigating Aug 14, 2026, 04:23 PM UTC

    We are currently investigating this issue.

  2. identified Aug 14, 2026, 04:27 PM UTC

    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.

  3. identified Aug 14, 2026, 04:33 PM UTC

    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.

  4. monitoring Aug 14, 2026, 04:41 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 14, 2026, 05:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 24, 2026 Performance issues on Edge Functions 43m Functions, Applications, Application Accelerator, Cache and 3 more

Started Jul 24, 2026, 05:53 PM UTC· resolved Jul 24, 2026, 06:36 PM UTC

  1. identified Jul 24, 2026, 05:53 PM UTC

    We are seeing an issue in our CDN services. Customers may experience degraded performance in this region.

  2. identified Jul 24, 2026, 06:01 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Jul 24, 2026, 06:02 PM UTC

    Our team has identified the issue and is currently applying a fix. Estimated time to recovery is 10 minutes.

  4. monitoring Jul 24, 2026, 06:13 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jul 24, 2026, 06:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 22, 2026 Performance issues on CDN 16m Applications, Application Accelerator, DDoS Protection, Cache and 13 more

Started Jul 22, 2026, 12:12 PM UTC· resolved Jul 22, 2026, 12:28 PM UTC

  1. investigating Jul 22, 2026, 12:12 PM UTC

    We are seeing an issue in our CDN services located in São Paulo, Brazil. Customers may experience degraded performance in this region.

  2. identified Jul 22, 2026, 12:12 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 22, 2026, 12:13 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 22, 2026, 12:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 21, 2026 Real Time Events issue 1h 27m Real-Time Events

Started Jul 21, 2026, 08:07 AM UTC· resolved Jul 21, 2026, 09:35 AM UTC

  1. investigating Jul 21, 2026, 08:07 AM UTC

    We are currently investigating an issue affecting Real Time Events. Our team is working to restore normal functionality as quickly as possible.

  2. identified Jul 21, 2026, 08:29 AM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jul 21, 2026, 09:00 AM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Jul 21, 2026, 09:25 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jul 21, 2026, 09:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 7, 2026 Network-Related Performance Issues in USA/Ashburn Region 22h 30m

Started Jul 07, 2026, 02:00 PM UTC· resolved Jul 08, 2026, 12:30 PM UTC

  1. resolved Jul 08, 2026, 08:08 PM UTC

    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 received 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.

Read the full incident report →

Minor June 23, 2026 Performance Issues in Data Services 1d 3h Data Stream, Real-Time Events, Real-Time Metrics

Started Jun 23, 2026, 11:12 PM UTC· resolved Jun 25, 2026, 03:09 AM UTC

  1. investigating Jun 23, 2026, 11:12 PM UTC

    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.

  2. identified Jun 23, 2026, 11:14 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jun 24, 2026, 10:54 AM UTC

    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.

  4. identified Jun 24, 2026, 12:20 PM UTC

    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.

  5. identified Jun 24, 2026, 01:12 PM UTC

    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.

  6. monitoring Jun 24, 2026, 03:42 PM UTC

    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.

  7. identified Jun 24, 2026, 05:32 PM UTC

    We have identified a recurrence of processing delays affecting Data Services. Our team has identified the cause and is actively working on a fix.

  8. monitoring Jun 24, 2026, 09:40 PM UTC

    A fix has been implemented and we are monitoring the results.

  9. resolved Jun 25, 2026, 03:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 29, 2026 Partial Outage — Azion Object Storage 7h 34m Object Storage

Started May 29, 2026, 03:16 PM UTC· resolved May 29, 2026, 10:51 PM UTC

  1. investigating May 29, 2026, 03:16 PM UTC

    We are currently investigating connectivity issues affecting Object Storage. Some users may experience failures or timeouts.

  2. investigating May 29, 2026, 04:14 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 29, 2026, 04:59 PM UTC

    We are continuing to investigate this issue.

  4. investigating May 29, 2026, 06:15 PM UTC

    We are continuing to investigate this issue.

  5. investigating May 29, 2026, 06:49 PM UTC

    We are continuing to investigate this issue.

  6. identified May 29, 2026, 07:51 PM UTC

    The issue has been identified and a fix is being implemented.

  7. identified May 29, 2026, 09:03 PM UTC

    The issue has been identified and a fix is being implemented.

  8. monitoring May 29, 2026, 09:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  9. resolved May 29, 2026, 10:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026 Performance issues on Object Storage 2h 23m Object Storage

Started May 28, 2026, 09:29 PM UTC· resolved May 28, 2026, 11:53 PM UTC

  1. investigating May 28, 2026, 09:29 PM UTC

    We are investigating degraded performance affecting object uploads to Object Storage. Users may experience intermittent 5xx errors during upload attempts.

  2. identified May 28, 2026, 09:30 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 28, 2026, 10:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 28, 2026, 11:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026 Network-Related Performance Issues in USA/Miami Region 8h 52m Real-Time Events, Object Storage, Real-Time Metrics, Orchestrator and 2 more

Started May 28, 2026, 04:32 AM UTC· resolved May 28, 2026, 01:24 PM UTC

  1. investigating May 28, 2026, 04:32 AM UTC

    We are currently investigating this issue.

  2. investigating May 28, 2026, 04:43 AM UTC

    We are continuing to investigate this issue.

  3. identified May 28, 2026, 04:51 AM UTC

    The issue has been identified and a fix is being implemented.

  4. investigating May 28, 2026, 05:07 AM UTC

    We are currently investigating this issue.

  5. monitoring May 28, 2026, 09:20 AM UTC

    A fix has been implemented and we are monitoring the results.

  6. monitoring May 28, 2026, 09:20 AM UTC

    We are continuing to monitor for any further issues.

  7. resolved May 28, 2026, 01:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026 Degraded Performance in Configuration Propagation 2h 18m Orchestrator

Started May 20, 2026, 03:25 PM UTC· resolved May 20, 2026, 05:43 PM UTC

  1. identified May 20, 2026, 03:25 PM UTC

    We are currently investigating performance issues affecting our Orchestration platform. Operations such as adding, removing or editing Azion products via the Console or API may take longer than usual. Our engineering team is actively working to identify the root cause and restore full performance as quickly as possible.

  2. monitoring May 20, 2026, 03:59 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 20, 2026, 05:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2026 Performance Issues in DNS services 10h 27m Applications, Application Accelerator, Cache, Edge DNS

Started Apr 28, 2026, 12:19 PM UTC· resolved Apr 28, 2026, 10:46 PM UTC

  1. investigating Apr 28, 2026, 12:19 PM UTC

    We are currently experiencing a partial disruption affecting our DNS services, which may impact domain resolution for some users. Our Engineering team has identified the issue and is actively working on mitigation efforts to restore full service stability as quickly as possible. We will continue to provide timely updates as more information becomes available.

  2. identified Apr 28, 2026, 12:35 PM UTC

    We are still actively working to mitigate the ongoing DNS service disruption. Our Engineering team continues to investigate and apply corrective actions to restore full stability. We appreciate your patience and will provide further updates as progress is made.

  3. identified Apr 28, 2026, 12:51 PM UTC

    Mitigation efforts are still in progress, and our Engineering team continues to work on restoring full DNS service stability. We are seeing gradual improvements, but some users may still experience intermittent issues with domain resolution. We will keep monitoring the situation closely and share further updates as new information becomes available.

  4. identified Apr 28, 2026, 01:09 PM UTC

    Investigation efforts are still in progress, and our Engineering team continues to analyze the issue affecting DNS services. We are actively working to identify the root cause and determine the appropriate mitigation actions. We will continue to provide updates as more information becomes available.

  5. monitoring Apr 28, 2026, 01:17 PM UTC

    Mitigation measures have been successfully applied, and the incident affecting DNS services has been mitigated. Service stability has been restored, and we are continuing to monitor the environment to ensure normal operation. We will provide a final update once the investigation is fully concluded.

  6. identified Apr 28, 2026, 03:24 PM UTC

    The issue has been identified and a fix is being implemented.

  7. identified Apr 28, 2026, 03:24 PM UTC

    We are continuing to work on a fix for this issue.

  8. monitoring Apr 28, 2026, 03:35 PM UTC

    A fix has been implemented and we are monitoring the results.

  9. identified Apr 28, 2026, 05:55 PM UTC

    The issue has been identified and a fix is being implemented.

  10. monitoring Apr 28, 2026, 06:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  11. monitoring Apr 28, 2026, 09:27 PM UTC

    We are continuing to monitor for any further issues.

  12. resolved Apr 28, 2026, 10:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 27, 2026 Performance Issues in Tiered Cache 18h 47m Tiered Cache

Started Apr 27, 2026, 06:05 PM UTC· resolved Apr 28, 2026, 12:53 PM UTC

  1. investigating Apr 27, 2026, 06:05 PM UTC

    We have identified the cause of the issue affecting Tiered Cache. Some requests are experiencing increased latency and intermittent errors.

  2. identified Apr 27, 2026, 06:24 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Apr 28, 2026, 12:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 22, 2026 Performance Issues in Azion Console 17h 58m Azion Console

Started Apr 22, 2026, 06:41 PM UTC· resolved Apr 23, 2026, 12:39 PM UTC

  1. investigating Apr 22, 2026, 06:41 PM UTC

    We have identified an issue impacting login and authentication on our SSO and Auth platform. Some users may experience failures when attempting to sign in or complete authentication requests. Our team is actively working to identify the cause and restore normal service.

  2. monitoring Apr 22, 2026, 07:26 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 23, 2026, 12:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 17, 2026 Performance Issues in Content Delivery 5h 59m Applications, Application Accelerator, Cache

Started Apr 17, 2026, 12:23 PM UTC· resolved Apr 17, 2026, 06:22 PM UTC

  1. investigating Apr 17, 2026, 12:23 PM UTC

    We are currently experiencing elevated latency and increased error rates impacting the content delivery service across the US and Europe regions. Users may encounter slower response times and degraded performance when accessing content.

  2. identified Apr 17, 2026, 12:37 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Apr 17, 2026, 12:48 PM UTC

    Latency remains elevated, and the content delivery service continues to be impacted. We are actively working on mitigation, and users may experience slower response times and intermittent issues when accessing content.

  4. identified Apr 17, 2026, 01:11 PM UTC

    We are continuing to observe elevated latency affecting the content delivery service. Mitigation efforts are ongoing, and users may still experience slower response times and intermittent issues when accessing content.

  5. monitoring Apr 17, 2026, 01:26 PM UTC

    The incident has been mitigated and the content delivery service is operating normally. We are continuing to monitor the situation to ensure stability.

  6. identified Apr 17, 2026, 02:55 PM UTC

    We are currently observing a recurrence of elevated latency affecting the content delivery service. Users may experience slower response times and intermittent issues when accessing content. Our team is actively investigating and working to mitigate the impact.

  7. monitoring Apr 17, 2026, 04:05 PM UTC

    The incident has been mitigated, and the content delivery service is operating normally. We are continuing to monitor the situation to ensure stability.

  8. resolved Apr 17, 2026, 06:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 7, 2026 Performance Issues in EdgeDNS 45m

Started Apr 07, 2026, 03:00 PM UTC· resolved Apr 07, 2026, 03:45 PM UTC

  1. resolved Apr 14, 2026, 01:53 PM UTC

    Between 15:20 UTC and 15:45 UTC on April 7, 2026, customers experienced degraded DNS resolution in the Brazil region. The incident lasted approximately 25 minutes and has been fully resolved.

Read the full incident report →

Notice March 23, 2026 Performance Issues in Data Stream –

Started Mar 23, 2026, 01:00 PM UTC· resolved Mar 23, 2026, 01:00 PM UTC

  1. resolved Mar 23, 2026, 07:58 PM UTC

    Data Stream experienced a field misalignment issue caused by a recent schema change. A new field was introduced into the log structure without proper backward compatibility handling. As the system relies on positional field mapping, this change caused subsequent fields to shift, leading to incorrect key-value associations during log parsing. Logs generated after the change may contain incorrectly mapped fields, resulting in data inconsistencies and potential misinterpretation by collector systems.

Read the full incident report →