PetDesk Outage History

PetDesk is up right now

PetDesk had 11 outages in the last 2 years totaling 153h 41m of downtime — averaging 0.5 incidents per month.

There were 11 PetDesk outages since December 2, 2024 totaling 153h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.petdesk.com

Major June 10, 2026

PetDesk Dashboard

Detected by Pingoru
Jun 10, 2026, 01:20 PM UTC
Resolved
Jun 10, 2026, 03:01 PM UTC
Duration
1h 41m
Affected: Provider Communications Dashboard
Timeline · 7 updates
  1. investigating Jun 10, 2026, 01:20 PM UTC

    We are currently investigating and issue effecting Dashboard.

  2. investigating Jun 10, 2026, 01:28 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 10, 2026, 01:34 PM UTC

    The issue has been identified and a fix is in progress.

  4. investigating Jun 10, 2026, 01:42 PM UTC

    We have failed over and have been seeing recovery for the last 10 minutes or so. Expect some lingering latency as everything settles. We continue to monitor.

  5. monitoring Jun 10, 2026, 01:43 PM UTC

    The fix has been implemented and all services have been restored. We will continue to monitor performance.

  6. monitoring Jun 10, 2026, 02:30 PM UTC

    We're continuing to see degraded performance in our monitoring. Our team is working to restore services to full performance.

  7. resolved Jun 10, 2026, 03:01 PM UTC

    The incident has been resolved and all systems are back to normal performance.

Read the full incident report →

Major May 26, 2026

Dashboard Performance and Availability

Detected by Pingoru
May 26, 2026, 02:58 PM UTC
Resolved
May 26, 2026, 03:27 PM UTC
Duration
29m
Affected: PetDesk Communications Dashboard LoginProvider Communications Dashboard
Timeline · 2 updates
  1. identified May 26, 2026, 02:58 PM UTC

    We have identified an issue with the performance and loading of the PetDesk Dashboard. Our team is currently investigating and working to resolve this problem. This incident will be updated with additional details once received.

  2. resolved May 26, 2026, 03:27 PM UTC

    We are pleased to report that the performance issue has been resolved! Pages on the PetDesk Dashboard will now load as expected, and performance has returned to normal. If you continue to experience problems, please reach out to PetDesk Support at [email protected].

Read the full incident report →

Minor April 16, 2026

PetDesk Scribe Post Processing Issue

Detected by Pingoru
Apr 16, 2026, 05:26 PM UTC
Resolved
Apr 16, 2026, 10:06 PM UTC
Duration
4h 39m
Affected: PetDesk Scribe
Timeline · 4 updates
  1. identified Apr 16, 2026, 05:26 PM UTC

    We have identified an issue in our post recording processing. An intermediate fix has resulted an increase in successful processing but we are in the process of rolling back to a previous version that will fully resolve this issue. We expect to be able to re-process recordings as needed and will provide updates on that effort here.

  2. monitoring Apr 16, 2026, 06:18 PM UTC

    The rollback is complete and appointments are processing again. New appointments should complete as expected. We will begin batch reprocessing appointments where there were incomplete SOAP notes shortly.

  3. monitoring Apr 16, 2026, 10:06 PM UTC

    Processing is fully functional and appointments that were not marked as complete, but were missing SOAP notes, have been re-processed. If you are still having issues with processed appointments in Scribe, please reach out to support.

  4. resolved Apr 16, 2026, 10:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 16, 2026

PetDesk Pay Service Degradation

Detected by Pingoru
Apr 16, 2026, 05:05 PM UTC
Resolved
Apr 16, 2026, 10:04 PM UTC
Duration
4h 58m
Affected: PetDesk Pay
Timeline · 3 updates
  1. monitoring Apr 16, 2026, 05:05 PM UTC

    Our upstream payments provider is experiencing an issue processing payments. We are monitoring the situation and will post updates here as they become available.

  2. monitoring Apr 16, 2026, 06:00 PM UTC

    Per our provider the system has been stabilized. We'll continue to monitor.

  3. resolved Apr 16, 2026, 10:04 PM UTC

    We've received no further reports of incidence and our upstream provider indicates that services are stable. If you are still having issues processing payments, please reach out to support.

