Skip to main content
Weave logo

Is Weave Down?

No — Weave is up

Reachable from all 8 checked regions

Average response time: 1200ms

Last checked · checks run every 6 hours

Official status page: https://status.getweave.com

Weave uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1100ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 16 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

16-day clean streak
Sep 13: no data
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: no data
Sep 26: 100.00% uptime, 16 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: no data
Sep 13 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
2028ms
DNS 27ms TCP 2ms TLS 13ms TTFB 1432ms
arn
2435ms
DNS 45ms TCP 1ms TLS 12ms TTFB 1584ms
cdg
1066ms
DNS 43ms TCP 2ms TLS 14ms TTFB 450ms
dfw
368ms
DNS 80ms TCP 1ms TLS 8ms TTFB 152ms
ewr
371ms
DNS 68ms TCP 1ms TLS 10ms TTFB 136ms
fra
1342ms
DNS 106ms TCP 1ms TLS 11ms TTFB 559ms
syd
1523ms
DNS 147ms TCP 1ms TLS 10ms TTFB 686ms
yyz
473ms
DNS 24ms TCP 1ms TLS 12ms TTFB 158ms

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.

Test it yourself

Related services

M
Mindbody
RingCentral
RingCentral
Dialpad
Dialpad
Vonage
Vonage

Weave outage FAQ

Is Weave down for everyone or just my office?
Compare the status page with your own connection, because Weave phones are VoIP and need the office internet. status.getweave.com lists Phone Service, SMS, reminders, payments, fax and the apps as separate rows. If they are all green, the fault is more likely your internet or handsets; Weave recommends a backup internet provider or a second phone line for exactly this case.
Can I still take calls when Weave phones are down?
Often yes, through the Weave mobile app. Weave says the app gives access to the office line from a smartphone and lets staff reroute calls to a cell phone, set conditional forwarding or record an emergency voicemail. That works when the office internet or desk phones fail; it will not help if the Phone Service row on the status page itself is down.
Does a practice management system outage affect Weave?
Yes, integration outages break parts of Weave while its own rows stay green. In June 2026 Weave's eClinicalWorks integration was deactivated for about 360 offices, so patient and appointment data stopped syncing, and in July 2026 a Mindbody outage stopped customers searching, booking or rescheduling appointments inside Weave. These incidents are posted on the status page without a component attached.
Why are Weave texts not sending?
Check the SMS (texting) Service row first, since texting is tracked apart from phones. Weave posted an outbound SMS failure in September 2026 that was resolved the same day. Automated Schedule Reminders has its own row too, so a reminder problem can appear without a texting incident. If both rows are green, Weave's support page lists errors sending and receiving texts as a support issue.
Which Weave is this?
This page tracks Weave Communications, the patient communication and phone platform at getweave.com used by more than 40,000 practice locations. It is unrelated to other apps and products named Weave. The check here measures app.getweave.com, the web app practices sign in to, and the incidents shown come from Weave's own status page at status.getweave.com.

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.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Weave goes down

This page refreshes every 6 hours. 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
Free plan available No credit card required