Transact Outage History

Started May 11, 2026, 02:09 PM UTC· resolved May 14, 2026, 08:00 AM UTC

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

   We’re investigating this issue: Current status and actions being taken: We’re seeing renewed, elevated error rates and latency affecting customers using Enterprise Key Management (EKM). Affected customers may experience issues sending messages and loading some channels. Our team is actively investigating this issue. Estimated time to resolution: No ETA at this time. Scope: This isn't affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally. Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading some channels. Known workarounds: No known workarounds at this time. We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

Read the full incident report →

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

1. monitoring May 11, 2026, 08:00 AM UTC

   Maintenance tasks: Transact will perform scheduled maintenance on the Cloud POS environment. Expected impact: There is no expected downtime for this maintenance, however, any scheduled exports or reports which would be sent by email during this time will be queued for processing when maintenance is completed. If you have any questions or experience any issues after the maintenance window has passed, please open a case via Illumia Connect or call Illumia Support at 888-381-8054, Option 3.

2. monitoring May 11, 2026, 12:00 PM UTC

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

Read the full incident report →

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

1. monitoring May 08, 2026, 12:13 PM UTC

   Users who are undergoing scheduled Grid Migrations are experiencing extended downtime. Downtime is expected during a Grid Migration however it's taking longer than usual. During the downtime users are unable to access Slack until the migration completes. We've identified an issue with Job Queues, which may be the cause and are investigating this further. The next update will be provided once additional information becomes available.

2. monitoring May 08, 2026, 05:44 PM UTC

   This issue is now resolved. Current status and actions being taken: We identified database write throttling as the cause of the stalled grid migrations. We applied a drop rule for jobs that were stuck in a retry loop, which has restored normal migration processing. Scope: A small number of enterprise users undergoing grid migrations experienced extended delays in accessing Slack. Current impact to end users: Affected users may have experienced an inability to access Slack during their migration window. Known workarounds: No workarounds needed at this time. We apologize for how this incident affected you and your business.

3. monitoring May 08, 2026, 05:45 PM UTC

   Resolved.

Read the full incident report →

Started May 08, 2026, 02:04 AM UTC· resolved May 13, 2026, 09:54 AM UTC

1. monitoring May 08, 2026, 02:04 AM UTC

   Customers may have experienced mail delay between 5pm and 5:15pm PDT.Our engineers have been alerted and are investigating. We will provide another update in 30 minutes or as soon as we have more information.

2. monitoring May 08, 2026, 02:53 AM UTC

   Customers may continue to experience mail delays. Our engineers are actively investigating and working to identify the cause. We will provide another update in 30 minutes or as soon as we have more information.

3. monitoring May 08, 2026, 03:38 AM UTC

   Our engineers have identified the issue and are working toward a fix. New Mail Send requests are not affected and are processing normally. We are still actively working on delivering previously delayed mails. We will provide another update in next 2hr or as soon as more information becomes available.

4. monitoring May 08, 2026, 07:04 AM UTC

   Our engineering team has identified the root cause of the issue and is actively working on a resolution. Please note that new Mail Send requests are processing as expected and are not impacted. We will share another update within the next two hours, or sooner if additional information becomes available.

5. monitoring May 08, 2026, 08:09 AM UTC

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

Read the full incident report →

Started May 08, 2026, 01:31 AM UTC· resolved May 14, 2026, 08:00 AM UTC

1. monitoring May 08, 2026, 01:31 AM UTC

   We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

2. monitoring May 08, 2026, 02:15 AM UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

3. monitoring May 08, 2026, 03:00 AM UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

4. monitoring May 08, 2026, 03:00 AM UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

5. monitoring May 08, 2026, 04:10 AM UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

6. monitoring May 08, 2026, 04:10 AM UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

7. monitoring May 08, 2026, 04:10 AM UTC

   We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

8. monitoring May 08, 2026, 05:53 AM UTC

   The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

9. monitoring May 08, 2026, 08:03 AM UTC

   We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

10. monitoring May 08, 2026, 11:12 AM UTC

    Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We apologise for the disruption and thank you for your patience.

11. monitoring May 08, 2026, 07:45 PM UTC

    On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started May 06, 2026, 09:35 AM UTC· resolved May 08, 2026, 11:14 AM UTC

