Transact Outage History

Started Jun 29, 2026, 09:00 AM UTC· resolved Jul 12, 2026, 03:22 PM UTC

1. monitoring Jun 29, 2026, 09:00 AM UTC

   TSE PR5000 2.6.4 Release Update: A software release update for the TSE PR5000 is scheduled for Tuesday, June 30th, 2026. Release 2.6.4 is an over-the-air (OTA) update. Automatic updates will take place for eligible devices at the scheduled time as set by the Install Software Updates parameter in the TSE Management portal. The purpose of this release is to add additional TLS root certificates to enable operation with newer certificates issued from GoDaddy and InCommon in the near future. If you have any questions, please open a case via Illumia Connect or call Illumia Support at 888-381-8054, Option 1.

Read the full incident report →

Started Jun 26, 2026, 09:12 AM UTC· resolved Jul 11, 2026, 10:46 PM UTC

1. monitoring Jun 26, 2026, 09:12 AM UTC

   We're aware of an issue affecting users ability to reach our Slack Support team via the Chat functionality on the Slack Help page. Users will be unable to click on the ‘Chat’ option and will see a ‘Chat is temporarily unavailable. Please send us a message or check back later’ error message. We're working to resolve this issue and will provide an update in 30 minutes or sooner if additional information becomes available.

2. monitoring Jun 26, 2026, 09:41 AM UTC

   Additional Slack engineers have been engaged and are investigating this issue. As a workaround, if users require support, they can use the ‘Send us a Message’ functionality on the Slack Help Center page here: https://slack.com/intl/en-gb/help/requests/new . A member of the Slack team will then be in touch. We're working to resolve this issue and will provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jun 26, 2026, 10:09 AM UTC

   We've resolved the issue and users can now use the Chat feature on the Slack Help Center. We performed a configuration change, which brought the feature back online and have validated that it's functioning as expected. We apologize for how this incident may have affected you and your business.

4. monitoring Jun 26, 2026, 10:10 AM UTC

   Resolved.

Read the full incident report →

Started Jun 25, 2026, 10:00 PM UTC· resolved Jul 09, 2026, 05:51 PM UTC

1. monitoring Jun 25, 2026, 10:00 PM UTC

   We're pleased to announce that Quickcharge will be deploying a fix on the evening of June 25th, 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 26, 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 25, 2026, 11:52 AM UTC· resolved Jul 09, 2026, 12:05 PM UTC

1. monitoring Jun 25, 2026, 11:52 AM UTC

   Illumia engineers have identified issues signing into eAccounts on Android for the latest version of the app (2026.4.0). A root cause has been identified and a fix will be released in the coming hours. Affected users may work around the issue while awaiting the fix by long pressing the eAccounts icon on Android, pressing Info, selecting storage, clearing storage and signing in again.

2. monitoring Jun 25, 2026, 03:52 PM UTC

   A fixed version of the eAccounts app has been released to the Google Play store, version 2026.4.1. Affected users can update the app immediately in the Google Play store, or will be automatically updated over the coming days.

3. monitoring Jun 25, 2026, 09:09 PM UTC

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

Read the full incident report →

Started Jun 24, 2026, 06:05 PM UTC· resolved Jul 07, 2026, 09:18 PM UTC

1. monitoring Jun 24, 2026, 06:05 PM UTC

   Starting around 9:40 AM PST on June 24th 2026, our engineers began investigating an issue with Click Tracked links from EU Regionalized configured senders not working. Users may experience recipients seeing a 'Your connection is not private' when clicking links sent from EU regionalized configured accounts. This does not impact mail send. This does not impact accounts configured for Global sending. We will provide another update in 1 hour or as soon as more information becomes available.

2. monitoring Jun 24, 2026, 06:10 PM UTC

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

3. monitoring Jun 24, 2026, 06:15 PM UTC

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

4. monitoring Jun 24, 2026, 06:19 PM UTC

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

5. monitoring Jun 24, 2026, 06:54 PM UTC

   Our engineers have monitored the fix and confirmed the issue with Click Tracked links from EU Regionalized Senders has been resolved. All services are now operating normally at this time.

Read the full incident report →

Started Jun 24, 2026, 08:00 AM UTC· resolved Jul 06, 2026, 12:23 PM UTC

1. monitoring Jun 24, 2026, 08:00 AM UTC

   Maintenance tasks: Illumia will perform scheduled maintenance on the Cloud POS Back Office environment. Please be sure to read the Cloud POS 6.29.28 Release Notes to learn more. Expected impact: There is no expected downtime for this maintenance, however, any scheduled exports or reports 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 Jun 24, 2026, 10:00 AM UTC

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

Read the full incident report →

Started Jun 23, 2026, 07:45 PM UTC· resolved Jul 07, 2026, 08:30 PM UTC

