Ticketmatic Outage History

Ticketmatic is up right now

Ticketmatic had 3 outages in the last 2 years totaling 7h 0m of downtime — averaging 0.1 incidents per month.

There were 3 Ticketmatic outages since September 7, 2024 totaling 7h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.ticketmatic.com

Major May 7, 2026

Service Disruption

Detected by Pingoru
May 07, 2026, 07:12 AM UTC
Resolved
May 07, 2026, 08:24 AM UTC
Duration
1h 12m
Affected: Backoffice
Timeline · 2 updates
  1. investigating May 07, 2026, 07:12 AM UTC

    We are currently experiencing an issue affecting our services. Our team is actively investigating the situation and working to identify the root cause. We understand the impact this may have and are treating this with high priority. We will provide updates as soon as more information becomes available. Thank you for your patience.

  2. resolved May 07, 2026, 08:24 AM UTC

    Between 9:00 and 10:00 today, part of our back office was unavailable, affecting backoffice users. Customer-facing ticket services were not impacted. The disruption was caused by a security update to our infrastructure. The update has been completed and full functionality is restored. We apologize for the inconvenience to affected back office users. If you're still experiencing issues, please reach out to support.

Read the full incident report →

Major September 7, 2024

Problem with static assets

Detected by Pingoru
Sep 07, 2024, 04:06 PM UTC
Resolved
Sep 07, 2024, 04:22 PM UTC
Duration
16m
Affected: WebsalesBackoffice
Timeline · 3 updates
  1. investigating Sep 07, 2024, 04:06 PM UTC

    We get reports of problems with downloading static assets like images and tickets. We are currently investigating this issue.

  2. monitoring Sep 07, 2024, 04:18 PM UTC

    The cause for the problem is identified as a malfunctioning DNS connection, resulting in problems connecting to the interal filestore. We applied a fix and we are monitoring the situation.

  3. resolved Sep 07, 2024, 04:22 PM UTC

    This incident has been resolved.

Read the full incident report →