Petal Health logo

Is Petal Health Down?

SaaSLive status, outages, and incident history

No. Petal Health is up right now.

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

OperationalChecked 4m agoLive · every 60s

Know the moment Petal Health breaks

Petal Health 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 Petal Health status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Petal Health Status Summary

As of 17:02 UTC on 14 November 2026, Petal Health is operational. PulsAPI checked Petal Health's official status page and found 20 of 20 components operational, with no active incidents. The latest incident, "Latency and errors in Hub", was on Oct 28, 2026 and lasted 1 min.

Cite as: PulsAPI, “Petal Health status”, checked 14 November 2026, 17:02 UTC. https://www.pulsapi.com/services/petal-health

Petal Health Component Status

The main Petal Health systems on this page. All 20 are operational right now.

20operational
Data Hub » Data Insights Offerings
Operational
Data Hub » Data refresh
Operational
Petal Medical Billing » Claims Management
Operational

17 more components tracked

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

Also tracking Petal Medical Billing » Data Collection & Classification, Petal Medical Billing » Medical Coding, Petal Patient » Care Orchestration Hub, Petal Patient » Patient Portal, Petal Patient » Provider Availability Management, Petal Workforce » Communication Center, Petal Workforce » Communications and Collaboration, Petal Workforce » Console, Petal Workforce » Mobile, Petal Workforce » Provider Scheduling, Petal Workforce » Secure Messaging, Platform » Connectors, and 5 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Petal Health Outages & Incidents

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

Latency and errors in HubResolved Oct 28, 2026 · 1 minResolved

This incident has been resolved. --- [2026-10-28T16:44:08.671-04:00] (monitoring) Mise à jour : Un contournement a été appliqué et les services de la plateforme PetalMD sont de nouveau opérationnels. Nos équipes poursuivent la surveillance de la situation afin de confirmer la stabilité des services. La cause exacte du problème reste à déterminer et fera l'objet d'une analyse approfondie. --- Update: A workaround has been applied and PetalMD platform services are operational again. Our teams continue to monitor the situation to confirm stability. The exact cause of the issue is still being determined and will be reviewed further. --- [2026-10-28T15:12:04.877-04:00] (investigating) Nous enquêtons actuellement sur un problème récurrent de résolution DNS affectant nos serveurs de production, similaire à l'incident de ce matin. Cela entraîne une latence accrue sur le Hub et pourrait affecter certains services. Nos équipes investiguent activement et nous vous tiendrons informés de l'évolution de la situation. --- We are currently investigating a recurrence of this morning's DNS resolution issue affecting our production servers. This is causing increased latency on the Hub and may affect some services. Our teams are actively investigating and we will keep you updated as the situation evolves.

Network issues and disruptionResolved Oct 28, 2026 · 57 minResolved

