Transact Outage History

Started Jun 08, 2026, 01:53 AM UTC· resolved Jun 10, 2026, 09:32 PM UTC

1. monitoring Jun 08, 2026, 01:53 AM UTC

   We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

2. monitoring Jun 08, 2026, 02:36 AM UTC

   We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

3. monitoring Jun 08, 2026, 02:56 AM UTC

   On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.

Read the full incident report →

Started Jun 06, 2026, 11:21 PM UTC· resolved Jun 10, 2026, 01:50 PM UTC

1. monitoring Jun 06, 2026, 11:21 PM UTC

   We are aware of users currently experiencing loading work items across Atlassian products in some regions. We are investigating with urgency and will provide update within one hour.

2. monitoring Jun 07, 2026, 12:07 AM UTC

   A fix has been implemented for the issues some customers have been experiencing with creating and viewing work items in Jira. We are now monitoring for this recovery and will update shortly with further confirmation.

3. monitoring Jun 07, 2026, 12:13 AM UTC

   The issues relating to viewing and creating work items in Jira should now be fully resolved.

Read the full incident report →

Started Jun 05, 2026, 07:41 PM UTC· resolved Jun 10, 2026, 11:15 AM UTC

1. monitoring Jun 05, 2026, 07:41 PM UTC

   Illumia is excited to announce the release of Cloud POS Windows Kiosk 5.1.34. Clients may perform a binary sync at any time to receive the latest features and fixes on register and kiosk devices. As a reminder, sending a binary sync will reboot the POS device. Please be sure to read the Cloud POS Windows Kiosk 5.1.34 Release Notes to learn more. If you have any questions, please open a case via Illumia Connect or call Illumia Support at 888-381-8054, Option 3.

Read the full incident report →

Started Jun 05, 2026, 02:00 AM UTC· resolved Jun 10, 2026, 10:48 AM UTC

1. monitoring Jun 05, 2026, 02:00 AM UTC

   We're pleased to announce that Quickcharge will be deploying a fix on the evening of June 4th, 2026. Please check your Back Office system for an in-app message to determine if your site is included in this deployment wave. For additional questions, feel free to contact our Support Team 844-766-4435 Thank you for being a valued Quickcharge customer, The Quickcharge Team

2. monitoring Jun 05, 2026, 06:00 AM UTC

   The scheduled maintenance has been completed and the impacted systems are operating normally.

Read the full incident report →

Started Jun 03, 2026, 12:58 AM UTC· resolved Jun 10, 2026, 06:27 AM UTC

1. monitoring Jun 03, 2026, 12:58 AM UTC

   We're investigating a new incident. Current impact to end users: Some users may be experiencing trouble loading or connecting to Slack. We're on the case. We'll provide an update within 30 minutes including further details on current actions being taken.

2. monitoring Jun 03, 2026, 01:38 AM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: we're investigating an issue where some Slack users are experiencing thread loading, client booting, and message delivery failures. We've identified several potential contributing factors and are working to confirm the root cause. Further updates will be shared as the investigation continues. We'll provide another update in 30 minutes until the impact is resolved for all users.

3. monitoring Jun 03, 2026, 01:47 AM UTC

   This issue is now resolved for all users. Current status and recent actions taken: we've resolved the issue where some Slack users may have experienced message send failures and thread loading issues. We identified and addressed the root cause, and services have been fully restored. We apologize for any disruptions to your day.

4. monitoring Jun 03, 2026, 01:48 AM UTC

   Resolved.

Read the full incident report →

Started Jun 02, 2026, 04:16 PM UTC· resolved Jun 09, 2026, 11:37 PM UTC

1. monitoring Jun 02, 2026, 04:16 PM UTC

   Current status: The Slack engineering team investigated connectivity issues that affected some users between approximately 13:30 and 14:00 UTC on June 2, 2026. The issue has been resolved and no further impact has been reported. Scope: Some users, primarily in Europe, may have experienced difficulty loading or sending Slack messages during this window We apologize for any inconvenience this may have caused.

2. monitoring Jun 02, 2026, 04:16 PM UTC

   Resolved.

Read the full incident report →

Started Jun 02, 2026, 03:32 PM UTC· resolved Jun 10, 2026, 05:10 AM UTC

