Vagaro Outage History

12 incidents recorded over the last 365 days, 12 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.

Every Recorded Vagaro Incident

Vagaro incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 15, 2026Site loading issues - Sept 15, 2026This incident has been resolved.4h 37mResolved
Jul 23, 2026Login IssuesThis incident has been resolved.2h 53mResolved
May 7, 2026System degradation May 7, 2026This incident has been resolved. We apologize for any inconvenience this may cause and thank you for your patience and understanding.2h 23mResolved
Apr 21, 2026Performance IssuesThis incident has been resolved. We apologize for any inconvenience this may cause and thank you for your patience and understanding.32 minResolved
Apr 8, 2026Performance IssuesThis incident has been resolved. We apologize for any inconvenience this may cause and thank you for your patience and understanding.1h 51mResolved
Mar 31, 2026Performance IssuesThis incident has been resolved. We apologize for any inconvenience this may cause and thank you for your patience and understanding.56 minResolved
Mar 13, 2026Checkout Error CodeThis incident has been resolved. We apologize for any inconvenience this may cause and thank you for your patience and understanding.1h 24mResolved
Mar 3, 2026Performance Issues East Coast RegionThis incident has been resolved. We apologize for any inconvenience this may cause and thank you for your patience and understanding.51 minResolved
Mar 3, 2026Important: Federal Reserve Deposits Delays (ACH) TransfersThis incident has been resolved. We apologize for any inconvenience this may cause and thank you for your patience and understanding.2h 23mResolved
Feb 19, 2026Performance IssuesThis incident has been resolved. We apologize for any inconvenience this may cause and thank you for your patience and understanding.1h 34mResolved
Feb 13, 2026Slowdown in service Feb 13This incident has been resolved.7h 8mResolved
Feb 7, 2026Performance IssuesThis incident has been resolved. We apologize for any inconvenience this may cause and thank you for your patience and understanding.23 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 Vagaro 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 Vagaro 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 Vagaro 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 Vagaro outage in this window ran 7h 8m, against a mean recovery of 2h 15m. If you depend on Vagaro 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.