Ticketmatic incident

Service disruption

Resolved after 3 hours 8 minutes, on May 18, 2016.

monitoring May 18, 2016, 07:02 PM UTC

The issue is resolved for now, we keep monitoring

Started
May 18, 2016, 06:18 PM UTC
Resolved
May 18, 2016, 09:27 PM UTC
Duration
3h 8m
Detected by Pingoru
May 18, 2016, 06:18 PM UTC

Update timeline

  1. investigating May 18, 2016, 06:18 PM UTC

    We experience a service disruption at this moment. We are further investigating

  2. investigating May 18, 2016, 06:24 PM UTC

    The cause for the disruption is identified and caused by excessive amount of database connections. The disruption is limited to a single account

  3. monitoring May 18, 2016, 07:02 PM UTC

    The issue is resolved for now, we keep monitoring

  4. resolved May 18, 2016, 09:27 PM UTC

    This incident has been resolved.

Your product runs on more than Ticketmatic

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →