Skip to main content
SimplePractice logo

Is SimplePractice Down?

No — SimplePractice is up

Reachable from all 8 checked regions

Average response time: 841ms

Last checked · checks run every 6 hours

Official status page: https://www.simplepracticestatus.com

SimplePractice uptime

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

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

30-day history

22-day clean streak
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: 100.00% uptime, 16 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 31 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: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 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.

gru
1016ms
DNS 290ms TCP 2ms TLS 9ms TTFB 664ms
iad
460ms
DNS 110ms TCP 2ms TLS 9ms TTFB 402ms
jnb
1667ms
DNS 407ms TCP 0ms TLS 77ms TTFB 986ms
lax
496ms
DNS 133ms TCP 1ms TLS 24ms TTFB 472ms
lhr
777ms
DNS 256ms TCP 2ms TLS 12ms TTFB 617ms
nrt
926ms
DNS 386ms TCP 1ms TLS 12ms TTFB 917ms
ord
403ms
DNS 32ms TCP 1ms TLS 22ms TTFB 358ms
sin
984ms
DNS 329ms TCP 1ms TLS 8ms TTFB 762ms

What SimplePractice does

SimplePractice is electronic health record and practice management software for therapists and other health and wellness professionals. Clinicians use it to schedule clients, write notes, run telehealth sessions, send reminders, take online payments and submit insurance claims, and clients use its portal to book and pay. For a solo practice it is often the whole back office, so an outage reaches clients directly.

What an outage looks like

The main application will not load, so clinicians cannot open the calendar or client notes before a session. Telehealth sessions fail to start or drop, and clients waiting for their video link see nothing. Appointment reminders by email or text may not send, online card payments fail, and insurance claims or eligibility checks return errors while the rest of the application keeps working.

What to do about it

Check simplepracticestatus.com, which lists the Main application, Telehealth Service, Online Payments Service, Email Service, SMS Service, Document Storage Service and Insurance Processing separately. If telehealth is down, phone the day's clients and reschedule, or move the session to another video platform your practice already uses for clinical work. If only insurance processing is affected, wait and submit claims later rather than filing them twice.

Is it down for everyone, or just you?

If this page says SimplePractice 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

SimplePractice outage FAQ

What should I do if a telehealth session will not start?
Check the Telehealth Service row on the status page first. If it shows an incident, call the client, explain, and either reschedule or move to another video platform your practice already uses for sessions. If the row is green and only one client cannot join, the cause is more likely their browser, their camera permissions or their connection.
Is SimplePractice down or is it the insurance clearinghouse?
Look at the Insurance group. SimplePractice reports Insurance Processing separately, with its own rows for Availity and Eligible, so claims and eligibility checks can fail because of one of those partners while scheduling, notes and telehealth work normally. In that case the delay is in claim submission, and nothing in the client record needs to be entered again.
Will clients still get their appointment reminders?
Not if the messaging rows are affected. The status page lists the Email Service and SMS Service separately from the main application, so reminders can stop while the calendar itself looks normal. If either row shows an incident near appointment time, contact the day's clients another way so a missing reminder does not turn into a no-show.
Is SimplePractice down for everyone or just me?
Compare the status page with this page's measurements from several regions. If both show SimplePractice healthy, the likely causes are local: a stale browser session, an extension blocking scripts, or your own network. Failures seen from several regions at once point to SimplePractice itself.

How we measure this

  • We request SimplePractice'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 SimplePractice 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 SimplePractice 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