1. monitoring May 06, 2026, 09:35 AM UTC

   We are investigating reports of lookup objects in Automation for Jira Service Management are not functioning as expected. Our engineering teams are actively investigating and working to resolve the issue. We will provide further updates in next 1 hour.

2. monitoring May 06, 2026, 10:18 AM UTC

   A fix has been implemented to address the failures observed in the lookup objects within JSM Automation. We are actively monitoring the situation to ensure stability. We will share the final update within next 1 hour.

3. monitoring May 06, 2026, 11:17 AM UTC

   The issue causing failures in the lookup objects within JSM Automation has been resolved. A fix was implemented to address the problem and the service is now operating normally for all affected customers.

Read the full incident report →

Started May 06, 2026, 03:18 AM UTC· resolved May 08, 2026, 08:05 AM UTC

1. monitoring May 06, 2026, 03:18 AM UTC

   We are investigating reports of users unable to log time while on business board. Our engineering teams are actively investigating and working to resolve the issue. We will provide more updates in next 1 hour.

2. monitoring May 06, 2026, 04:16 AM UTC

   Our engineering teams have identified the 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.

3. monitoring May 06, 2026, 06:39 AM UTC

   The issue causing Jira users inability to log time on business board has been resolved. A fix was deployed to address the problem and the service is operating normally for all affected customers.

Read the full incident report →

Started May 04, 2026, 10:00 AM UTC· resolved May 08, 2026, 07:58 AM UTC

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

   Some users are experiencing issues with workflows. Triggered workflows may fail to complete, with the first step not executing. We'll provide another update as soon as possible.

2. monitoring May 04, 2026, 11:43 AM UTC

   The investigation identified elevated latency in EU backend services as the cause of workflows not completing. Approximately 25% of workflow trigger attempts are affected, primarily impacting EU customers. Pod restarts have stopped, and error rates are improving. A fix is being prepared and will be deployed shortly. We'll provide another update as soon as possible.

3. monitoring May 04, 2026, 01:08 PM UTC

   A fix has been deployed to address the elevated latency in EU backend services. The team is monitoring the environment to ensure service stability and full recovery. We'll provide another update as soon as possible.

4. monitoring May 04, 2026, 05:37 PM UTC

   This issue is now resolved for all users. Current status and recent actions taken: A fix has been deployed that resolved the underlying cause of this issue. Our health metrics have returned to normal levels and workflows are running as expected. Scope: Users in the EU region — primarily teams based in Central Europe — experienced elevated workflow failure rates. Previous impact to end users: Users may have experienced workflows failing to run, with the first step remaining stuck in an initialized state. Some users in the EU region may also have experienced general slowness when using Slack. Required resolution steps: No steps are required. Workflows should be running normally. If you continue to experience any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We apologize for any disruptions this may have caused to your day.

5. monitoring May 04, 2026, 05:38 PM UTC

   Resolved.

Read the full incident report →

Started May 02, 2026, 12:55 AM UTC· resolved May 08, 2026, 04:10 AM UTC

1. monitoring May 02, 2026, 12:55 AM UTC

   We are investigating an incident affecting Jira Software (viewBoard, viewIssue, createIssue). Our team is working to identify the cause and restore service to normal levels. We will provide the next update within 60 minutes.

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

   We are actively investigating reports of a service disruption affecting the issue viewing experience in Jira. This is also impacting the accessibility of support tickets. We will share updates here as more information becomes available.

3. monitoring May 02, 2026, 02:00 AM UTC

   We are actively investigating reports of a service disruption affecting the Work Item viewing experience in Jira. This is also impacting the accessibility of support tickets. We will share updates here as more information becomes available.

4. monitoring May 02, 2026, 02:48 AM UTC

   The Jira Work Item View experience has been restored to normal service. Our teams are continuing to investigate the root cause affecting this issue. We will provide more details once we identify the root cause

Read the full incident report →

Started May 01, 2026, 06:30 PM UTC· resolved May 08, 2026, 04:10 AM UTC

