PayClock Outage History

PayClock is up right now

PayClock had 3 outages in the last 2 years totaling 2h 29m of downtime — averaging 0.1 incidents per month.

There were 3 PayClock outages since August 19, 2025 totaling 2h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.payclock.com

Major June 30, 2026

We're currently having issues with our clocks

Detected by Pingoru
Jun 30, 2026, 08:04 PM UTC
Resolved
Jun 30, 2026, 09:05 PM UTC
Duration
1h
Timeline · 2 updates
  1. investigating Jun 30, 2026, 08:04 PM UTC

    Some people are experiencing problems with our clock service right now. We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.

  2. resolved Jun 30, 2026, 09:05 PM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major June 30, 2026

We're currently having issues

Detected by Pingoru
Jun 30, 2026, 06:35 PM UTC
Resolved
Jun 30, 2026, 07:01 PM UTC
Duration
25m
Timeline · 3 updates
  1. investigating Jun 30, 2026, 06:35 PM UTC

    Some people are experiencing problems with our service right now. We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.

  2. investigating Jun 30, 2026, 06:50 PM UTC

    We've fixed the core issue, and are waiting for things to recover.

  3. resolved Jun 30, 2026, 07:01 PM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major May 15, 2026

We're currently having issues with running reports.

Detected by Pingoru
May 15, 2026, 04:32 PM UTC
Resolved
May 15, 2026, 05:36 PM UTC
Duration
1h 3m
Timeline · 2 updates
  1. investigating May 15, 2026, 04:32 PM UTC

    Some people are experiencing problems with running reports right now. We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.

  2. resolved May 15, 2026, 05:36 PM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →