- Service Status
- /
- Weave

Is Weave Down?
- Weave's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 1044 ms
Right now
The verdict is the worse of these two. How we decide
Weave's status page
status.getweave.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Phone Service | Operational |
| SMS (texting) Service | Operational |
| Automated Schedule Reminders | Operational |
| Reviews Service | Operational |
| Call Recording Service | Operational |
| Email Marketing | Operational |
| Fax Service | Operational |
| Mobile App | Operational |
| Desktop Application | Operational |
| Payments | Operational |
| Weave Portal | Operational |
FlareWarden checks
app.getweave.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 1044 ms
- Checked
By region
- Ashburn reachable, 1600 ms
- Chicago reachable, 383 ms
- Johannesburg reachable, 2466 ms
- London reachable, 1202 ms
- Los Angeles reachable, 181 ms
- San Jose reachable, 280 ms
- Singapore reachable, 1131 ms
- Tokyo reachable, 1111 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 31 ms | 1 ms | 12 ms | 107 ms |
| Chicago | 54 ms | 2 ms | 11 ms | 132 ms |
| Johannesburg | 177 ms | 0 ms | 11 ms | 1056 ms |
| London | 28 ms | 2 ms | 13 ms | 538 ms |
| Los Angeles | 43 ms | 4 ms | 10 ms | 93 ms |
| San Jose | 94 ms | 3 ms | 13 ms | 152 ms |
| Singapore | 13 ms | 1 ms | 14 ms | 250 ms |
| Tokyo | 115 ms | 0 ms | 12 ms | 529 ms |
History
Incidents Weave reported
Since Oct 22, 1 day · from status.getweave.com
- Incidents
- 3
- Major or critical
- 0
- Median to resolve
- 6m
- lasted 1h 23m
- lasted 3m
- lasted 6m
minor ·
Weave website availability
Measured by FlareWarden · app.getweave.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 1089ms
Last 30 days
27-day clean streakMeasured by FlareWarden's own checks of app.getweave.com from multiple regions every 6 hours. Weave's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 27 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Weave does
Weave, from Weave Communications in Lehi, Utah, is the patient communication platform used by independent dental, optometry, veterinary and medical practices, not the other products of that name. It supplies the office's VoIP phones and combines calls, two-way texting, appointment reminders, reviews, fax, email marketing and payments in a desktop app, a web portal and a mobile app, synced with the practice management system.
What an outage looks like
Desk phones stop ringing, calls connect with no audio, voicemails will not open or Polycom handsets show error messages. Texts to patients fail to send, reminders stop going out, or text-to-pay links open an error page. The desktop app or portal may not load or sign in. Integration faults look different: patient and appointment data that stops updating from the practice management system.
What to do about it
Check status.getweave.com, which lists Phone Service, SMS (texting) Service, Automated Schedule Reminders, Payments, Fax Service, Mobile App, Desktop Application and Weave Portal separately. If only your office is affected, Weave suggests using its mobile app to forward calls to a cell phone and set an emergency voicemail. Weave support is 888-579-5668, with live chat in the help portal.
Is it down for everyone, or just you?
If this page says Weave 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
Weave outage FAQ
Is Weave down for everyone or just my office?
Can I still take calls when Weave phones are down?
Does a practice management system outage affect Weave?
Why are Weave texts not sending?
Which Weave is this?
How we measure this
- We request Weave's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 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 Weave 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 Weave 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 Weave goes down
We check Weave 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