1. monitoring May 01, 2026, 06:30 PM UTC

   Maintenance tasks: The Transact systems team has advised that they will be doing an emergency maintenance update to our Production SFTP server for TS SaaS today. Expected impact: Brief downtime is expected during the maintenance window. Pre-maintenance files that are pending will process automatically once maintenance completes. Connection attempts during this period may time out. Illumia wishes to inform our clients of all scheduled maintenance to production systems. If you have any questions or experience any issues after the maintenance window has passed, please open a case via Illumia Connect or 1-888-381-8054, Option 4 then follow the appropriate prompts for Illumia SaaS Client Support.

2. monitoring May 01, 2026, 07:00 PM UTC

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

Read the full incident report →

Started Apr 28, 2026, 05:14 PM UTC· resolved May 08, 2026, 04:10 AM UTC

1. monitoring Apr 28, 2026, 05:14 PM UTC

   We are currently experiencing issues with connectivity between certain modules within Illumia Payments and a subset of client ERP systems. The impact is specifically to a subset of online lookups performed in Cashiering or Customer Research Center (CRC) as well as to a subset of Online Posting connections. Interfaces that use Transact Exchange are not impacted.

2. monitoring Apr 28, 2026, 06:24 PM UTC

   Illumia engineers have found that the connectivity issue is affecting a small set of clients. Support will be reaching out to work with those clients individually.

3. monitoring Apr 28, 2026, 09:14 PM UTC

   Engineers have determined that a phased restart of services should re-enable online lookups for this subset of clients and we are starting that process now. There should be no impact to existing services. Online Postings will be fixed with service restarts over night. Clients who are experiencing connection errors with Online Postings may need to retry postings from the Online Service Manager after the services have been restarted.

4. monitoring Apr 29, 2026, 02:36 PM UTC

   This incident has been resolved and all systems are now operating normally. Impacted clients may need to reattempt yesterday’s failed transactions within Online Service Manager.

Read the full incident report →

Started Apr 28, 2026, 05:00 AM UTC· resolved May 08, 2026, 03:01 AM UTC

1. monitoring Apr 28, 2026, 05:00 AM UTC

   Illumia is excited to announce a new update to the Illumia Insights environment. Please be sure to read the Illumia Insights Release Notes available here to learn more. Expected impact: Users may experience a delay in data refresh while the update is in progress. If you have any questions or experience any issues after the maintenance window has passed, please open a case via Illumia Connect or call Illumia Support at 888-381-8054, Option 3.

2. monitoring Apr 28, 2026, 09:00 AM UTC

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

Read the full incident report →

Started Apr 24, 2026, 04:07 PM UTC· resolved May 08, 2026, 01:33 AM UTC

1. monitoring Apr 24, 2026, 04:07 PM UTC

   A subset of integrations between Illumia Payments and client ERP systems are currently experiencing latency or unavailability due to a cloud provider issue. Illumia Engineers are working to remediation the issue.

2. monitoring Apr 24, 2026, 06:26 PM UTC

   We are beginning to see signs of recovery for the impacted ERP integrations. Not all have recovered yet and we are continuing to monitor the situation.

3. monitoring Apr 24, 2026, 07:26 PM UTC

   The issue with the service(s) ERP Integration is tentatively resolved and Illumia engineers are monitoring the systems to confirm there are no further issues.

4. monitoring Apr 24, 2026, 10:20 PM UTC

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

Read the full incident report →

Started Apr 24, 2026, 04:01 PM UTC· resolved May 08, 2026, 01:22 AM UTC

1. monitoring Apr 24, 2026, 04:01 PM UTC

   Cloud POS is currently experiencing delays with orders moving through the queuing process. Illumia engineers are currently working to resolve the issue.

2. monitoring Apr 24, 2026, 04:51 PM UTC

   The delay in orders moving through the queuing process is being caused by a cloud provider issue. The provider is actively working towards a resolution.

3. monitoring Apr 24, 2026, 05:26 PM UTC

   Our cloud provider continues to troubleshoot the issue that is causing delays in certain order routing operations. We would like to provide some additional clarity on the specific impacts: Orders being sent from Illumia Mobile Ordering to Cloud POS are not being delayed. Orders being sent from Cloud POS registers or kiosks to the kitchen using Local Routing will reach KDS units and kitchen printers promptly, but will take additional time to be recorded on the backend system for reporting purposes. Orders being send from Cloud POS registers or kiosks to the kitchen using Cloud Routing will encounter delays.

