DaySmart Appointments 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 DaySmart Appointments Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 24, 2026 | Investigating — Service InterruptionThis incident is now resolved. Our team confirmed the service is stable before closing out this incident. We apologize for the interruption and thank you for your patience throughout. | 36 min | Resolved |
| Aug 13, 2026 | Investigating — Service OutageThis issue is now fully resolved. The system is operating normally and access has been restored to all customer accounts. Our team has completed testing and confirmed everything is fully stable. We will be working… | 26h 23m | Resolved |
| Apr 8, 2026 | Account Access ReportsThis incident has been resolved. | 14h 19m | Resolved |
| Jan 27, 2026 | Intermittent System IssueThe issue has been resolved, and our systems are now functioning normally. If you continue to experience any issues, please let us know. Thank you. | 35 min | Resolved |
| Jan 9, 2026 | Service Provider is DownIntercom, the tool used to contact our support team and access the Appointments Help Center, has resolved the reported issues. Thank you for your patience during this time. | 46 min | Resolved |
| Nov 18, 2025 | Intermittent Software PerformanceResolved – The Cloudflare issue has been resolved and all systems are fully operational. | 2h 41m | 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 DaySmart Appointments 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 DaySmart Appointments 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 DaySmart Appointments 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 DaySmart Appointments outage in this window ran 1d 2h, against a mean recovery of 7h 33m. If you depend on DaySmart Appointments 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.