Transact Outage History

Transact is up right now

Transact had 79 outages in the last 2 years totaling 5366h 48m of downtime — averaging 3.2 incidents per month.

There were 79 Transact outages since April 14, 2026 totaling 5366h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.transactcampus.com/rss

Minor June 5, 2026

Quickcharge - Software Deployment

Detected by Pingoru
Jun 05, 2026, 06:00 AM UTC
Resolved
Jun 10, 2026, 10:48 AM UTC
Duration
5d 4h
Timeline · 1 update
  1. 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 →

Minor June 2, 2026

Degraded performance of Jira automations

Detected by Pingoru
Jun 02, 2026, 04:51 PM UTC
Resolved
Jun 10, 2026, 04:51 AM UTC
Duration
7d 12h
Timeline · 1 update
  1. 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 →

Minor June 1, 2026

For Jira-software viewIssues and viewBoard are degraded

Detected by Pingoru
Jun 01, 2026, 01:23 PM UTC
Resolved
Jun 09, 2026, 06:20 PM UTC
Duration
8d 4h
Timeline · 1 update
  1. 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 →

Minor May 29, 2026

Additional Products Coming Soon

Detected by Pingoru
May 29, 2026, 02:25 AM UTC
Resolved
Jun 08, 2026, 02:10 AM UTC
Duration
9d 23h
Timeline · 1 update
  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 →

Minor May 27, 2026

Severe Latency Impacting All Slack Services

Detected by Pingoru
May 27, 2026, 11:02 PM UTC
Resolved
Jun 08, 2026, 02:10 AM UTC
Duration
11d 3h
Timeline · 1 update
  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 →

Minor May 25, 2026

TS SaaS - Scheduled Reports

Detected by Pingoru
May 25, 2026, 04:11 PM UTC
Resolved
Jun 02, 2026, 05:34 PM UTC
Duration
8d 1h
Timeline · 1 update
  1. 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 →

Minor May 22, 2026

SenderAuth and Whitelabel domain errors

Detected by Pingoru
May 22, 2026, 06:50 PM UTC
Resolved
Jun 01, 2026, 01:23 PM UTC
Duration
9d 18h
Timeline · 1 update
  1. 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 →

Minor May 20, 2026

TSE - InCommon SSL certificate issue

Detected by Pingoru
May 20, 2026, 09:45 PM UTC
Resolved
Jun 01, 2026, 10:04 AM UTC
Duration
11d 12h
Timeline · 1 update
  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 →

Minor May 18, 2026

Transact IDX

Detected by Pingoru
May 18, 2026, 11:49 PM UTC
Resolved
May 29, 2026, 12:26 PM UTC
Duration
10d 12h
Timeline · 1 update
  1. monitoring May 18, 2026, 11:49 PM UTC

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

Read the full incident report →