All Systems Operational

About This Site

If you are experiencing issues and there are no active incidents below, please contact Spruce support in-app or at support@sprucehealth.com

Web App Operational
90 days ago
99.99 % uptime
Today
Mobile Apps Operational
90 days ago
99.99 % uptime
Today
Phone Call Routing Operational
90 days ago
99.96 % uptime
Today
Marketing Website Operational
90 days ago
100.0 % uptime
Today
Fax Operational
90 days ago
100.0 % uptime
Today
SMS Routing Operational
90 days ago
100.0 % uptime
Today
Video Calling Operational
90 days ago
100.0 % uptime
Today
Spruce app notifications Operational
90 days ago
100.0 % uptime
Today
Integrations Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Sep 1, 2026
Resolved - We have confirmation from our telecommunications partner that their systems are fully operational. We are noticing the same on our end.
Sep 1, 15:18 PDT
Update - We have confirmation from our telecommunications partner that their systems are fully operational. We are noticing the same on our end.
Sep 1, 15:17 PDT
Monitoring - Between 9:00 AM and 10:27 AM PT, an outage at one of our upstream telecommunications providers affected calling and message delivery on Spruce.

During this window:

* Calling: Some inbound and outbound calls failed to connect. Affected inbound calls were routed to voicemail where a voicemail greeting was configured. Affected outbound calls failed with an error indicating the call could not be placed.
* Inbound SMS: Some incoming text messages were delayed.
* Voicemail: Some voicemails were delayed in appearing in Spruce.

Spruce itself remained available throughout. Teammates could sign in, access their conversations, and send messages as normal. Outbound text messages sent during this period were all eventually delivered.

Our provider has confirmed their systems are operating normally, and we have seen normal calling and message delivery on Spruce since 10:27 AM PT.

We're sorry for the disruption and are actively monitoring to ensure that the system remains fully operational.

Sep 1, 09:00 PDT
Aug 31, 2026
Completed - The scheduled infrastructure maintenance has been completed.

We observed no impact to the Spruce application, API, messaging, or calling during this window.

The platform is fully operational.

Aug 31, 20:43 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 31, 20:00 PDT
Scheduled - We will be performing schedule infrastructure maintenance on August 31 between 8:00PM - 10:00PM PT.

During this window, you may experience brief periods (typically a few seconds) where the Spruce API may return temporary errors on requests that use an idempotency key, and new group SMS conversations may fail to create. Existing conversations and other messaging should be largely unaffected.

There will be no impact to accessing the Spruce application or to making and receiving calls.

An engineer will be actively monitoring the system throughout the maintenance window. We'll work to keep any impact as brief as possible and will post updates here as work progresses.

We apologize for any inconvenience.

Aug 26, 12:15 PDT
Aug 30, 2026

No incidents reported.

Aug 29, 2026

No incidents reported.

Aug 28, 2026

No incidents reported.

Aug 27, 2026

No incidents reported.

Aug 26, 2026

No incidents reported.

Aug 25, 2026

No incidents reported.

Aug 24, 2026
Resolved - Resolved — This incident has been resolved.

On August 24, 2026, Spruce Inbox intermittently failed to reflect the current state of conversations in real time, across three separate periods. During these windows, conversations were delayed in appearing or updating in the inbox, and unread counts could also be inaccurate — the two symptoms didn't always occur together, so a conversation could lag even when the unread count looked correct, and vice versa. This did not affect the ability to make or receive calls, or to send and receive messages; the issue was limited to how the inbox displayed and refreshed that activity.

The issue was caused by a bug in inbox indexing introduced by a recent programming language runtime upgrade. A fix was deployed at 5:10 PM PT on August 24, and the inbox has been refreshing normally since.

Affected periods (all times PT, August 24, 2026):
* 12:11 PM – 1:05 PM
* 1:39 PM – 1:55 PM
* 2:50 PM – 3:05 PM

Aug 24, 17:00 PDT
Identified - This is a retroactive update for an incident that occurred on August 24, 2026. The issue was identified around 12pm PT.
Aug 24, 12:00 PDT
Aug 23, 2026

No incidents reported.

Aug 22, 2026

No incidents reported.

Aug 21, 2026

No incidents reported.

Aug 20, 2026

No incidents reported.

Aug 19, 2026

No incidents reported.

Aug 18, 2026

No incidents reported.