Athenahealth Running Slow? Start With These Five Checks Before You Call the Vendor.
Five things to check before you open a ticket with the vendor, in the order most likely to find the cause. All five can be done by the office without waiting on anyone.
Your practice manager is standing at the front desk watching a patient check-in screen spin for 30 seconds. Your billing staff is refreshing orders that won't load. By the time athenahealth finally responds, you've lost three minutes per patient, and that's just one workstation on one afternoon. Over a week, those minutes add up to hours of lost productivity and frustrated staff.
Most of the time, when a practice calls athenahealth to report the EHR is down or running slow, the problem is not athenahealth. It's the office network, the ISP, a single workstation, or browser cache that hasn't been cleared in months. Running five quick checks before you open a vendor ticket saves you the wait time for support to tell you the same thing, and gets your staff back to work faster.
Check 1: Is athenahealth itself having a bad day?
Start here. Navigate to status.athenahealth.com, the official athenahealth Trust and Status Center, to get a real-time, module-by-module view of the platform's health. Look for any module showing yellow (degraded performance) or red (down). If athenahealth is reporting issues on its end, take a screenshot and note the time. That screenshot becomes part of your ticket later. If the status page shows green across the board, the slowness is on your side.
Check 2: Does your office internet meet the bar?
athenahealth publishes specific network requirements: 1 Mbps up and down per user for athenaOne traffic and a 120 ms round-trip time. In practice, many offices run a speed test and aim for at least 10 Mbps per active user as a safety margin.
Open a browser and run a free speed test (speedtest.net or fast.com both work). Note your download speed, upload speed, and ping time. Compare those numbers to athenahealth's published requirements. If you're below 1 Mbps up or down, or your ping is above 120 ms, your internet connection is the bottleneck, not athenahealth.
Check 3: Is it your ISP or your router?
The fastest way to tell whether the problem is your internet provider or your office network is to test athenaNet on a mobile hotspot. Pull out a phone, turn on its hotspot, connect a workstation to it, and try logging into athenahealth. If the EHR loads normally over cellular, your ISP or office router is the bottleneck. If it's still slow on the hotspot, the problem is athenahealth's infrastructure or your workstation itself.
Check 4: Is it every workstation or just one?
The pattern of slowness tells you where to focus next:
- Slow on all workstations, Internet or network issue. Call your ISP or check your router.
- Slow on one workstation, That specific computer has a problem. Move to Check 5.
- Slow only at certain times of day, Bandwidth congestion during peak hours, or background processes running on that workstation.
Check 5: The local fixes that clear most "spinning" screens
If you've narrowed it down to a single workstation or a pattern that points to that computer, try these:
- Clear the browser cache and cookies in Chrome or Edge. Stale cached data is the most common cause of spinning screens and timed-out sessions in athenaNet. Restart the browser after clearing.
- Restart the workstation. Close everything, shut down, wait 30 seconds, and power back on. This clears temporary files and resets network connections.
- Check for operating system and browser updates. An outdated OS or browser can drag athenahealth down.
- Close unnecessary programs. Too many programs running at once consume RAM and slow the system. Close email, Slack, video calls, and anything else not needed for the EHR.
- Confirm the hard drive isn't nearly full. A hard drive at 90% capacity slows everything down. Check how much free space is left.
- Verify the workstation has adequate RAM. Older computers with 4 GB or less of RAM struggle with athenahealth. If you're not sure, check Device Manager (Windows) or System Report (Mac).
When to actually open the ticket, and what to have ready
If self-service fixes don't resolve the issue after 2–3 days, if multiple users are seeing the same problem, or if error messages appear, it's time to contact athenahealth support.
Before you call, gather this information:
- Screenshot of the speed test (download, upload, ping).
- Screenshot of the status.athenahealth.com page at the time the slowness occurred.
- List of which workstations are affected.
- Whether the slowness happens during peak hours or all day.
- How much time staff are losing to waiting on screens to load or orders to process.
Write down a specific description of what's happening: "Orders won't load on the billing workstation after 2 p.m." is better than "athenahealth is slow." The more specific you are, the faster support can help.
For practices without a dedicated IT person
If your practice doesn't have an in-house network engineer, these five checks can be hard to run under pressure. A local IT partner can come on-site, run the speed test and hotspot check, audit your office network against athenahealth's published bandwidth and latency requirements, and gather the diagnostic screenshots before opening the vendor ticket. That way, when you call athenahealth, you already have the evidence in hand, and you know whether the problem is on their side or yours.
If athenahealth is still slow after these five checks, send us the speed-test screenshot, the status page screenshot, and the list of affected workstations, we will come on-site, isolate the cause, and open the vendor ticket with the evidence already attached.
