Skip to main content

Is Practice Fusion Down?

No — Practice Fusion is up

Reachable from all 8 checked regions

Average response time: 316ms

Last checked · checks run every 6 hours

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

Practice Fusion uptime

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

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

30-day history

70-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 23 checks
Sep 18: 100.00% uptime, 31 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 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, 32 checks
Sep 30: 100.00% uptime, 42 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.

dfw
189ms
DNS 175ms TCP 2ms TLS 3ms TTFB 187ms
ewr
182ms
DNS 165ms TCP 5ms TLS 4ms TTFB 180ms
fra
62ms
DNS 47ms TCP 1ms TLS 4ms TTFB 61ms
gru
869ms
DNS 404ms TCP 112ms TLS 116ms TTFB 769ms
iad
164ms
DNS 151ms TCP 1ms TLS 4ms TTFB 162ms
jnb
904ms
DNS 243ms TCP 161ms TLS 164ms TTFB 761ms
lax
102ms
DNS 88ms TCP 2ms TLS 4ms TTFB 100ms
lhr
58ms
DNS 42ms TCP 2ms TLS 5ms TTFB 55ms

What Practice Fusion does

Practice Fusion is a cloud electronic health record used by independent and small practices for charting, e-prescribing, scheduling and billing. Patients reach their own records through Patient Fusion, which the status page tracks as a separate component. Because the record lives entirely in the cloud, an outage stops clinical documentation at the point of care rather than merely inconveniencing back-office work.

What an outage looks like

Charts fail to open, or open and refuse to save an encounter note, which is the worst version because the visit continues while the record does not. E-prescribing fails at transmission to the pharmacy. The schedule does not load, so front desk staff cannot see who is arriving. Patient Fusion can fail independently, leaving patients unable to reach records while the practice-facing side works.

What to do about it

Check status.practicefusion.com, which reports Practice Fusion EHR and Patient Fusion PHR separately and publishes monthly uptime against a stated 99.90 percent goal. Fall back to paper for the visits in front of you and chart them afterwards rather than holding a day in memory. Support is reachable on (415) 346-7700 or toll free (844) 903-7567, Monday to Friday, 9 AM to 7:45 PM EST.

Is it down for everyone, or just you?

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

Okta
Okta
DocuSign
DocuSign
Zoom
Zoom
Salesforce
Salesforce

Practice Fusion outage FAQ

What should the practice do during an outage?
Switch to paper for the encounters happening now and back-enter them once the record returns. That sounds obvious and is routinely delayed by an hour of waiting for recovery, which is the hour that costs the most. Print or export the day's schedule at the start of each morning as standing practice, because the schedule is often the first thing you lose and the hardest to reconstruct mid-clinic.
Are patient records lost during an outage?
Saved records are not lost by an availability incident; reaching them is what fails. The exposure is documentation in progress: a note typed into a session that dropped before saving generally does not survive. Treat anything entered during a partial outage as unconfirmed and verify it after recovery, especially medication and allergy changes where a silently failed save has real clinical consequence.
Do e-prescriptions still reach the pharmacy?
Not while transmission is failing. A prescription that appears to send during an incident may not have reached the pharmacy, and assuming it did is the failure mode worth guarding against. Confirm receipt by phone for anything urgent rather than relying on the interface, and re-check the queue after recovery for prescriptions that are stuck rather than sent.
Is Patient Fusion down if the EHR is up?
It can be. The status page lists Practice Fusion EHR and Patient Fusion PHR as separate components, so patients can lose access to their own records while clinical staff work normally. If patients report they cannot reach records and the practice side is fine, that is the expected shape rather than a contradiction, and front desk staff can answer record requests directly in the meantime.
What uptime does Practice Fusion commit to?
The status page states a goal of 99.90 percent uptime, which it describes as 33 minutes of allowed downtime, and publishes actual monthly figures against it. For the first half of 2026 those were 99.96, 99.85, 99.96, 99.95, 99.97 and 100 percent from January to June. The measurement on this page is independent of that reporting and covers reachability from several regions.

How we measure this

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