1. monitoring Jun 23, 2026, 07:45 PM UTC

   Illumia engineers are aware that a small subset of users users may occasionally encounter an error while logging into the the Illumia Payments eMarket and ePayments sites. We are working working towards a resolution.

2. monitoring Jun 24, 2026, 12:48 AM UTC

   Illumia Engineers have engaged with our cloud vendor to troubleshoot the issue affecting a small subset of users.

3. monitoring Jun 25, 2026, 01:54 PM UTC

   Illumia Engineers have identified a workaround to this issue and are completing validation in lower environments before implementing it in production. The number of users impacted by this issue remains very low, and it is only impacting a very small number of login attempts.

4. monitoring Jun 26, 2026, 05:12 PM UTC

   The workaround has been successfully validated in lower environments. Because implementing the workaround will require a brief interruption in service, and since the current impact from this issue is extremely low, we will be implementing the workaround during the already scheduled maintenance window this Saturday night/Sunday morning.

5. monitoring Jun 28, 2026, 12:56 PM UTC

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

6. monitoring Jun 28, 2026, 03:34 PM UTC

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

Read the full incident report →

Started Jun 23, 2026, 02:26 PM UTC· resolved Jul 06, 2026, 04:10 PM UTC

1. monitoring Jun 23, 2026, 02:26 PM UTC

   Illumia is excited to announce the release of Mobile Ordering Android Application 2026.2 on June 24th. Please be sure to read the Mobile Ordering Android Application 2026.2 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.

2. monitoring Jun 30, 2026, 08:00 AM UTC

   The Software Bulletin notification has been removed from the site.

Read the full incident report →

Started Jun 22, 2026, 02:04 AM UTC· resolved Jul 06, 2026, 09:17 AM UTC

1. monitoring Jun 22, 2026, 02:04 AM UTC

   We are aware of issues affecting processing via Session-Initiated IVR. Windcave is currently investigating this with priority. Further updates will follow.

2. monitoring Jun 23, 2026, 02:04 AM UTC

   auto-closed

Read the full incident report →

Started Jun 21, 2026, 10:33 AM UTC· resolved Jul 02, 2026, 03:55 AM UTC

1. monitoring Jun 21, 2026, 10:33 AM UTC

2. monitoring Jun 21, 2026, 10:54 AM UTC

   Illumia Engineers have determined that the service(s) ePayments, checkout and storefront sites are currently unavailable.

3. monitoring Jun 21, 2026, 11:50 AM UTC

   The issue with the service(s) Admin Site and Cashiering, ePayment Sites, eMarket Sites is tentatively resolved and Illumia engineers are monitoring the systems to confirm there are no further issues.

4. monitoring Jun 21, 2026, 12:13 PM UTC

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

Read the full incident report →

Started Jun 19, 2026, 10:46 PM UTC· resolved Jun 26, 2026, 09:18 AM UTC

1. monitoring Jun 19, 2026, 10:46 PM UTC

   Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.

2. monitoring Jun 26, 2026, 05:13 AM UTC

   Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.

Read the full incident report →

Started Jun 16, 2026, 01:19 AM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 16, 2026, 01:19 AM UTC

   Some users may have been unable to edit or delete messages in certain channels. We identified and resolved the issue. We apologize for how this issue affected you and your business.

2. monitoring Jun 16, 2026, 01:19 AM UTC

   Resolved.

Read the full incident report →

Started Jun 14, 2026, 09:00 PM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 14, 2026, 09:00 PM UTC

   Twilio-Sendgrid mail delivery was degraded for approximately 16 minutes between 3:18 PM and 3:34 PM Pacific Time on 06/14/2026. During this period of time customers may have experienced delays affecting a subset of users. User experience was degraded with delayed mail delivery during this window, though the scope was limited to affected users rather than a system-wide outage. The issue has now been resolved.

2. monitoring Jun 14, 2026, 09:01 PM UTC

   Incident closed.

Read the full incident report →

Started Jun 14, 2026, 04:45 PM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 14, 2026, 04:45 PM UTC

   Starting around 12:00 AM PDT on June 14, 2026, our engineers began investigating an issue with our core API and platform services. Users may experience high latency, timeouts, and 5xx errors with sending email through the API and the UI. We will provide another update in 30 minutes or as soon as more information becomes available.

2. monitoring Jun 14, 2026, 05:20 PM UTC

   Engineers are still investigating issues causing email sending delays. We will provide a status update in 30 minutes or as soon as more information becomes available.

3. monitoring Jun 14, 2026, 05:34 PM UTC

   Our engineers have identified the issue and are working toward a fix. Mitigation efforts are underway to resolve the intermittent errors and delays. We will provide another update in 30 minutes or as soon as more information becomes available.

