TimeTap Outage History
8 incidents recorded over the last 365 days, 8 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 TimeTap Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 22, 2026 | Booking Sites Not LoadingA solution has been put in place to resolve intermittent error loading messages on client side schedulers. | 54 min | Resolved |
| May 13, 2026 | External Calendar Syncs Not Receiving New or Updated Appointments from TimeTapSync backlog has cleared. | 23h 14m | Resolved |
| May 12, 2026 | Slow Loading Times in Back Office and Client SchedulerSlow loading times experienced on both the Back Office and Client Scheduler have been resolved. | 34 min | Resolved |
| May 7, 2026 | Resolved: Email Delivery Outage (12:55 PM – 1:26 PM ET)Between approximately 12:55 PM and 1:26 PM ET on May 7, 2026, email were not being delivered as expected and returned the following status error in messaging logs: “Failed - Request does not contain a valid Server… | 0 min | Resolved |
| Mar 24, 2026 | Gateway Time Out On Back Office and Client Side SchedulerThis incident has been resolved. | 2h 17m | Resolved |
| Feb 5, 2026 | Invoice Creation and Closure IssueA fix has been deployed and tested. | 28 min | Resolved |
| Dec 17, 2025 | Office 365 With Teams Calendar Sync DelayOffice 356 with Team Calendar syncing is up to date and there is no longer a delay. | 40h 3m | Resolved |
| Nov 18, 2025 | Cloudflare OutageCloudflare has resolved their outage and TimeTap is operational at this time. | 41 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 TimeTap 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 TimeTap 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 TimeTap 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 TimeTap outage in this window ran 1d 16h, against a mean recovery of 8h 31m. If you depend on TimeTap 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.