Ticketnetwork Outage History

26 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Ticketnetwork status100.00% uptime history

Every Recorded Ticketnetwork Incident

Ticketnetwork incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 27, 2026Production PatchingThe scheduled maintenance has been completed.5h 0mScheduled
Oct 26, 2026Production PatchingThe scheduled maintenance has been completed.5h 0mScheduled
Oct 23, 2026POSNext / TN Open APIs (Broker API) MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Sep 29, 2026Production Server MaintenanceThe scheduled maintenance has been completed.5h 0mScheduled
Sep 28, 2026Production Server MaintenanceThe scheduled maintenance has been completed.5h 0mScheduled
Sep 18, 2026Performance DegradedThis incident has been resolved. Please reach out to our support teams to report any problems or concerns.17 minResolved
Sep 11, 2026POSNext / TN Open APIs (Broker API) MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Aug 27, 2026Maps and Checkout Performance DegradedThis incident has been resolved. Please reach out to our support teams to report any problems or concerns.43 minResolved
Aug 6, 2026POSNext reporting outageThis incident has been resolved.17h 40mResolved
Aug 4, 2026POSNext / TN Open APIs (Broker API) MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jun 17, 2026POSNext / TN Open APIs (Broker API) MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jun 4, 2026Production Database MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
May 14, 2026Production Database MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
May 8, 2026Sandbox Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Apr 30, 2026Sandbox API MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Apr 20, 2026Signature Site - Retail Website performanceThis incident has been resolved. Please reach out to our support teams to report any problems or concerns.44 minResolved
Mar 31, 2026POSNext / TN Open APIs (Broker API) MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Mar 30, 2026Retail User AccountsThis incident has been resolved. Please reach out to our support teams to report any problems or concerns.1h 22mResolved
Mar 27, 2026Maintenance Scheduled - FreshdeskThe scheduled maintenance has been completed.1h 0mScheduled
Mar 17, 2026Performance DegradedThis incident has been resolved.46 minResolved
Feb 16, 2026Broker Software MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 10, 2026Retail Website performanceThis incident has been resolved. Please reach out to our support teams to report any problems or concerns.1h 46mResolved
Dec 18, 2025Reporting DelaysThis incident has been resolved. Please reach out to our support teams to report any problems or concerns.1h 29mResolved
Dec 11, 2025Performance DegradedThis incident has been resolved27 minResolved
Dec 8, 2025ezEvent.com is downezEvent is back and up-and-running.1h 41mResolved
Dec 8, 2025POSNext not loadingThis incident has been resolved30 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Ticketnetwork incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Ticketnetwork Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Ticketnetwork acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Ticketnetwork outage in this window ran 17h 40m, against a mean recovery of 2h 56m. If you depend on Ticketnetwork in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.