1. monitoring Jun 02, 2026, 03:32 PM UTC

   We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an update here within the next hour, or sooner if new information becomes available.

2. monitoring Jun 02, 2026, 04:51 PM UTC

   On June 6, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours.

Read the full incident report →

Started Jun 01, 2026, 08:06 AM UTC· resolved Jun 09, 2026, 06:20 PM UTC

1. monitoring Jun 01, 2026, 08:06 AM UTC

   We are investigating cases of partial-outage for Jira-software in the EU Region. We will provide more details within the next hour.

2. monitoring Jun 01, 2026, 08:06 AM UTC

   We have identified an issue causing degraded performance for Jira Software, Jira Work Management, and Jira Service Management in the EU region. affected users may experience 5XX errors when accessing issues, boards, and navigation. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

3. monitoring Jun 01, 2026, 09:08 AM UTC

   We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring the stability.

4. monitoring Jun 01, 2026, 01:23 PM UTC

   This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence. If you continue to experience issues, please contact Atlassian Support. We apologise for the disruption and thank you for your patience.

Read the full incident report →

Started Jun 01, 2026, 02:08 AM UTC· resolved Jun 09, 2026, 05:28 AM UTC

1. monitoring Jun 01, 2026, 02:08 AM UTC

   We are currently investigating a partial degradation impacting usergroups. We’ll provide an update as soon as we have more information to share and are sorry for any inconvenience this issue is causing.

2. monitoring Jun 01, 2026, 02:38 AM UTC

   We continue to investigate the issue and have identified a recent deployment as a likely trigger. Users may experience issues with user groups, including failed @mentions or groups appearing unavailable. We are actively working on restoring functionality and will provide another update as soon as possible.

3. monitoring Jun 01, 2026, 03:05 AM UTC

   Our investigation has determined that the issue is isolated to a single customer environment and is not impacting the broader service. As a result, this incident will be removed from the status page and we will continue to work directly with the affected customer to address their issue.

4. monitoring Jun 01, 2026, 03:06 AM UTC

   Resolved.

Read the full incident report →

Started May 29, 2026, 02:30 PM UTC· resolved Jun 08, 2026, 06:15 PM UTC

1. monitoring May 29, 2026, 02:30 PM UTC

   Customers have experienced elevated latency occurred in US East region from 6:30 AM to 8:58 AM Pacific time. Our engineers have investigated and resolved the issue. All impacted services are operating normally.

2. monitoring May 29, 2026, 02:31 PM UTC

   Incident closed.

Read the full incident report →

Started May 29, 2026, 02:25 AM UTC· resolved Jun 08, 2026, 02:10 AM UTC

1. monitoring May 29, 2026, 02:25 AM UTC

   We are pleased to announce that information about CBORD products will soon be visible here. For now, please continue to visit the CBORD Hub for the most up to date information about thse products.

Read the full incident report →

Started May 27, 2026, 11:02 PM UTC· resolved Jun 08, 2026, 02:10 AM UTC

1. monitoring May 27, 2026, 11:02 PM UTC

   The Slack Engineering team is currently investigating severe latency impacting all Slack services. We'll provide an update as soon as we have more information to share and apologize for any inconvenience this is causing.

Read the full incident report →

Started May 27, 2026, 11:00 PM UTC· resolved Jun 06, 2026, 11:42 PM UTC

1. monitoring May 27, 2026, 11:00 PM UTC

   We're investigating a new incident. Current impact to end users: We’re aware of an issue affecting workflows, message edits, channel renames, apps, and channel creations. We'll provide an update within 30 minutes including further details on current actions being taken.

2. monitoring May 27, 2026, 11:31 PM UTC

   We continue to investigate the issue, and are‌ implementing fixes to restore services. We're starting to see some improvements from the fixes implemented so far. We’ll provide another update as soon as we have more information, and again we are sorry for the inconvenience this is causing.

3. monitoring May 28, 2026, 01:03 AM UTC

   Teams continue to implement configuration adjustments and deployment fixes to resolve the issue. All features except for Workflows and Messaging should be recovered. Some lingering impact remains. Users may notice: Empty pills instead of @-mention Delayed reacji Mismatch in Channel member count and channel membership Slow loading of messages, user avatars, and unfurls We are working with urgency to improve platform stability and reduce impact. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

