Is Spruce Health down?

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.

We have confirmation from our telecommunications partner that their systems are fully operational. We are noticing the same on our end.

We have confirmation from our telecommunications partner that their systems are fully operational. We are noticing the same on our end.

This is a retroactive update for an incident that occurred on August 24, 2026. The issue was identified around 12pm PT.

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