TimelyCare Outage History
6 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded TimelyCare Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Mar 9, 2026 | Members may not be able to access app.timelycare.comThis incident has been resolved. | 7 min | Resolved |
| Feb 23, 2026 | Members might not be able to retrieve messagesMembers may get an error when going to their 'messages' page. Messages may appear on subsequent reloads. We are investigating the issue | -171361 min | Resolved |
| Feb 23, 2026 | Increased error rate in all applicationsAmazon web services is reporting increases in error rates in the region which hosts timelycare infrastructure. Users of timelycare web applications may experience intermittent errors which clear on a reload. We… | -725787 min | Resolved |
| Feb 23, 2026 | Some new user accounts could not be createdSome new users are unable to create new accounts. We are investigating the issue. | -1259549 min | Resolved |
| Feb 23, 2026 | Elevated error rate in web and mobile applicationsA vendor message broker service used in our application for client synchronization began returning errors intermittently from its api. Users of TimelyCare and TimelyProvider saw intermittent errors in their browser but… | -1547913 min | Resolved |
| Feb 23, 2026 | Users unable to loginUsers are receiving errors when attempting to log in to TimelyProvider and TimelyCare. This was due to a Cloud Service Provider having a data center outage. | -1880738 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next TimelyCare incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This TimelyCare Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before TimelyCare acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single TimelyCare outage in this window ran 7 min, against a mean recovery of 7 min. If you depend on TimelyCare in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.