4. monitoring May 28, 2026, 01:41 AM UTC

   We are continuing to work on implementing fixes to fully resolve the issue. Messaging should now be recovered. Users may continue to experience issues with workflow steps completing. Empty pills instead of @-mention; delayed reacji; mismatch in Channel member count and channel membership; and slow loading of messages, user avatars, and unfurls should now all be working properly. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

5. monitoring May 28, 2026, 02:17 AM UTC

   Messaging latency has now cleared. Newly triggered workflows should start and complete as normal. Workflows that executed during the impact period ending at approximately 7pm PDT may not have completed. Customers may notice delayed workflow execution for jobs that triggered during the disruption period. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

6. monitoring May 28, 2026, 02:46 AM UTC

   Workflow builder jobs that were triggered during the disruption period have been replayed and will complete over the next several hours. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

7. monitoring May 28, 2026, 03:22 AM UTC

   Cleanup and recovery efforts continue. Workflow builder job backlogs are being drained. Event subscriptions have been re-enabled. No further impact is expected. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

8. monitoring May 28, 2026, 03:55 AM UTC

   We’re glad to inform you that the Workflow Builder job backlogs were cleared and workflow execution has returned to normal. We continue progressing through the final stages of recovery activities across affected service areas as overall platform stability improves. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

9. monitoring May 28, 2026, 04:30 AM UTC

   Recovery activities continue, and restoration efforts are progressing well. Platform stability is improving, and no further customer impact is expected. We’ll provide an update in the next 60 minutes or sooner, if additional information becomes available.

10. monitoring May 28, 2026, 05:13 AM UTC

    Slack services continue to progress through the final stages of ‌recovery activities to restore functionality across all services. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

11. monitoring May 28, 2026, 05:47 AM UTC

    Slack services have largely returned to normal operational levels. Messaging, Workflows, Apps, Integrations, APIs, and Connections have all been restored. We'll continue with the final restoration activities and we'll provide updates as significant developments occur.

12. monitoring May 28, 2026, 10:04 AM UTC

    We're investigating a new impact to Slack. Current impact to end users: Slack users are experiencing issues with managing channels, statuses aren't clearing or updating correctly, and edits on Canvas aren't being saved. We'll provide an update within 30 minutes including further details on current actions being taken.

13. monitoring May 28, 2026, 10:45 AM UTC

    We continue to investigate the issue and are working with urgency to improve stability and reduce impact. We’ll provide another in 30 minutes or sooner, including further details on current actions being taken. We're sorry for the inconvenience this is causing.

14. monitoring May 28, 2026, 11:17 AM UTC

    Users continue to experience issues with their ability to manage channels, Canvas edits not saving, and user statuses not clearing or updating correctly. Investigations are underway. The issues aren't reproducible and we're working to get the IDs to investigate further. We're working with urgency to improve platform stability and reduce impact. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

15. monitoring May 28, 2026, 11:46 AM UTC

    We continue to investigate the issue, and are‌ gathering the resources necessary to restore services. We’ll provide another update in 30 minutes or as soon as we have more information, and again we're sorry for the inconvenience this is causing.

16. monitoring May 28, 2026, 12:01 PM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: Remediation efforts are underway via configuration adjustments and deployment. We're still working to resolve the issues with Canvas. We'll be back with another update once we have news to share.

17. monitoring May 28, 2026, 12:25 PM UTC

    Recovery activities continue, and restoration efforts are progressing well. Slack users should now be able to edit Canvases as the errors have dropped. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

18. monitoring May 28, 2026, 12:55 PM UTC

    Remediation efforts via configuration adjustments and deployment are in progress. Users may still run into issues updating their status and managing channels. We’ll provide another update in 30 minutes or as soon as we have more information, and again we are sorry for the inconvenience this is causing.

19. monitoring May 28, 2026, 01:35 PM UTC

    Remediation efforts via configuration adjustments and deployment will take several hours to complete to fully resolve channel management and status issues. Slack users may continue to experience intermittent impact. We'll be back with another update in 30 minutes when we have news to share.

20. monitoring May 28, 2026, 02:09 PM UTC

    Slack users continue to experience permissions-related issues such as: unable to manage channels, add Canvas to tabs, update statuses, convert public to private channels while we work on a complete restoration. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