4. monitoring Jun 14, 2026, 06:11 PM UTC

   Our engineers have implemented a fix and are monitoring system performance. We will continue to observe the platform for the next hour to ensure full stability, and will mark this incident as resolved if no further issues are seen. We will provide another update in 1 hour or as soon as more information becomes available.

5. monitoring Jun 14, 2026, 07:23 PM UTC

   Our engineers have monitored the fix and confirmed the issue with high latency and 5xx errors has been resolved. All services are now operating normally at this time.

Read the full incident report →

Started Jun 11, 2026, 10:48 PM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 11, 2026, 10:48 PM UTC

   We are actively investigating reports of performance degradation affecting Bitbucket OAuth login. We will share updates here as more information is available.

2. monitoring Jun 11, 2026, 11:21 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience OAuth login issues in Bitbucket. We will continue to share additional updates here as more information is available.

3. monitoring Jun 11, 2026, 11:58 PM UTC

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

4. monitoring Jun 12, 2026, 12:14 AM UTC

   On June 11, 2026, Bitbucket users may have experienced performance degradation affecting Bitbucket OAuth login. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jun 11, 2026, 10:13 PM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 11, 2026, 10:13 PM UTC

   We're aware of an issue affecting the Slack desktop app. Users may find that content in child windows, such as channels or documents opened in a separate window, displays at reduced height. We’ve identified the technical trigger and are deploying a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

2. monitoring Jun 11, 2026, 10:43 PM UTC

   We’ve deployed a fix and are now performing validations. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jun 11, 2026, 11:15 PM UTC

   We've validated that the fix resolved the issue and child windows are now displaying content as expected. You may need to reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) in order for this fix to be reflected on your end. We're sorry for the disruption this caused to your day.

4. monitoring Jun 11, 2026, 11:16 PM UTC

   Resolved.

Read the full incident report →

Started Jun 10, 2026, 08:36 PM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 10, 2026, 08:36 PM UTC

   We're aware of an issue impacting the Slack Gmail add-on integration. As a result, users are unable to interact with the add-on and may encounter a “Something went wrong when executing the add-on. For help, contact the add-on developer” error message when attempting to use it. We are investigating the cause of this issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

2. monitoring Jun 10, 2026, 09:05 PM UTC

   We’re still actively investigating the issue impacting the Slack Gmail add-on. We are working to identify the cause, and no workaround is currently available. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jun 10, 2026, 09:37 PM UTC

   We’re still investigating the issue impacting Slack Gmail add-ons. No additional news to share just yet, but we’re focused on getting things back to normal as quickly as we can. We apologize for the continued trouble. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

4. monitoring Jun 10, 2026, 10:49 PM UTC

   We’re still investigating the issue impacting Slack Gmail add-ons. No additional news to share just yet, but we’re focused on getting things back to normal as quickly as we can. We apologize for the continued trouble. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring Jun 10, 2026, 11:39 PM UTC

   We continue to investigate the issue impacting Slack Gmail add-ons. We've identified the cause and our teams are working on a fix to resolve the issue as soon as possible. We’ll provide an update once additional information becomes available.

6. monitoring Jun 11, 2026, 12:18 AM UTC

   We’re actively working on the fix to resolve the issue. We estimate this will take approximately four hours or more to complete, and validate the fix, before it can be deployed. As such, the next status update will be once the fix has been completed and validated, or we have new information to share. We apologize for any inconvenience this issue is causing for users.

7. monitoring Jun 11, 2026, 06:04 AM UTC

   We’re continuing to investigate the issues with the Slack Gmail add-on and are actively working on a fix to resolve the issue. There’s no new information to share at this time, but we’ll provide an update as soon as we have more details on implementing the fix. We apologize for any inconvenience this issue is causing for users.

8. monitoring Jun 11, 2026, 06:39 AM UTC

   We've resolved the issue that prevented customers from using the Slack Gmail add-on. The fix has been successfully deployed; health metrics have stabilized, and the Gmail add-on is now fully operational for all affected users. We apologize for any inconvenience this may have caused.

9. monitoring Jun 11, 2026, 06:40 AM UTC

   Resolved.

Read the full incident report →

Started Jun 10, 2026, 10:38 AM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 10, 2026, 10:38 AM UTC

   Transact engineers are investigating a possible issue with Mobile Credential for Google Pay Wallet. Mobile credential provisioning is currently offline. New credentials cannot be issued. Currently provisioned credentials will continue to work with no issues.

2. monitoring Jun 10, 2026, 11:13 AM UTC

   Our third-party service provider has informed us that the issue with Mobile Credential is limited to provisioning with Samsung Wallet. Google and Apple Pay will continue to work as expected. We will provide an update when more information is available.

3. monitoring Jun 10, 2026, 01:40 PM UTC

   The issue with the service(s) Mobile Credential for Google Pay Wallet is tentatively resolved and Illumia engineers are monitoring the systems to confirm there are no further issues.

