PetDesk Outage History

13 incidents recorded over the last 365 days, 12 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 PetDesk Incident

PetDesk incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 10, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Sep 3, 2026Potential impact for PetDesk CustomersPer AWS: The issue is resolved and the service is operating normally at this time.1h 47mResolved
Aug 14, 2026Phone Service InterruptionOur provider has confirmed a resolution on their side and we have confirmed resolution for PetDesk Phones as well. We'll continue to monitor. If you experience any further issues, please contact support.8 minResolved
Jul 10, 2026Increased ErrorsThis incident has been resolved.66h 50mResolved
Jun 25, 2026Phones Transcripts IssueAll missed call recordings have been reprocessed.7h 56mResolved
Jun 17, 2026PetDesk Phones Caller ID and RecordingPreviously missing call recordings have been reprocessed and are now available in your dashboard. Changes have already been put in place with our upstream provider to prevent call recording processing from being missed…23h 29mResolved
Jun 10, 2026PetDesk DashboardThe incident has been resolved and all systems are back to normal performance.1h 41mResolved
May 26, 2026Dashboard Performance and AvailabilityWe 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…29 minResolved
Apr 16, 2026PetDesk Scribe Post Processing IssueThis incident has been resolved.4h 39mResolved
Apr 16, 2026PetDesk Pay Service DegradationWe'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.4h 58mResolved
Apr 14, 2026Scribe Processing Errors and DelaysAn 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…0 minResolved
Dec 3, 2025Dashboard Performance and AvailabilitySystem contention caused by an errant database query caused PetDesk Dashboard to experience sporadic performance issues and even failed page loads during this time. The query was identified and terminated permitting the…-1027 minResolved
Nov 18, 2025Cloudflare Related Service IncidentCloudflare has indicated that their issue has been resolved. PetDesk Phones functionality has been fully restored.5h 6mResolved

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 PetDesk 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 PetDesk 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 PetDesk 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 PetDesk outage in this window ran 2d 18h, against a mean recovery of 9h 50m. If you depend on PetDesk 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.