21. monitoring May 28, 2026, 03:22 PM UTC

    This issue is now resolved for all users. Current status and recent actions taken: We deployed a series of configuration adjustments and infrastructure fixes to restore services. Messaging, Workflows, Apps, and Connections were progressively restored over the last several hours. Some users continued to experience permissions-related issues, including inability to manage channels and Canvas edits not saving, as a result of residual stale cache data. Cache deployment activities completed at 14:13 UTC on May 28, 2026, fully resolving the issue. Scope: This issue affected Slack users globally. Previous impact to end users: Slack users experienced difficulties accessing Slack features, including Messaging, Workflows, Apps, Integrations, APIs, Canvas, and Connections, beginning at 22:21 UTC on May 27, 2026. Following an infrastructure change, a cascading scheduling failure caused widespread service impact across all regions and clients. Slack services largely returned to normal operational levels at 05:45 UTC on May 27, with residual impact that remained during the deployment. A brief issue with Canvas surfaced at 10:00 UTC on May 28‌ that lasted until approximately 12:30 UTC. Required resolution steps: No steps required. We apologize for any disruptions to your day. We'll undertake a full investigation of the incident, establishing the technical trigger, the mechanism of failure, and preventative measures to avoid further disruptions.

22. monitoring May 28, 2026, 03:23 PM UTC

    Resolved.

Read the full incident report →

Started May 25, 2026, 09:11 AM UTC· resolved Jun 02, 2026, 05:34 PM UTC

1. monitoring May 25, 2026, 09:11 AM UTC

   Illumia Engineers are responding to alerts which indicate an issue with scheduled reporting functions. On demand reporting is unaffected.

2. monitoring May 25, 2026, 04:11 PM UTC

   This incident has been resolved and all systems are now operating normally.

Read the full incident report →

Started May 22, 2026, 05:30 PM UTC· resolved Jun 01, 2026, 01:23 PM UTC

1. monitoring May 22, 2026, 05:30 PM UTC

   Starting around 10:17AM on May 22 2026, our engineers began investigating an issue affecting SenderAuth and Whitelabel domains. A subset of customers may be experiencing errors when calling the /v3/domains endpoint. We will provide another update as soon as more information becomes available.

2. monitoring May 22, 2026, 05:51 PM UTC

   Our engineers have implemented a fix and are monitoring system performance. We will provide another update in an hour or as soon as more information becomes available.

3. monitoring May 22, 2026, 06:50 PM UTC

   Our engineers have monitored the fix and confirmed the issue with SenderAuth and Whitelabel domains has been resolved. All services are now operating normally at this time.

Read the full incident report →

Started May 20, 2026, 09:45 PM UTC· resolved Jun 01, 2026, 10:04 AM UTC

1. monitoring May 20, 2026, 09:45 PM UTC

   Description: Newly issued InCommon SSL certificates may not work as expected. This could cause a service disruption with devices such as PR5000 or Transact Verify. The team is actively investigating and triaging the problem. Solution: If your organization does not have an immediate need for a new InCommon certificate, please consider waiting to renew until a long-term solution is identified by the team. If there is an immediate need for an updated certificate, please contact Illumia support to discuss options. Regards, Illumia Support

Read the full incident report →

Started May 20, 2026, 09:17 AM UTC· resolved Jun 01, 2026, 10:04 AM UTC

1. monitoring May 20, 2026, 09:17 AM UTC

   Users are reporting an issue with Forge custom fields not getting created on Jira work items page, after deploying an application. Our teams are investigating the issue and more updates will be shared within next 2 hour or sooner.

2. monitoring May 20, 2026, 11:20 AM UTC

   Our teams are actively working on the identifying the root cause and we will provide an update within 3 hours, or sooner if there is any significant progress. Thank you for your patience.

3. monitoring May 20, 2026, 12:06 PM UTC

   Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. The impact is limited to new deployments with Forge custom fields on Jira work items, however existing deployments with custom fields are running without any issues.

4. monitoring May 20, 2026, 02:14 PM UTC

   The root cause has been identified and a fix has been applied. Full service restoration has been completed.

Read the full incident report →

Started May 19, 2026, 08:51 PM UTC· resolved May 29, 2026, 04:20 PM UTC