Mise à jour : Les erreurs et la latence sont revenues à la normale sur l'ensemble de la plateforme. Nos équipes continuent de surveiller la situation de près et poursuivent leur investigation afin de confirmer la cause du problème. Nous vous tiendrons informés si la situation évolue. --- Update: Errors and latency have returned to normal across the platform. Our teams continue to monitor the situation closely and are continuing the investigation to confirm the root cause. We will keep you informed if the situation changes. --- [2026-10-28T09:50:40.238-04:00] (monitoring) Mise à jour : Les erreurs et la latence sont revenues à la normale sur l'ensemble de nos services. Nos équipes continuent de surveiller la situation de près afin de confirmer le rétablissement complet. Nous vous tiendrons informés si la situation évolue. --- Update: Errors and latency have returned to normal across all of our services. Our teams continue to monitor the situation closely to confirm full recovery. We will keep you informed if anything changes. --- [2026-10-28T09:51:17.159-04:00] (monitoring) Mise à jour : Les erreurs et la latence sont revenues à la normale sur l'ensemble de nos services. Nos équipes continuent de surveiller la situation de près afin de confirmer le rétablissement complet. Nous vous tiendrons informés si la situation évolue. Update: Errors and latency have returned to normal across all of our services. Our teams continue to monitor the situation closely to confirm full recovery. We will keep you informed if anything changes. --- [2026-10-28T09:36:53.820-04:00] (investigating) Nous rencontrons actuellement un problème de réseau affectant l'ensemble de notre plateforme. Certains utilisateurs peuvent rencontrer des erreurs ou une lenteur lors de l'utilisation de nos services. Nos équipes sont mobilisées pour identifier la cause et rétablir le fonctionnement normal. Nous vous tiendrons informés dès que nous aurons de nouvelles mises à jour. --- We are currently experiencing a network issue affecting our entire platform. Some users may see errors or slowness while using our services. Our teams are actively working to identify the cause and restore normal operation. We will share further updates as soon as we have more information. --- [2026-10-28T09:17:30.888-04:00] (investigating) We are continuing to investigate this issue. --- [2026-10-28T09:07:18.766-04:00] (investigating) We are continuing to investigate this issue. --- [2026-10-28T09:05:09.212-04:00] (investigating) We are continuing to investigate this issue. --- [2026-10-28T09:03:56.985-04:00] (investigating) Nous sommes en train d'enquêter sur une perturbation réseau susceptible d'affecter certaines fonctionnalités de l'ensemble des produits Petal. Nous vous tiendrons informés dès que possible. --- We're investigating a network disruption that may affect functionality across Petal products. We will share more information as it becomes available.

Hub errorsResolved Oct 15, 2026 · 27 minResolved

Une alerte de charge a été déclenchée ce matin sur un composant de traitement en arrière-plan. Après investigation, aucun impact sur les clients ou sur les fonctionnalités du produit n'a été identifié — la prise de rendez-vous et les autres fonctionnalités sont demeurées disponibles tout au long de l'événement. Une commande corrective a été appliquée et la situation est revenue à la normale. Nous considérons cet événement résolu. --- A load alert was triggered this morning on a background processing component. Following investigation, no customer or product functionality impact was identified — appointment booking and other features remained available throughout the event. A corrective action was applied and the situation has returned to normal. We consider this event resolved. --- [2026-10-15T09:23:17.724-04:00] (monitoring) Un correctif a été appliqué pour résoudre un problème d'indexation Elasticsearch ayant causé des erreurs intermittentes sur la prise de rendez-vous (y compris le Hub Québec), l'admin et la planification. Les erreurs ont cessé et nous continuons de surveiller la situation de près. --- A fix was applied to address an Elasticsearch indexing issue that caused intermittent errors on appointment booking (including the Québec hub), admin, and scheduling. Errors have stopped and we continue to closely monitor the situation. --- [2026-10-15T09:09:11.207-04:00] (identified) Nous avons identifié des erreurs intermittentes affectant la prise de rendez-vous sur le Hub (y compris au Québec), ainsi que les fonctionnalités d'administration et de planification. Les erreurs ont diminué depuis et la situation semble se résorber. Nous continuons la surveillance. --- We identified intermittent errors affecting appointment booking on the Hub (including Quebec), as well as admin and scheduling features. Errors have since decreased and the issue appears to be resolving. We're continuing to monitor.

Petal Health Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Petal Health 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 Petal Health Outage Reports

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

Something wrong with Petal Health on your end?

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

About Petal Health

Petal Health's status page at status.petal-health.com lists 20 components, such as Data Insights Offerings, Data refresh and Claims Management. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Petal Health's side or yours.

Petal Health Status FAQ

Is Petal Health down right now?

The verdict at the top of this page comes from the latest poll of the official Petal Health 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 Petal Health 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 Petal Health recovers.

How do I check Petal Health uptime history?

PulsAPI tracks Petal Health 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 Petal Health changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Petal Health outages?

PulsAPI reads the official Petal Health 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 Petal Health components?

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

Can I get alerts when Petal Health goes down?

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

Is there a free way to monitor Petal Health?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Petal Health 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 Petal Health 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