Skip to main content
DrChrono logo

Is DrChrono Down?

No — DrChrono is up

Reachable from all 8 checked regions

Average response time: 316ms

Last checked · checks run every 6 hours

Official status page: https://status.drchrono.com

DrChrono uptime

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

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

30-day history

20-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: no data
Sep 23: no data
Sep 24: 100.00% uptime, 16 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, 31 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 29 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.

lax
178ms
DNS 82ms TCP 2ms TLS 8ms TTFB 173ms
lhr
208ms
DNS 34ms TCP 2ms TLS 13ms TTFB 197ms
nrt
616ms
DNS 429ms TCP 1ms TLS 7ms TTFB 606ms
ord
162ms
DNS 77ms TCP 1ms TLS 22ms TTFB 158ms
sin
496ms
DNS 239ms TCP 1ms TLS 7ms TTFB 491ms
sjc
113ms
DNS 14ms TCP 2ms TLS 10ms TTFB 106ms
syd
489ms
DNS 259ms TCP 1ms TLS 7ms TTFB 485ms
yyz
267ms
DNS 171ms TCP 2ms TLS 16ms TTFB 262ms

What DrChrono does

DrChrono, now branded DrChrono by EverHealth, is a cloud EHR for independent medical practices that puts scheduling, clinical notes, e-prescribing and medical billing in one system, with an iPad app, integrated telehealth and the OnPatient patient portal. It also sits between the practice and outside services: ID.me for controlled-substance prescribing, clearinghouses for claims, lab networks and fax.

What an outage looks like

The web application at drchrono.com loads slowly or throws errors, and recent incidents list the iPad EHR as affected at the same time. Past incidents also show narrower failures: appointment reminders not sending, billing reports not loading, patient search failing, and controlled-substance prescriptions blocked by ID.me authentication errors while the rest of the chart works. Faxes are delayed or fail when the Updox integration is disrupted.

What to do about it

Open status.drchrono.com and read both lists: DrChrono's own services, including the web app, iPad EHR, telehealth and onpatient.com, and the separate 3rd party services group, which shows ID.me, Updox, Waystar, Trizetto, Change Healthcare, Quest, Labcorp, Twilio SMS and others. If a partner row is red, the fix is on their side. Otherwise contact support through the EverHealth web form linked from support.drchrono.com.

Is it down for everyone, or just you?

If this page says DrChrono 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
SimplePractice
P
Practice Fusion
Doxy.me
Doxy.me
Twilio
Twilio

DrChrono outage FAQ

Why can't I send controlled-substance prescriptions in DrChrono?
Often the cause is ID.me rather than DrChrono. EPCS in DrChrono requires ID.me multi-factor authentication by push notification or code generator. In April 2026 an ID.me push-notification fault blocked controlled prescriptions for several days, and DrChrono's suggested workaround was switching the primary MFA device to a code generator under Account, Provider Settings, eRx Info.
Is it DrChrono or one of its partners?
Check the 3rd party services group on the status page. DrChrono lists its integrations as separate rows, including ID.me, Updox, Waystar, Trizetto, Change Healthcare, Quest Diagnostics, Labcorp, Health Gorilla, Stripe, Square and Twilio SMS. A red partner row with green DrChrono rows means the problem is limited to what that partner handles, such as faxing through Updox, and charting and scheduling should keep working.
Does the iPad app work when drchrono.com is down?
Do not count on it. The status page tracks the drchrono iPad EHR as its own component, and recent incidents covering slowness, intermittent errors and prescription problems listed the iPad EHR alongside drchrono.com. When the web application is affected, check the iPad EHR row before switching devices, and keep a paper schedule for the day's patients.
Is DrChrono down for everyone or just me?
Compare the status page with this page's checks from several regions. If both show DrChrono healthy, the likely causes are local: an expired session, a browser extension, the practice network or a single iPad. If our checks fail from several regions while the status page is still green, the vendor has probably not posted its incident yet.
Will appointment reminders go out during an outage?
Not reliably. DrChrono has posted incidents where reminders stopped sending for some customers, in May 2025 and again in May 2026, while the application otherwise worked. The status page also lists Twilio SMS among its partner services. If a reminder incident or a partner messaging problem is posted on a clinic day, call that day's patients directly to avoid no-shows.

How we measure this

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