Is Tebra Down?
- Tebra's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 823 ms
Right now
The verdict is the worse of these two. How we decide
Tebra's status page
status.tebra.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Platform | Operational |
| Clinical (EHR) | Operational |
| Billing (PM) | Operational |
| Practice Growth | Operational |
| Engage | Operational |
| Telehealth | Operational |
| Phone & IVR | Operational |
| Help Center | Operational |
FlareWarden checks
tebra.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 823 ms
- Checked
By region
- Amsterdam reachable, 984 ms
- Chicago reachable, 346 ms
- San Jose reachable, 255 ms
- Singapore reachable, 1127 ms
- Stockholm reachable, 1277 ms
- Sydney reachable, 1204 ms
- Tokyo reachable, 855 ms
- Toronto reachable, 538 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 45 ms | 2 ms | 15 ms | 717 ms |
| Chicago | 56 ms | 1 ms | 9 ms | 296 ms |
| San Jose | 69 ms | 2 ms | 10 ms | 232 ms |
| Singapore | 12 ms | 4 ms | 14 ms | 966 ms |
| Stockholm | 104 ms | 1 ms | 8 ms | 1097 ms |
| Sydney | 144 ms | 1 ms | 6 ms | 1044 ms |
| Tokyo | 129 ms | 1 ms | 13 ms | 761 ms |
| Toronto | 54 ms | 1 ms | 8 ms | 478 ms |
History
Incidents Tebra reported
Since Oct 22, 1 day · from status.tebra.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Tebra website availability
Measured by FlareWarden · tebra.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 920ms
Last 30 days
27-day clean streakMeasured by FlareWarden's own checks of tebra.com from multiple regions every 6 hours. Tebra's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 27 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
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.
Related services
Tebra outage FAQ
Is Tebra down for everyone or just me?
Does a TriZetto outage affect Tebra claims and ERAs?
Why is e-prescribing or e-labs not working in Tebra?
How do I get Tebra outage updates?
Does a Tebra outage affect the desktop PM application?
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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Tebra itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Tebra goes down
We check Tebra every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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