Solv Outage History
10 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Solv Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Manage Slowdown 10/27This incident has been resolved. | 19 min | Resolved |
| Oct 19, 2026 | Loading Delays in Solv ManageAs of 9:55 AM PST, Solv has released a fix and Manage load times have returned to normal. You should now find that all surfaces load without delay. We will continue to monitor performance. Thank you for your patience… | 56 min | Resolved |
| Sep 8, 2026 | Redox OutageEarlier today, Redox experienced an outage which impacted patient transfers to the EMR. As of 3:23 PM ET Redox applied a fix to resolve this issue and transfers are now processing as expected. We will continue to… | 8 min | Resolved |
| Sep 1, 2026 | 9/1 SMS Vendor Outage and Intermittent Slowness in Solv ManageAs of 1:48 PM ET the issue impacting performance of Solv Manage is resolved and performance is restored to baseline. | 19 min | Resolved |
| Aug 27, 2026 | Solv Manage PerformanceAn intermittent slowdown across the Solv Manage platform has since been resolved with a fix that was implemented at 10:55 AM ET. Impacted functionality was confirmed restored at 11:00 AM ET and has remained stable… | -2923 min | Resolved |
| Jul 10, 2026 | Solv Manage SlownessSolv’s engineering team has put measures in place to address system slowness and you should see Solv Manage operating at full speed. If you still observe slowness, please reach out. | 45 min | Resolved |
| Jul 6, 2026 | Solv Manage PerformanceSolv Manage is back up. Amazon Web Services has resolved the underlying issue behind this morning's slowdown. Our engineering team will keep a close eye on performance throughout the day. If you run into any trouble… | 2h 16m | Resolved |
| Feb 10, 2026 | External OutageEarlier today, Solv services were impacted by a widespread outage with our cloud provider, Amazon Web Services (AWS). This caused disruptions to EHR integrations, patient paperwork, and live chat. AWS has since restored… | 1h 37m | Resolved |
| Nov 28, 2025 | SMS Delays - VerizonVerizon has resolved their deliverability issues. You should expect messages to be delivered as normal. | 53h 49m | Resolved |
| Nov 18, 2025 | Cloudflare DisruptionFollowing Cloudflare’s service restoration and our mitigation steps, we are seeing sustained improvement across all booking, registration, and queue surfaces. Single Sign-On (SSO) access has been restored and is… | 6h 43m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Solv incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Solv Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Solv acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Solv outage in this window ran 2d 5h, against a mean recovery of 7h 26m. If you depend on Solv in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.