PatientNow logo

Is PatientNow Down?

SaaSLive status, outages, and incident history

No. PatientNow is up right now.

Every monitored PatientNow system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 8m agoLive · every 60s

Know the moment PatientNow breaks

PatientNow is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

How we know: the official PatientNow status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

PatientNow Status Summary

As of 16:02 UTC on 14 November 2026, PatientNow is operational. PulsAPI checked PatientNow's official status page and found 7 of 7 components operational, with no active incidents. The latest incident, "Delayed Payment Status Updates for Terminal Transactions", was on Nov 11, 2026 and lasted 2h 28m.

Cite as: PulsAPI, “PatientNow status”, checked 14 November 2026, 16:02 UTC. https://www.pulsapi.com/services/patientnow

PatientNow Component Status

The main PatientNow systems on this page. All 7 are operational right now.

7operational
AestheticNOW
Operational
EnvisionNow
Operational
PatientNow Essentials
Operational

4 more components tracked

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

Also tracking PatientNow Pro, Recura, RxPhoto, VoIP.

See all of them free

Component statuses may change independently during partial outages.

Recent PatientNow Outages & Incidents

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

Delayed Payment Status Updates for Terminal TransactionsResolved Nov 11, 2026 · 2h 28mResolved

The fix has been fully deployed to our web services. Mastercard terminal transactions should now update invoices in PatientNow correctly. We are monitoring the system to confirm that everything is working as expected and will provide a final update once we have verified the results. If you notice an invoice that was not updated, please contact Support. --- [2026-11-11T21:56:56Z] (monitoring) The fix has been fully deployed to our web services. Mastercard terminal transactions should now update invoices in PatientNow correctly. We are monitoring the system to confirm that everything is working as expected and will provide a final update once we have verified the results. If you notice an invoice that was not updated, please contact Support. --- [2026-11-11T21:33:56Z] (identified) After analyzing the issue, we have developed a fix and are currently rolling it out to our web services. We do not expect any additional impact to the service during the deployment. We will provide another update once the rollout is complete and we have confirmed that Mastercard terminal transactions are updating invoices in PatientNow correctly. --- [2026-11-11T20:32:55Z] (identified) We have confirmed that this issue is limited to Mastercard transactions processed through payment terminals. Transactions made with other card brands are not affected and continue to update invoices in PatientNow as expected. --- [2026-11-11T20:13:45Z] (identified) We have identified the cause of the issue affecting invoice status updates for terminal card transactions. The payment terminal provider (triPOS) recently began returning a new type of transaction identifier for Mastercard transactions, in a format our system does not yet accept. As a result, payments are approved on the terminal, but the corresponding invoice in PatientNow is not updated. Card payments are being processed successfully, and no funds are at risk. Our engineering team is working on a fix and we will provide another update once it is deployed. --- [2026-11-11T20:09:37Z] (identified) We have identified the cause of the issue affecting invoice status updates for terminal card transactions. The payment terminal provider (triPOS) recently began returning a new type of transaction identifier for Mastercard transactions, in a format our system does not yet accept. As a result, payments are approved on the terminal, but the corresponding invoice in PatientNow is not updated. Card payments are being processed successfully, and no funds are at risk. Our engineering team is working on a fix and we will provide another update once it is deployed. After the fix, we will reconcile the affected invoices. --- [2026-11-11T19:31:16Z] (investigating) We are investigating an issue where invoices paid through a payment terminal are not updating to the correct status in PatientNow after the transaction is approved in Payrix. The payment is processed successfully on the Payrix side, but the corresponding invoice in PatientNow may continue to show the previous status. Our team is actively investigating, and we will provide an update as soon as we have more information.

Degraded performance – Payment processingResolved Nov 6, 2026 · 20 minResolved

This incident has been resolved. Our third-party payment processor, Payrix, has confirmed that the issue was fixed as of 10:31 AM MST on November 6, 2026, and payment processing has returned to normal. Between [start time] and 10:31 AM MST, some payments may have failed or been delayed. If you believe a transaction was affected, please retry it or contact our support team. We apologize for the inconvenience. --- [2026-11-06T17:29:24Z] (identified) We have identified that the issue is caused by a disruption at our third-party payment processor, Payrix. Our own systems are operating normally. We are in contact with the provider and tracking their progress toward a resolution. Some payments may continue to fail or be delayed in the meantime.

PNE clients unable to run any reports due to errorResolved Nov 4, 2026 · 17 minResolved

Issue is identified and resolved --- [2026-11-04T19:52:01Z] (investigating) PNE clients unable to run any reports due to error.

PatientNow Uptime History

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

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live PatientNow Outage Reports

Problems reported by engineers using PatientNow. 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 PatientNow problems reported yet.

Something wrong with PatientNow on your end?

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

About PatientNow

PatientNow posts its status at status.patientnow.com. The page covers 7 components, among them AestheticNOW, EnvisionNow and PatientNow Essentials. Past incidents and uptime for PatientNow stay on this page, which helps when you want to know how often it has trouble.

PatientNow Status FAQ

Is PatientNow down right now?

The verdict at the top of this page comes from the latest poll of the official PatientNow status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if PatientNow 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 PatientNow recovers.

How do I check PatientNow uptime history?

PulsAPI tracks PatientNow uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever PatientNow changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect PatientNow outages?

PulsAPI reads the official PatientNow status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual PatientNow components?

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

Can I get alerts when PatientNow goes down?

Yes. Create a free account and subscribe to PatientNow: 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 PatientNow 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 PatientNow problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor PatientNow?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so PatientNow 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 PatientNow with the rest of your stack

4372+ 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