Read the full incident report →

Minor April 14, 2026

Scribe Processing Errors and Delays

Detected by Pingoru
Apr 14, 2026, 06:15 PM UTC
Resolved
Apr 14, 2026, 06:15 PM UTC
Duration
—
Timeline · 2 updates
  1. resolved Apr 14, 2026, 10:59 PM UTC

    An upstream provider experienced capacity issues causing processing errors and delays when processing Scribe recordings.

  2. postmortem Apr 14, 2026, 11:01 PM UTC

    An upstream provider encountered capacity issues around 1:15 pm CST. As a result Scribe recordings continued to process but were delayed due to repeated timeouts. Around 4pm CST capacity issues were resolved upstream and Scribe processing began to recover with full recovering around 5pm CST.

Read the full incident report →

Critical November 18, 2025

Cloudflare Related Service Incident

Detected by Pingoru
Nov 18, 2025, 01:30 PM UTC
Resolved
Nov 18, 2025, 06:36 PM UTC
Duration
5h 6m
Affected: Retriever
Timeline · 3 updates
  1. monitoring Nov 18, 2025, 01:30 PM UTC

    Cloudflare, an upstream provider, is currently experiencing an incident with their global network which is affecting some PetDesk systems. At the moment this includes petvisor.com, app.getkontak.com (Kontak/Phones Reporting), and retriever.getkontak.com (our standalone Kontak/Phones system). We are monitoring the incident and will post further updates here when we have them.

  2. monitoring Nov 18, 2025, 03:05 PM UTC

    Cloudflare is recovering and app.getkontak.com, retriever.getkontak.com, and the Phones integration in PetDesk Dashboard are recovering as well. We will continue to monitor and resolve this incident fully once Cloudflare indicates resolution on their side.

  3. resolved Nov 18, 2025, 06:36 PM UTC

    Cloudflare has indicated that their issue has been resolved. PetDesk Phones functionality has been fully restored.

Read the full incident report →

Minor October 20, 2025

SMS Delivery Delay

Detected by Pingoru
Oct 20, 2025, 07:15 PM UTC
Resolved
Oct 21, 2025, 01:21 AM UTC
Duration
6h 5m
Affected: SMS Notifications
Timeline · 4 updates
  1. investigating Oct 20, 2025, 07:15 PM UTC

    We are currently experiencing intermittent 10DLC SMS delivery issues through our provider, Twilio, due to the ongoing AWS US-East-1 regional outage. We will provide an update as soon as we have more information.

  2. monitoring Oct 20, 2025, 07:17 PM UTC

    Currently monitoring the situation with our upstream providers and will provide additional information as it becomes available to us.

  3. monitoring Oct 20, 2025, 09:08 PM UTC

    We're seeing reduced delays in SMS delivery and progress towards resolution, but will continue to monitor until our upstream service dependencies have reported a resolution.

  4. resolved Oct 21, 2025, 01:21 AM UTC

    Upstream service providers have marked today's issue as resolved.

Read the full incident report →

Critical September 19, 2025

PetDesk Communications Dashboard load issues

