- Service Status
- /
- Vagaro

Is Vagaro Down?
- Vagaro's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 7 of 7 regions · 1827 ms
Right now
The verdict is the worse of these two. How we decide
Vagaro's status page
status.vagaro.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Vagaro.com the service itself | Operational |
| Vagaro Pro App | Operational |
| Vagaro Clients App | Operational |
| Credit Card Processing | Operational |
| Email Reminders | Operational |
| Email Marketing | Operational |
| Third Party - Twilio Outgoing SMS | Operational |
| Sendgrid Email API | Operational |
| SendGrid Email API Version 3 | Operational |
| Vagaro Phone Support | Operational |
FlareWarden checks
vagaro.com from 7 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 7 of 7
- Response
- 1827 ms
- Checked
By region
- Amsterdam reachable, 2366 ms
- Ashburn reachable, 939 ms
- Dallas reachable, 828 ms
- Frankfurt reachable, 3990 ms
- Newark reachable, 628 ms
- Paris reachable, 1663 ms
- São Paulo reachable, 2377 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 640 ms | 9 ms | 11 ms | 1745 ms |
| Ashburn | 60 ms | 1 ms | 3 ms | 650 ms |
| Dallas | 130 ms | 7 ms | 12 ms | 508 ms |
| Frankfurt | 538 ms | 165 ms | 169 ms | 3126 ms |
| Newark | 30 ms | 1 ms | 5 ms | 408 ms |
| Paris | 112 ms | 1 ms | 4 ms | 1218 ms |
| São Paulo | 764 ms | 2 ms | 5 ms | 1677 ms |
History
Incidents Vagaro reported
Since Oct 22, 2 days · from status.vagaro.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Vagaro website availability
Measured by FlareWarden · vagaro.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 1628ms
Last 30 days
24-day clean streakMeasured by FlareWarden's own checks of vagaro.com from multiple regions every 6 hours. Vagaro's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 24 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Vagaro does
Vagaro is business software for beauty, wellness and fitness businesses, from booth renters and barbers to spas, med spas and multi-location gyms. Owners and staff run the calendar, online booking, checkout and card payments, forms and client reminders from vagaro.com or the Vagaro Pro app, while their clients use the Vagaro Clients app. Card processing runs through Vagaro Merchant Services, so an outage can stop both booking and payment.
What an outage looks like
Most Vagaro incidents are slowdowns: the calendar and checkout load slowly or stop responding on vagaro.com and the Vagaro Pro app at once, sometimes only for businesses in one US region. Narrower failures include Pro app logins that fail, cards rejected at checkout with error codes such as 6-422-908 or 3-345, delayed ACH deposits, and online booking that fails for clients while the rest works.
What to do about it
Open status.vagaro.com, which Vagaro's help center links, and see which row is marked: Vagaro.com, the Pro or Clients app, Credit Card Processing, Email Reminders, Twilio outgoing SMS or phone support. If every row is green, Vagaro suggests restarting the device, checking the internet connection, reinstalling the Pro app or clearing browser cache. US support is (925) 464-1932 ext. 2, or email support@vagaro.com.
Is it down for everyone, or just you?
If this page says Vagaro is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Vagaro outage FAQ
Is Vagaro down for everyone or just me?
Why is Vagaro declining cards at checkout?
Does the Vagaro Pro app work when vagaro.com is down?
Will appointment reminders and texts still go out?
How do I reach Vagaro support during an outage?
How we measure this
- We request Vagaro's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 7 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Vagaro publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Vagaro itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Vagaro goes down
We check Vagaro every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring

