DaySmart Appointments logo

Is DaySmart Appointments Down?

SaaSLive status, outages, and incident history

No. DaySmart Appointments is up right now.

Every monitored DaySmart Appointments system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 7m agoLive · 60s while moving

Know the moment DaySmart Appointments breaks

DaySmart Appointments is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official DaySmart Appointments status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

DaySmart Appointments Component Status

The main DaySmart Appointments systems on this page. All 4 are operational right now.

4operational
Customer View
Operational
Sandbox
Operational
Site Admin
Operational

1 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Web Services.

See all of them free

Component statuses may change independently during partial outages.

Recent DaySmart Appointments Outages & Incidents

Incident history from the official DaySmart Appointments status page, including resolution updates.

Investigating — Service InterruptionResolved Sep 24, 2026 · 36 minResolved

This 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. --- [2026-09-24T12:07:46.045-07:00] (monitoring) We're seeing accounts come back online. Before we mark this as resolved, our team is verifying that everything is fully restored and working as expected. We'll post another update once we've confirmed the service is stable. Thank you for your continued patience. --- [2026-09-24T11:55:27.864-07:00] (investigating) We're currently experiencing an outage. Our team is actively investigating the cause. We apologize for the disruption and appreciate your patience.

Investigating — Service OutageResolved Aug 13, 2026 · 26h 23mResolved

This 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 internally and with our hosting providers (PhoenixNAP) to understand root cause and remediation. We sincerely apologize for the disruption and the impact it had on your business today, which we truly appreciate. Thank you for your patience and understanding throughout the incident. If you experience any further issues or have any questions, please reach out to our support team and we'll be glad to help. --- [2026-08-14T07:14:17.460-07:00] (monitoring) The system is running as expected, and access has been restored to customer accounts. Our team is now completing final testing and monitoring to confirm everything is fully stable. Final confirmation will be provided once that work is complete. Thank you for your continued patience, and we apologize for the impact this has had on your business. --- [2026-08-14T01:28:06.479-07:00] (monitoring) We're continuing to make progress toward fully restoring service. The team has now shifted into testing and exploratory work to confirm an all clear. Account access is available to customers at this stage, and you may now be able to log in and access your account as we complete this final testing. Updates will be provided as soon as service is fully restored. Thank you for your continued patience, and we apologize for the impact this has had on your business. --- [2026-08-13T22:55:43.609-07:00] (monitoring) We're continuing to make progress to fully restore service. The team is in final phases of restoring all databases (anticipated in 1-2 hours), at which point they will shift to testing and exploratory work to determine an all clear.  Some customers may be able to access their accounts at this time as the team continues to make progress. Given this progress, the team has abandoned further work on the Disaster Recovery Plan path and fully focused on restoring the PhoenixNap environment. We'll confirm here as soon as the service is fully restored. Thank you for your continued patience and we apologize for the impact this has had on your business. --- [2026-08-13T19:28:35.166-07:00] (identified) As of 19:03 MT, our provider (PhoenixNAP) has confirmed that services at their Phoenix data center are back online following today's cooling issue. Our team is now completing the work to bring our systems fully back up, and we'll confirm here as soon as service is fully restored on our end. Your data remains secure. Thank you for your continued patience throughout today's disruption. --- [2026-08-13T16:48:00.832-07:00] (identified) Temperatures have stabilized to a level that allows us to begin powering the equipment back up. We remain in continuous contact with PhoenixNAP and consider restoring the existing infrastructure to be the fastest path to recovery. Our disaster recovery plan continues to run in parallel as a contingency, and your data remains secure. We will provide a further update as soon as more information becomes available. We sincerely appreciate your patience and understanding. --- [2026-08-13T15:32:48.990-07:00] (identified) PhoenixNAP continues to stabilize temperatures where our equipment is located. We continue to be in continuous contact with PhoenixNAP and believe bringing up the existing infrastructure is the fastest path to recovery. At the same time, we continue to work on our Disaster Recovery Plan as an alternate environment in case the issue with PhoenixNAP does not improve. --- [2026-08-13T14:29:17.072-07:00] (identified) Recovery efforts are continuing to progress with our provider (PhoenixNAP). Our disaster recovery plan remains active in parallel, and your data remains secure. We will share a further update as soon as more information becomes available. We sincerely appreciate your patience and understanding. --- [2026-08-13T13:19:47.494-07:00] (identified) Our provider (PhoenixNAP) continues to work toward restoring service as 3 chillers are now back online and temperatures continue to come down to a workable level. Our disaster recovery plan also remains active in parallel, and your data remains secure. We will provide a further update as soon as more information becomes available. We sincerely appreciate your patience and understanding. --- [2026-08-13T11:59:02.862-07:00] (identified) Recovery is continuing to progress. Our provider (Phoenix NAP) is adding temporary cooling and heat-removal equipment now, with additional cooling and backup power planned through the afternoon. 2 of 4 chillers in the data center are online and a 3rd is coming online within the hour. Temperatures are dropping and pacing towards the vendor's recovery time of 2pm PDT. Our disaster recovery plan continues to run in parallel, and your data remains secure. We'll keep posting updates here. Thank you for your continued patience. --- [2026-08-13T10:32:46.869-07:00] (identified) Our provider (PhoenixNAP) has on-site teams restoring cooling and reports good progress — one chiller is back online and temperatures are already falling, with further cooling and heat removal equipment and additional chillers being brought online through the afternoon. Our disaster recovery plan is also running in parallel, and your data remains secure. We'll keep posting updates here as the situation progresses. We sincerely apologize for the disruption. --- [2026-08-13T09:41:58.533-07:00] (identified) We wanted to update you on the current outage — our Phoenix data center experienced a chiller failure this morning that took the entire facility offline. Our hosting service provider believes they’ve identified the issue and expects remediation within 6 hours; in parallel, we’ve initiated our disaster recovery plan to utilize data backups (a process that will take 6–8 hours). We sincerely apologize for the disruption and are working to resolve this as quickly as possible. --- [2026-08-13T08:36:47.158-07:00] (identified) Our infrastructure provider is still working to restore service, and our team remains in direct contact with them, pushing for updates and a resolution timeline. We understand the impact this disruption is having on your operations, and we sincerely apologize for the inconvenience. Please know that resolving this remains our top priority, and we are committed to keeping you informed. --- [2026-08-13T07:38:32.888-07:00] (identified) Our infrastructure provider has identified the cause and is working to restore service. We're monitoring closely and will post updates as we have them. Thank you for your patience. --- [2026-08-13T06:35:57.366-07:00] (identified) This outage is not caused by an issue within our own platform. Our infrastructure provider is experiencing an outage that is affecting the services we rely on to keep our system running. Our team is in active contact with them and is monitoring the situation closely. We apologize for the inconvenience and interruption of your services. --- [2026-08-13T05:58:10.208-07:00] (investigating) We are currently experiencing system issues. Our team is aware and actively investigating to identify the cause. We apologize for any inconvenience and will provide an update shortly.

DaySmart Appointments Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a DaySmart Appointments incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 898.48% average · 2 days with incidentsSep 25

Live DaySmart Appointments Outage Reports

Problems reported by engineers using DaySmart Appointments. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No DaySmart Appointments problems reported yet.

Something wrong with DaySmart Appointments on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About DaySmart Appointments

DaySmart Appointments exposes 4 monitored components on its status page at status.appointment-plus.com — Web Services, Site Admin and Customer View among them. Follow DaySmart Appointments downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured DaySmart Appointments uptime at 100.00%. Response times, incident history, and SLA tracking for DaySmart Appointments are available on the PulsAPI dashboard.

DaySmart Appointments Status FAQ

Is DaySmart Appointments down right now?

The verdict at the top of this page comes from the latest poll of the official DaySmart Appointments status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if DaySmart Appointments is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until DaySmart Appointments recovers.

How do I check DaySmart Appointments uptime history?

PulsAPI tracks DaySmart Appointments uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever DaySmart Appointments changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect DaySmart Appointments outages?

PulsAPI reads the official DaySmart Appointments status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual DaySmart Appointments components?

Yes. PulsAPI monitors 4 individual DaySmart Appointments components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when DaySmart Appointments goes down?

Yes. Create a free account and subscribe to DaySmart Appointments: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with DaySmart Appointments to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot DaySmart Appointments problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor DaySmart Appointments?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so DaySmart Appointments plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track DaySmart Appointments with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services