Detected by Pingoru
Sep 19, 2025, 03:57 PM UTC
Resolved
Sep 19, 2025, 05:31 PM UTC
Duration
1h 33m
Affected: Mobile App LoginPetDesk Communications Dashboard LoginProvider Communications Dashboard
Timeline · 6 updates
  1. investigating Sep 19, 2025, 03:57 PM UTC

    We have been notified of a problem that has hindered certain users from accessing the PetDesk Communications Dashboard. Our team promptly initiated an investigation and is diligently working to restore access for all clients. Further details will be provided soon.

  2. investigating Sep 19, 2025, 04:13 PM UTC

    We are continuing to investigate this issue.

  3. identified Sep 19, 2025, 04:24 PM UTC

    We have identified the cause and are implementing a fix to restore services. We will continue to provide updates as we work to resolve this issue.

  4. monitoring Sep 19, 2025, 04:41 PM UTC

    We’ve implemented a fix and are seeing services come back online. Our team will continue to closely monitor the restoration process and share regular updates until we’ve confirmed the issue is fully resolved.

  5. monitoring Sep 19, 2025, 05:01 PM UTC

    The issue appears resolved and services have been restored. Users may experience occasional slowness as systems fully recover. We continue to monitor closely and will post an update once we have confirmed that performance is fully back to normal.

  6. resolved Sep 19, 2025, 05:31 PM UTC

    Thank you for your patience. We have confirmed that services are fully recovered, performance has been restored, and applications are operating normally. We expect smooth performance moving forward. This will be our final update on this incident.

Read the full incident report →

Minor August 1, 2025

Missed overnight syncs for some practices - Covetrus Connect experienced loader job failures

Detected by Pingoru
Aug 01, 2025, 02:52 PM UTC
Resolved
Aug 01, 2025, 11:31 PM UTC
Duration
8h 39m
Affected: All Other PIMS (synced through Covetrus Connect)
Timeline · 2 updates
  1. identified Aug 01, 2025, 02:52 PM UTC

    Covetrus Connect identified an issue related to the API loader jobs that affected almost all of their syncs last night (8/1/25). At this time, new data from 7/31 may not be available from this integration partner, impacting our customers who sync PIMS data through Covetrus Connect . Covetrus Connect is working through this issue quickly to reach a resolution.

  2. resolved Aug 01, 2025, 11:31 PM UTC

    Covetrus Connect loader jobs are now caught up and we expect syncs should resume normally tonight without issues.

Read the full incident report →

Minor May 18, 2025

Delayed data sync for multiple providers syncing through Covetrus

Detected by Pingoru
May 18, 2025, 05:00 PM UTC
Resolved
May 22, 2025, 04:30 PM UTC
Duration
3d 23h
Affected: All Other PIMS (synced through Covetrus Connect)
Timeline · 3 updates
  1. identified May 19, 2025, 03:51 PM UTC

    On May 15th, 5/15, Covetrus performed a release and applied sweeping updates across clinics, impacting numerous records. The rollout duration caused PetDesk to flag these syncs as potential issues due to large-scale data changes. The safeguard was intentionally put in place, but it was triggered incorrectly in this case. Our team worked through restarting and ensuring all delayed syncs were completed successfully, but some delays occurred between 5/15 and 5/19.

  2. monitoring May 21, 2025, 05:48 PM UTC

    Covetrus Syncs are now fully recovered and operating normally. We expect tonight's sync run to resume normal operations and will monitor this activity.

  3. resolved May 22, 2025, 08:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 2, 2024

Slowed System Performance

Detected by Pingoru
Dec 02, 2024, 03:04 PM UTC
Resolved
Dec 03, 2024, 04:02 PM UTC
Duration
1d
Affected: Provider Communications Dashboard
Timeline · 4 updates
  1. investigating Dec 02, 2024, 03:04 PM UTC

    We are currently experiencing system slowness, and our team is actively working to identify and resolve the issue as quickly as possible. Thank you for your patience and understanding.

  2. identified Dec 02, 2024, 05:04 PM UTC

    We’ve applied an initial adjustment to improve performance and are continuing to work toward a full resolution. Thank you for your patience.

  3. monitoring Dec 02, 2024, 05:50 PM UTC

    We applied a temporary fix and we are seeing a substantial improvement in performance. As part of this initial fix, the “new appointments” count on the left sidebar will temporarily display as 0. To see new appointments, please manually refresh the “Needs Attention” page. We are continuing to monitor performance and work on the full solution continues. Thank you for your understanding as we work to resolve this quickly!

  4. resolved Dec 03, 2024, 04:02 PM UTC

    This incident has been resolved.

Read the full incident report →