SimplePractice incident

Site wide connectivity Issues

Major Resolved View vendor source →

SimplePractice experienced a major incident on December 17, 2025 affecting Main application, lasting 4h 5m. The incident has been resolved; the full update timeline is below.

Started
Dec 17, 2025, 03:04 PM UTC
Resolved
Dec 17, 2025, 07:09 PM UTC
Duration
4h 5m
Detected by Pingoru
Dec 17, 2025, 03:04 PM UTC

Affected components

Main application

Update timeline

  1. investigating Dec 17, 2025, 03:04 PM UTC

    We are currently experiencing a limited feature interruption related to our Client Portal, so clients may not be able to sign into their Client Portal. We are actively working to resolve this issue as quickly as possible. More updates to follow shortly.

  2. monitoring Dec 17, 2025, 03:36 PM UTC

    A fix has been implemented for this, and the Client Portal should now be accessible to any clients. We'll be monitoring this further and provide further updates shortly.

  3. monitoring Dec 17, 2025, 04:03 PM UTC

    We are still continuing to monitor this, and will be providing further updates as we have them.

  4. investigating Dec 17, 2025, 04:47 PM UTC

    The fix implemented earlier did not resolve the issue, and we are now continuing to investigate this further. We will keep communicating updates as we have them.

  5. investigating Dec 17, 2025, 05:10 PM UTC

    We have now taken note of connectivity issues across different areas of the platform including but not limited to: - Stripe Payment Processing - Professional Website - Connections to Telehealth sessions We are actively investigating these issues, and will provide further updates as we have them.

  6. identified Dec 17, 2025, 05:53 PM UTC

    We have identified the cause of the issues, and are now working on a fix. We will continue to provide updates as we have them.

  7. monitoring Dec 17, 2025, 06:39 PM UTC

    We have implemented a fix for this, and are now monitoring this further. We'll be providing additional updates as we have them.

  8. resolved Dec 17, 2025, 07:09 PM UTC

    This incident has been resolved.