Vagaro Outage History
Uptime record, past incidents, and downtime history for Vagaro.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 91.7% | 12 | 1 |
| April 2026 | 93.3% | 30 | 2 |
| March 2026 | 100% | 4 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 46 Days)
Mar 28
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
System degradation May 7, 2026
Started: May 7, 2:56 PM
identified
Our development team is continuing to work diligently to resolve the service slowdown/interruption currently impacting some Vagaro customers. We appreciate your continued patience and apologize for the disruption this may be causing
May 7, 4:51 PM
identified
Our development team is still actively working to resolve the current slowdown/service interruption some Vagaro customers are experiencing. We thank you for your patience and we apologize for any inconvenience.
May 7, 3:28 PM
identified
Some Vagaro customers are currently experiencing a slowdown/service interruption. Our development team is actively working to resolve this issue as soon as possible. We apologize for any inconvenience.
May 7, 2:56 PM
April 2026
Performance Issues
Started: Apr 21, 9:46 PM
investigating
Some Vagaro customers are currently experiencing a slowdown/service interruption. Our development team is actively working to resolve this issue as soon as possible. We apologize for any inconvenience.
Apr 21, 9:46 PM
Performance Issues
Started: Apr 8, 4:22 PM
identified
Some Vagaro customers are currently experiencing a slowdown/service interruption. Our development team is actively working to resolve this issue as soon as possible. We apologize for any inconvenience.
Apr 8, 4:22 PM
March 2026
Performance Issues
Started: Mar 31, 5:01 PM
identified
Some Vagaro customers are currently experiencing a slowdown/service interruption. Our development team is actively working to resolve this issue as soon as possible. We apologize for any inconvenience.
Mar 31, 5:01 PM