1. monitoring May 19, 2026, 08:51 PM UTC

   We've identified the trigger, causing slow file and emoji uploads in Slack, and have deployed a fix. At this time, we are monitoring the environment to confirm full resolution. - Current status and actions being taken: We've identified a frontend error as the cause of the issue and have deployed a fix. We're actively monitoring our health metrics to confirm the fix has resolved the issue for all users. - Estimated time to resolution: No ETA at this time. - Scope: Users globally may be experiencing this issue. - Current impact to end users: Some users may experience slowness when uploading files and emojis in Slack. Attaching or sending files may be taking longer than expected — or failing to complete in a timely manner. - Known workarounds: No workarounds at this time. We'll provide another update as soon as we have more information to share.

2. monitoring May 19, 2026, 10:27 PM UTC

   This issue is now resolved for all users. Current status and recent actions taken: The fix has successfully deployed, and our health metrics have stabilized. The issue is now fully resolved for all affected users. Scope: This wasn't affecting any specific region, but a percentage of users may have been affected globally. Previous impact to end users: Some users may have experienced slowness when uploading files and emojis in Slack. Attaching or sending files may have taken longer than expected — or failed to complete in a timely manner. Required resolution steps: No additional steps are required. We apologize for any disruptions to your day.

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

   Resolved.

Read the full incident report →

Started May 18, 2026, 02:53 PM UTC· resolved May 28, 2026, 12:54 PM UTC

1. monitoring May 18, 2026, 02:53 PM UTC

   Some Slack users experienced issues where Huddle AI summaries ‌weren't being generated. Users also appeared to be showing as in a huddle after it had ended. We've fixed both issues. Missing summaries were restored, and the system responsible for showing huddle statuses has been refreshed. If you still notice any users appearing stuck in a huddle, please contact Slack Support. We apologize for the inconvenience and any impact this may have had.

2. monitoring May 18, 2026, 02:53 PM UTC

   Resolved.

Read the full incident report →

Started May 14, 2026, 02:37 PM UTC· resolved May 28, 2026, 11:18 AM UTC

1. monitoring May 14, 2026, 02:37 PM UTC

   We're investigating a new incident. Current impact to end users: We’re aware of an issue affecting file uploads, message edits, channel renames, and channel creations. We'll provide an update within 30 minutes including further details on current actions being taken.

2. monitoring May 14, 2026, 02:50 PM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: We're investigating reports of slow loading times, errors when updating workflows, editing messages, creating or renaming channels, reactions, and issues with file uploads and third-party integrations. Some users may encounter failures when posting images or using add-ins. We'll be back with another update once we have news to share.

3. monitoring May 14, 2026, 03:19 PM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: We've identified a potential cause related to an internal infrastructure component responsible for processing background tasks. Several nodes running this component were experiencing resource exhaustion and CrashLoopBackOff errors, causing connectivity failures to our message queue brokers. A revert of a recent configuration change is currently rolling out and we're seeing signs of improvement — 503 errors are trending down and some impacted pods are stabilizing. We'll continue monitoring the progress. We'll be back with another update once we have news to share. Thank you for your patience.

4. monitoring May 14, 2026, 03:34 PM UTC

   The issue affecting multiple features, including file uploads, message edits, and channel management, has been resolved. A fix has been fully deployed, and all systems are functioning normally. If you are still experiencing any trouble, please perform a hard reload of Slack by pressing Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Mobile users should fully close and relaunch the app. We sincerely apologize for the disruption to your day and appreciate your patience while we worked to sort this out.

5. monitoring May 14, 2026, 03:35 PM UTC

   Resolved.

Read the full incident report →

Started May 14, 2026, 05:03 AM UTC· resolved May 28, 2026, 04:37 AM UTC

1. monitoring May 14, 2026, 05:03 AM UTC

   We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

2. monitoring May 14, 2026, 05:11 AM UTC

   Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

3. monitoring May 14, 2026, 05:24 AM UTC

   It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available.

4. monitoring May 14, 2026, 05:34 AM UTC

   Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update within an hour as we are able to progress mitigating this issue.

5. monitoring May 14, 2026, 05:43 AM UTC

   Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

6. monitoring May 14, 2026, 06:40 AM UTC

   We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

7. monitoring May 14, 2026, 06:41 AM UTC

   We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

8. monitoring May 14, 2026, 06:48 AM UTC

   All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Read the full incident report →

