Ticketmatic Outage History

Ticketmatic is up right now

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

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

Source: http://status.ticketmatic.com

Notice June 26, 2026

Service Disruption

Detected by Pingoru
Jun 26, 2026, 07:01 AM UTC
Resolved
Jun 26, 2026, 09:48 AM UTC
Duration
2h 46m
Affected: WebsalesBackofficeAPI
Timeline · 4 updates
  1. investigating Jun 26, 2026, 07:01 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. monitoring Jun 26, 2026, 08:20 AM UTC

    A fix has been implemented and we are monitoring the results.

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

    Full service has been restored. Some customers may have experienced intermittent timeouts as systems recovered.

  4. resolved Jun 26, 2026, 09:48 AM UTC

    This incident has been resolved. The platform has been operating normally since approximately 11:00 CEST. The interruption was caused by a data-handling issue that placed excessive load on one of our databases; the underlying cause has been corrected. No data was lost. We apologise for the inconvenience.

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 →