Upserve Outage History

16 incidents recorded over the last 365 days, 7 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 Upserve status100.00% uptime history

Every Recorded Upserve Incident

Upserve incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 22, 202610/22/26 Service Interruption: Guestbook, Magic Quadrant, & Repeat Customer FavoritesThis incident has been resolved.24h 1mResolved
Oct 21, 2026PHP Security Vulnerability MitigationThis incident has been resolved.14 minResolved
Oct 13, 2026Intermittent Disruption Impacting HQ Reporting, Workforce, and Online OrderingThis incident has been resolved.3h 19mResolved
Oct 13, 2026Intermittent Disruption Impacting HQ Reporting, Workforce, and Online OrderingThis incident has been resolved.2h 54mResolved
Aug 19, 20268/19/2026 Elevated Online Ordering ErrorsThe Upserve engineering team has resolve an issue causing an increase in Online Ordering errors. If you are experiencing any issues with Online Ordering, please contact support.1h 4mResolved
Jul 23, 202607/22/2026 Upserve Inventory DegradationWe believe this incident to be resolved, and the Upserve Inventory system to be working normally at this time. However, the root cause of the incident resulted in inconsistent counts data and missing purchase order…26h 26mResolved
Jul 21, 202607/21/2026 Upserve Inventory DegradationThis incident has been resolved.25h 10mResolved
Jun 2, 2026Scheduled Maintenance 06/02/2026The scheduled maintenance has been completed.1h 30mScheduled
Jun 1, 2026Scheduled Maintenance 06/01/2026The scheduled maintenance has been completed.30 minScheduled
May 26, 2026Scheduled Maintenance 05/26/2026The scheduled maintenance has been completed.1h 0mScheduled
May 19, 2026Scheduled Maintenance 05/19/2026The scheduled maintenance has been completed.1h 0mScheduled
May 12, 2026Scheduled Maintenance 05/12/2026The scheduled maintenance has been completed.1h 35mScheduled
May 11, 2026Scheduled Maintenance 05/11/2026The scheduled maintenance has been completed.30 minScheduled
May 10, 2026Scheduled Maintenance 05/10/2026The scheduled maintenance has been completed.30 minScheduled
May 5, 2026Scheduled Maintenance 05/05/2026The scheduled maintenance has been completed.1h 30mScheduled
May 3, 2026Scheduled Maintenance 05/03/2026The scheduled maintenance has been completed.2h 30mScheduled

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 Upserve 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 Upserve 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 Upserve 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 Upserve outage in this window ran 1d 2h, against a mean recovery of 5h 51m. If you depend on Upserve 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.