4. monitoring Apr 24, 2026, 06:59 PM UTC

   The issue with Cloud POS Order Routing is tentatively resolved and Illumia engineers are monitoring the systems to confirm there are no further issues.

5. monitoring Apr 24, 2026, 10:20 PM UTC

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

Read the full incident report →

Started Apr 23, 2026, 07:27 AM UTC· resolved May 06, 2026, 09:22 PM UTC

1. monitoring Apr 23, 2026, 07:27 AM UTC

   Some users are having trouble loading Threads in Slack, this is affecting Windows and Chrome users. Users may receive an error asking them to ‘Try Again’. We apologize for the inconvenience and will report back as more information becomes available.

2. monitoring Apr 23, 2026, 08:05 AM UTC

   We’re still investigating these issues with Threads not loading. No additional information to share just yet, but we’ll keep you posted as soon as we have an update.

3. monitoring Apr 23, 2026, 09:50 AM UTC

   Further investigation confirms that the issue impacting Thread loading has been self- resolved, and our team will continue to investigate to ensure that this doesn’t reoccur. We apologize for the trouble today and thank you for your patience.

4. monitoring Apr 23, 2026, 09:51 AM UTC

   Resolved.

Read the full incident report →

Started Apr 22, 2026, 01:38 PM UTC· resolved May 06, 2026, 06:38 AM UTC

1. monitoring Apr 22, 2026, 01:38 PM UTC

   Illumia engineers have identified an issue with SAML authentication for some clients which may be preventing login to eAccounts web and mobile. We are currently investigating.

2. monitoring Apr 22, 2026, 02:04 PM UTC

   We've updated our SAML 2 SSO configuration: the SAML 2 and Shibboleth SSO metadata has been replaced and our SAML signing (sign-in) certificate has been rotated. Action required: Please update your SAML 2 IdP SSO setup immediately to avoid login failures. The SAML metadata URL is unchanged for a given existing configuration. What to do (recommended): Refresh your IdP SAML2 application connected to eAccounts to ensure the latest metadata is being retrieved. If a static metadata XML file is being used in the SAML 2 IdP configuration, retrieve the metadata URL from the metadata URL link inside of SP Management Portal.

3. monitoring Apr 22, 2026, 06:32 PM UTC

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

Read the full incident report →

Started Apr 22, 2026, 01:02 AM UTC· resolved May 04, 2026, 05:58 PM UTC

1. monitoring Apr 22, 2026, 01:02 AM UTC

   ACI v2 is experiencing intermittent availability. Engineers are investigating the issue.

2. monitoring Apr 22, 2026, 01:56 AM UTC

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

3. monitoring Apr 22, 2026, 02:09 AM UTC

   This issue has been resolved and the system is operating normally.

Read the full incident report →

Started Apr 21, 2026, 01:46 PM UTC· resolved May 02, 2026, 02:51 AM UTC

1. monitoring Apr 21, 2026, 01:46 PM UTC

   We're aware of an issue affecting Slack. Some users who have set a custom status to expire at a specific time are finding that their status is not automatically clearing as expected. We are actively investigating and we'll provide an update as soon as we have more information available.

2. monitoring Apr 21, 2026, 03:47 PM UTC

   Resolved This issue is now resolved for all users. Current status and recent actions taken: Custom statuses set to expire at a specific time are now clearing as expected. The issue self-resolved when the next scheduled expiration job successfully processed the affected users. Scope: Some external users globally were affected. Users on desktop were impacted; the issue was not reproducible internally or across test workspaces. Previous impact to end users: Some users may have experienced custom statuses that did not automatically clear at their scheduled expiration time. Required resolution steps: No steps required. We apologize for any disruptions to your day.

3. monitoring Apr 21, 2026, 03:48 PM UTC

   Resolved.

Read the full incident report →

Started Apr 20, 2026, 04:12 PM UTC· resolved May 02, 2026, 12:51 AM UTC

1. monitoring Apr 20, 2026, 04:12 PM UTC

   Illumia Engineers are investigating an issue with the service(s) Cloud POS. Syncs are experiencing delays and failures.