4. monitoring Jun 10, 2026, 01:51 PM UTC

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

Read the full incident report →

Started Jun 10, 2026, 09:42 AM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 10, 2026, 09:42 AM UTC

   Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.

2. monitoring Jun 10, 2026, 10:00 AM UTC

   On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets. We have implemented a fix and services have been restored to normal operation for all affected customers.

Read the full incident report →

Started Jun 10, 2026, 05:07 AM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 10, 2026, 05:07 AM UTC

   Starting around 9:25 AM GMT+8 on June 10, 2026, our engineers began investigating an issue affecting email processing within SendGrid. Users may have experienced elevated email deferrals, with some messages temporarily receiving "Internal Server Error" responses during delivery attempts. This issue does not impact mail send capability; however, delivery may have been delayed for a subset of messages. Our team continues to investigate the root cause and monitor system performance. We will provide another update in 60 minutes or as soon as more information becomes available.

2. monitoring Jun 10, 2026, 05:51 AM 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 Jun 10, 2026, 08:49 AM UTC

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

Read the full incident report →

Started Jun 10, 2026, 04:55 AM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 10, 2026, 04:55 AM UTC

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

2. monitoring Jun 10, 2026, 05:39 AM UTC

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. monitoring Jun 10, 2026, 06:14 AM UTC

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. monitoring Jun 10, 2026, 06:31 AM UTC

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Started Jun 09, 2026, 09:50 PM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 09, 2026, 09:50 PM UTC

   Illumia Engineers have been informed of a third-party issue which is intermittently causing high latency receiving mobile orders. We will provide additional updates as we receive them.

2. monitoring Jun 09, 2026, 11:44 PM UTC

   Our third-party provider is still working to resolve the issue causing latency with some mobile orders. They are actively working on mitigations, but are still seeing failures at this time. Our next update will be sent tomorrow morning.

3. monitoring Jun 10, 2026, 10:50 AM UTC

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

4. monitoring Jun 10, 2026, 02:06 PM UTC

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

Read the full incident report →

Started Jun 09, 2026, 06:23 PM UTC· resolved Jun 16, 2026, 05:09 AM UTC

1. monitoring Jun 09, 2026, 06:23 PM UTC

   Illumia engineers have identified an issue processing IDX imports and are currently investigating.

2. monitoring Jun 09, 2026, 07:18 PM UTC

   This issue is affecting only a small subset of clients. Most imports are going through without delays. Illumia engineers continue to investigate issues with the few affected clients.

3. monitoring Jun 09, 2026, 08:50 PM UTC

   Illumia engineers have been notified of a third-party service provider issue which is causing high latency for some client imports. We will provide updates as we receive them.

4. monitoring Jun 09, 2026, 11:41 PM UTC

   Our third-party provider is still working to resolve the issue causing latency with some file uploads to IDX. They are actively working on mitigations, but are still seeing failures at this time. Our next update will be sent tomorrow morning.

5. monitoring Jun 10, 2026, 10:49 AM UTC

   The issue with the service(s) Transact IDX, Door Access is tentatively resolved and Illumia engineers are monitoring the systems to confirm there are no further issues.

6. monitoring Jun 10, 2026, 01:21 PM UTC

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

Read the full incident report →

Started Jun 09, 2026, 05:29 AM UTC· resolved Jun 14, 2026, 04:39 PM UTC

1. monitoring Jun 09, 2026, 05:29 AM UTC

   We are investigating reports of intermittent errors and degredated performance for some Jira Service Management and Jira Cloud customers. We will provide further updates within one hour.

2. monitoring Jun 09, 2026, 06:21 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

3. monitoring Jun 09, 2026, 06:22 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

4. monitoring Jun 09, 2026, 09:26 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

5. monitoring Jun 09, 2026, 09:27 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

6. monitoring Jun 09, 2026, 10:20 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

7. monitoring Jun 09, 2026, 10:21 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

8. monitoring Jun 09, 2026, 10:36 AM UTC

   Our team has been able to apply the fix and mitigate the issue. The services have been restored to normal operations. We will continue to actively monitor over the next 8 hours to confirm stability.

9. monitoring Jun 09, 2026, 06:27 PM UTC

   The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jun 08, 2026, 05:25 PM UTC· resolved Jun 10, 2026, 11:38 PM UTC

1. monitoring Jun 08, 2026, 05:25 PM UTC

   Illumia is pleased to announce a Quickcharge release scheduled for the late evening of June 11 through the early morning of June 12. Please check your Back Office system for an in-app message to determine whether your site is included in this deployment wave. Release Notes will be distributed in a future communication and will also be available through our support channels. Thank you for being a valued Quickcharge customer. The Quickcharge Team If you have any questions, please open a case via Transact Connect or call Quickcharge Support at 844-766-4435.

Read the full incident report →