Altura Outage History

Started Sep 29, 2026, 02:19 PM UTC· resolved Sep 30, 2026, 08:24 AM UTC

1. investigating Sep 29, 2026, 02:19 PM UTC

   Azure OpenAI service incident in Sweden Central (Azure tracking IDs 7QL5-Z50, 6GL1-QK8 and 2YH0-QL0).

2. monitoring Sep 29, 2026, 03:06 PM UTC

   Azure's main incident 7QL5-Z50 is still Active

3. resolved Sep 30, 2026, 08:24 AM UTC

   ~15:30 UTC: last Azure OpenAI 5xx observed" and "18:42 UTC: Azure marks impact mitigated.

Read the full incident report →

Started Sep 24, 2026, 06:57 AM UTC· resolved Sep 24, 2026, 07:23 AM UTC

1. investigating Sep 24, 2026, 06:57 AM UTC

   We're investigating an issue affecting Workflows and will share an update shortly.

2. resolved Sep 24, 2026, 07:23 AM UTC

   Workflows are working again.

Read the full incident report →

Started Sep 22, 2026, 07:48 AM UTC· resolved Sep 22, 2026, 10:25 AM UTC

1. identified Sep 22, 2026, 07:48 AM UTC

   We’re investigating an issue affecting access to the Altura app. Some users may be unable to sign in or use the product. Our team is working to restore service and will provide another update shortly.

2. identified Sep 22, 2026, 07:53 AM UTC

   We’re investigating an issue affecting access to the Altura app. Some users may be unable to sign in or use the product. Our team is working to restore service and will provide another update shortly.

3. identified Sep 22, 2026, 08:12 AM UTC

   We’re investigating an issue affecting the Altura platform. Login is working, but users cannot be redirected into the app due to the outage. The app itself is currently unavailable. We’re working to restore service and will share an update shortly.

4. monitoring Sep 22, 2026, 09:13 AM UTC

   Service has been restored and we are monitoring the platform closely. Users should again be able to access the app. We will provide further updates if needed.

5. resolved Sep 22, 2026, 10:25 AM UTC

   Service has been restored and the platform is operating normally. Users can access the app again. Thank you for your patience.

Read the full incident report →

Started Sep 02, 2026, 08:24 AM UTC· resolved Sep 04, 2026, 01:08 PM UTC

1. investigating Sep 02, 2026, 08:24 AM UTC

   We're currently investigating a full outage of AI features on the platform.

2. identified Sep 02, 2026, 08:40 AM UTC

   We've identified the issue and are applying fixes to resolve the outage.

3. monitoring Sep 02, 2026, 08:51 AM UTC

   The outage has been resolved and the AI features work again. We're still monitoring the features to make sure they are fully performant again.

4. resolved Sep 02, 2026, 09:04 AM UTC

   The incident has been resolved.

5. resolved Sep 02, 2026, 09:07 AM UTC

   All systems are operation again.

6. identified Sep 02, 2026, 09:17 AM UTC

   The incident reoccurred before the root cause could be completly erradicated. We have identified the issue and the permanent fix will soon be released

7. monitoring Sep 02, 2026, 09:45 AM UTC

   We've deployed the fix and are monitoring systems in case the incident reoccurs

8. investigating Sep 02, 2026, 10:33 AM UTC

   We observed that the performance of the system post hot fix is still degrade. We continue to investigate where the cause of the issue is to identify the quickest path to restore the service completely.

9. identified Sep 02, 2026, 11:40 AM UTC

   We are working on a fix to avoid large files for being requeued for processing while they are still being processed. This should provide relief to the situation and allow us to identify next steps to address all root causes

10. investigating Sep 02, 2026, 12:49 PM UTC

    We have restored the service to it's nominal level of performance and identified what triggers the issue. However we still don't have a permanent fix for it. The next incident update should be expected by the end of the day (around 5PM CEST). The request to all customers for now is to not upload large files for processing (for example, excel files with hundreds of thousands of rows).

11. identified Sep 02, 2026, 02:47 PM UTC

    We're implementing fixes to prevent processing issues with large files. Due to the complexity of the work, we expect these fixes to be released tomorrow by midday (CEST) The next update can be expected by tomorrow morning.

12. identified Sep 03, 2026, 08:06 AM UTC

    We have made several improvements to the stability of the platform and expect 5 more to be completed today. The platform continues to be stable, as long as large files are not submitted for processing. The next incident update should be expected by the end of the day (around 5PM CEST). The request to all customers for now is to not upload large files for processing (for example, excel files with hundreds of thousands of rows).

13. identified Sep 03, 2026, 04:11 PM UTC

    The last platform fix to completely resolve this incident is almost complete and we expect it to be done by 12pm CEST tomorrow. The platform continues to be stable, as long as large files are not submitted for processing. The request to all customers for now is to not upload large files for processing (for example, excel files with hundreds of thousands of rows).

14. resolved Sep 04, 2026, 01:08 PM UTC

    Final fixes have been deployed to production and the resulting performance of document processing increase. Now even large files are able to be processed rapidly without blocking other documents.

Read the full incident report →

Started Aug 27, 2026, 08:54 AM UTC· resolved Aug 27, 2026, 09:08 AM UTC

1. identified Aug 27, 2026, 08:54 AM UTC

   We have identified the issue and are working to fix it!

2. resolved Aug 27, 2026, 09:08 AM UTC

   Issue has been fixed and documents are now processing as normal.

Read the full incident report →

Started Aug 04, 2026, 04:00 PM UTC· resolved Aug 04, 2026, 06:00 PM UTC

1. identified Aug 04, 2026, 04:00 PM UTC

   Users trying to connect their Sharepoint to Altura are seeing authentication errors and are currently unable to successfully add the connection. We are investigating the issue.

2. resolved Aug 04, 2026, 06:00 PM UTC

   We identified that a previous deployment made changes to the authentication method used by Sharepoint, but those changes were not reflected in the Sharepoint connection

Read the full incident report →