2. monitoring Apr 20, 2026, 06:21 PM UTC

   Illumia Engineers continue to work on applying a mitigation to the impacted resources. Syncs may still be delayed.

3. monitoring Apr 20, 2026, 07:26 PM UTC

   Illumia Engineers have engaged vendor support for assistance in applying the mitigation. Syncs may still be delayed.

4. monitoring Apr 20, 2026, 07:58 PM UTC

   The issue with the service(s) Cloud POS is tentatively resolved and Illumia engineers are monitoring the systems to confirm there are no further issues.

5. monitoring Apr 20, 2026, 11:36 PM UTC

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

Read the full incident report →

Started Apr 20, 2026, 09:05 AM UTC· resolved Apr 29, 2026, 09:13 PM UTC

1. monitoring Apr 20, 2026, 09:05 AM UTC

   This issue is now resolved for all users. Current status and recent actions taken: We've completed rolling back the change to address the issue impacting core Slack functionality, including launching Slack, sending messages, loading threads, and other related actions. Scope: All Slack enterprise customers. Previous impact to end users: Users experienced issues with channel-related operations, including delays or failures when loading channels or retrieving channel membership lists. We apologize for any disruptions to your day.

2. monitoring Apr 20, 2026, 09:05 AM UTC

   Resolved.

Read the full incident report →

Started Apr 18, 2026, 08:07 PM UTC· resolved Apr 28, 2026, 06:24 PM UTC

1. monitoring Apr 18, 2026, 08:07 PM UTC

   Our engineers have investigated and resolved the issues with delayed delivery of emails for a subset of customers. From 12:05 pm PST to 12:45 pm PST customers may have seen a delay in the delivery of their emails. The issue has been resolved and all impacted services are operating normally.

2. monitoring Apr 18, 2026, 08:08 PM UTC

   Incident closed.

Read the full incident report →

Started Apr 16, 2026, 02:26 PM UTC· resolved Apr 28, 2026, 08:53 AM UTC

1. monitoring Apr 16, 2026, 02:26 PM UTC

   Illumia Engineers are investigating a possible issue with the service(s) Cloud POS. This appears to be limited to syncs being generated and delivered to client registers.

2. monitoring Apr 16, 2026, 02:58 PM UTC

   Illumia Engineers have determined that the service(s) Cloud POS is operating in a degraded state.

3. monitoring Apr 16, 2026, 04:52 PM UTC

   Illumia Engineers have engaged our Cloud Provider for additional support in applying a mitigation for this issue.

4. monitoring Apr 16, 2026, 07:03 PM UTC

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

Read the full incident report →

Started Apr 15, 2026, 04:00 PM UTC· resolved Apr 24, 2026, 10:21 PM UTC

1. monitoring Apr 15, 2026, 04:00 PM UTC

   Starting around 08:30 AM PST on April 15th, 2026, our engineers began investigating an issue with EU subusers that are unable to send emails. Customer may experience the error "User is not authorized to send mail based on their regional attribute." This is currently being investigated. This impacts mail send only for subusers located in EU. We will provide another update in an hour or as soon as more information becomes available.

2. monitoring Apr 15, 2026, 05:06 PM UTC

   We are continuing investigating this issue. We will provide more updates in 2 hours, or as soon as they become available.

3. monitoring Apr 15, 2026, 06:37 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.

4. monitoring Apr 15, 2026, 06:44 PM UTC

   Our engineers have monitored the fix and confirmed the issue with EU subusers unable to send emails has now been resolved. All services are now operating normally at this time.

Read the full incident report →

Started Apr 15, 2026, 02:44 PM UTC· resolved Apr 24, 2026, 06:10 PM UTC

1. monitoring Apr 15, 2026, 02:44 PM UTC

   Illumia Engineers are investigating an issue with the service(s) Quickcharge/US6. Back office and Mobile ordering are inaccessible at this time.

2. monitoring Apr 15, 2026, 03:02 PM UTC

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

Read the full incident report →

Started Apr 14, 2026, 03:46 PM UTC· resolved Apr 24, 2026, 03:56 PM UTC

1. monitoring Apr 14, 2026, 03:46 PM UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability.

2. monitoring Apr 14, 2026, 04:11 PM UTC

   On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →