Skip to main content
Tebra logo

Is Tebra Down?

No — Tebra is up

Reachable from all 8 checked regions

Average response time: 862ms

Last checked · checks run every 6 hours

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

Tebra uptime

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

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

30-day history

14-day clean streak
Sep 10: no data
Sep 11: no data
Sep 12: no data
Sep 13: no data
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: no data
Sep 25: no data
Sep 26: 100.00% uptime, 16 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, 30 checks
Oct 1: 100.00% uptime, 32 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
Sep 10 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.

ams
1033ms
DNS 82ms TCP 2ms TLS 12ms TTFB 897ms
arn
1275ms
DNS 100ms TCP 1ms TLS 8ms TTFB 1096ms
nrt
801ms
DNS 117ms TCP 1ms TLS 12ms TTFB 705ms
ord
349ms
DNS 28ms TCP 2ms TLS 10ms TTFB 278ms
sin
1159ms
DNS 78ms TCP 1ms TLS 8ms TTFB 996ms
sjc
266ms
DNS 84ms TCP 2ms TLS 10ms TTFB 246ms
syd
1199ms
DNS 146ms TCP 1ms TLS 6ms TTFB 882ms
yyz
815ms
DNS 92ms TCP 1ms TLS 7ms TTFB 802ms

What Tebra does

Tebra is a cloud EHR and practice management platform for independent medical practices, formed in 2021 when Kareo and PatientPop merged and based in Newport Beach, California. Practices use it for clinical notes and e-prescribing, scheduling, insurance claims and patient payments, plus reminders, practice websites and review management. It has a web platform, a mobile app and a separate desktop application (PM) for billing.

What an outage looks like

Sign-in fails with Login Failed. Check your information and try again, or the web app is slow, logs users out or shows modules only partly loaded. Clinical notes, medications, the calendar or Message Center may fail to open while the rest works. Vendor faults look different: e-prescriptions that will not complete, e-lab orders that error, ERAs that arrive late, or Code Check calling valid codes invalid or expired.

What to do about it

Check status.tebra.com, which splits Platform, Clinical (EHR), Billing (PM), Practice Growth, Engage, Telehealth, Phone & IVR and Help Center. During clearinghouse delays Tebra has told practices their claims were submitted and not to resubmit them. When the Code Check vendor failed, users could bypass the warning and approve the encounter. Customer Care is (866) 93-TEBRA, weekdays 5 AM to 4 PM Pacific.

Is it down for everyone, or just you?

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

DrChrono
DrChrono
P
Practice Fusion
SimplePractice
SimplePractice
Doxy.me
Doxy.me

Tebra outage FAQ

Is Tebra down for everyone or just me?
Check which component status.tebra.com marks, since most Tebra incidents hit one area rather than everything. The page lists Platform, Clinical (EHR), Billing (PM), Practice Growth, Engage, Telehealth, Phone & IVR and Help Center separately. If all are green and only your login fails, ask your practice's System Administrator to confirm your user account is active before calling Customer Care.
Does a TriZetto outage affect Tebra claims and ERAs?
Yes, TriZetto is Tebra's clearinghouse partner, and its problems show up as Billing (PM) incidents. In July 2026 a TriZetto issue delayed ERAs to Tebra for several days, and in August 2025 claim status reports backed up. During that backlog Tebra said claims had been submitted successfully and asked practices not to resubmit them, so check the status page before sending claims again.
Why is e-prescribing or e-labs not working in Tebra?
It is often an outage at a Tebra vendor rather than Tebra itself. The status page has blamed its EPCS vendor for failed eRx orders during the October 2025 AWS outage, and its e-labs vendor Ellkay for an error page on new lab orders in August 2025. These appear under Clinical (EHR), so the rest of the chart can work normally while prescriptions or orders fail.
How do I get Tebra outage updates?
Subscribe on status.tebra.com, which Tebra's help center calls its Status Blog for scheduled maintenance and current issues, using its Subscribe to Updates button. For a problem not listed there, call Customer Care at (866) 93-TEBRA (83272), Monday to Friday 5 AM to 4 PM Pacific. Customer Care is closed on weekends, so a weekend outage is best followed on the status page itself.
Does a Tebra outage affect the desktop PM application?
It can. Tebra runs a web platform and a separate desktop application for practice management (PM), and several incidents have hit both, such as a July 2026 login failure affecting the web app and PM app and a January 2026 issue reaching the PM and web app. Billing (PM) is its own row on the status page, so check it alongside Platform.

How we measure this

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