Started May 13, 2026, 04:00 AM UTC· resolved May 18, 2026, 03:41 PM UTC

1. monitoring May 13, 2026, 04:00 AM UTC

   The Campus ID Software Services Engineering team will deploy a TSE Software patch to v4.1.9 in hosted environments. The upgrade will be completed within a single day, with each institution experiencing an estimated six-hour outage during the process. Please review the TSE Upgrade schedule below: ActivityUpgrade WindowImpact TSE Software Upgrade May 13, 2026 (12:00 AM ET - 06:00AM ET) May 12, 2026 (11:00 PM CT - 05:00 AM CT) May 12, 2026 (10:00PM MT - 04:00 AM MT) May 12, 2026 (09:00 PM PT - 03:00 AM PT) ~6 HRS - ALL TSE Services will be offline Individual cases will be created for each institution’s upgrade, where all related communications and release documentation will be provided. Please review the attached materials in advance and direct any questions through the respective case. Institutions with a Test Hosted Environment will be upgraded to TSE 4.1.9 on May 6, 2026, from 07:00 AM to 01:00 PM MST (10:00 AM to 04:00 PM ET). This upgrade will occur one week prior to the scheduled start of Production patch deployments. Please note that the TSE software patch will be applied to all production (LIVE) hosted institutions during their designated maintenance windows. Expected impact: The TSE system will be unavailable during the upgrade window specified in each case. Illumia is committed to keeping clients informed of all scheduled maintenance affecting production systems. If you have any questions or experience issues after the maintenance window has concluded, please open a case through Illumia Connect or contact Support at 1-888-381-8054, Option 2, then 1

2. monitoring May 13, 2026, 10:00 AM UTC

   The scheduled maintenance has been completed and the impacted systems are operating normally.

Read the full incident report →

Started May 13, 2026, 01:37 AM UTC· resolved May 18, 2026, 02:52 PM UTC

1. monitoring May 13, 2026, 01:37 AM UTC

   At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

2. monitoring May 13, 2026, 02:41 AM UTC

   Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

3. monitoring May 13, 2026, 05:38 AM UTC

   The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

4. monitoring May 13, 2026, 06:38 AM UTC

   Our team has been able to confirm that new automation events should now be processed correctly. We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

5. monitoring May 13, 2026, 07:42 AM UTC

   While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident. We will provide an update on the progress within one hour.

6. monitoring May 13, 2026, 08:42 AM UTC

   Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

7. monitoring May 13, 2026, 09:59 AM UTC

   We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Read the full incident report →

Started May 12, 2026, 04:31 PM UTC· resolved May 14, 2026, 08:00 AM UTC

1. monitoring May 12, 2026, 04:31 PM UTC

   Starting around 9 AM PDT on Tuesday, 5/12/2026, our engineers started investigating an issue with teammates, where invitees could not join their organizations and instead they were led to creating standalone Twilio Unified accounts. New teammates, therefore, are unable to join their organizations at the time. This issue does not impact mail send. We will provide another update in an hour or as soon as more information becomes available.

2. monitoring May 12, 2026, 04:59 PM UTC

   Our engineers have identified the issue and are working toward a fix. We will provide another update in one hour or as soon as more information becomes available.

3. monitoring May 12, 2026, 05:13 PM UTC

   Our engineers have implemented a fix and are monitoring system performance. Teammates that were impacted by the issue need to request a new invite link and delete cache and cookies on their browsers before attempting to join again. We will provide another update in one hour or as soon as more information becomes available.

4. monitoring May 12, 2026, 06:20 PM UTC

   Our engineers have monitored the fix and confirmed the issue with teammate account creation has been resolved. All services are now operating normally at this time.

Read the full incident report →

Started May 11, 2026, 10:30 PM UTC· resolved May 14, 2026, 08:00 AM UTC

1. monitoring May 11, 2026, 10:30 PM UTC

2. monitoring May 11, 2026, 11:14 PM UTC

   The issue is tentatively resolved and we are monitoring the system to ensure there are no further issues.

3. monitoring May 11, 2026, 11:19 PM UTC

   This incident has been resolved and all systems are now operating normally. Clients who send files to be imported using the autorun facility between 4:10 PM EDT and 7:10 EDT may need to resend those files.

Read the full incident report →