Paydock Outage History

Paydock is up right now

Paydock had 9 outages in the last 2 years totaling 8h 34m of downtime — averaging 0.4 incidents per month.

There were 9 Paydock outages since September 18, 2024 totaling 8h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://paydock.statuspage.io

Notice July 24, 2026

Degraded performance on Paydock platform

Detected by Pingoru
Jul 24, 2026, 04:45 AM UTC
Resolved
Jul 24, 2026, 04:45 AM UTC
Duration
Timeline · 1 update
  1. resolved Jul 27, 2026, 06:42 AM UTC

    Following the earlier incident, Paydock experienced a second period of degraded performance beginning 04:49 UTC (14:49 AEST). The affected window — during which several internal services in the payment path were unavailable — was 05:29–05:49 UTC (15:29–15:49 AEST). Performance stabilised shortly after, and full recovery was confirmed by 07:05 UTC (17:05 AEST).

Read the full incident report →

Critical May 12, 2026

Paydock Platform Outage

Detected by Pingoru
May 12, 2026, 09:47 AM UTC
Resolved
May 12, 2026, 11:09 AM UTC
Duration
1h 21m
Affected: Paydock APIPaydock Dashboard
Timeline · 3 updates
  1. investigating May 12, 2026, 09:47 AM UTC

    Our monitoring has alerted us to issues affecting Portal access, as well as payment processing. We're actively investigating this, and we'll provide updates to this page as soon as we have more information.

  2. identified May 12, 2026, 10:15 AM UTC

    We've identified the cause of the issue, and have restored access to the dashboard, as well as unblocked payment processing. There may still be issues with messaging services (notifications, audit logs), we are still working to restore all functionality.

  3. resolved May 12, 2026, 11:09 AM UTC

    All services have been restored to full functionality. Please reach out to [email protected] if you are still experiencing any issues.

Read the full incident report →

Critical October 16, 2025

We are currently experiencing issues with Payment throughput.

Detected by Pingoru
Oct 16, 2025, 04:18 AM UTC
Resolved
Oct 16, 2025, 05:23 AM UTC
Duration
1h 5m
Affected: Paydock API
Timeline · 3 updates
  1. investigating Oct 16, 2025, 04:18 AM UTC

    We are currently experiencing issues with Payment throughput, we are investigating.

  2. monitoring Oct 16, 2025, 04:50 AM UTC

    Platform stability has returned, we are currently monitoring.

  3. resolved Oct 16, 2025, 05:49 AM UTC

    Issues with Payment throughput were resolved at 3:23pm AEDT

Read the full incident report →

Major October 16, 2025

Platform Degradation - API and Dashboard

Detected by Pingoru
Oct 16, 2025, 03:24 AM UTC
Resolved
Oct 16, 2025, 06:49 AM UTC
Duration
3h 25m
Affected: Paydock APIPaydock Dashboard
Timeline · 2 updates
  1. investigating Oct 16, 2025, 03:24 AM UTC

    We are currently investigating reported Platform Degradation with API and dashboard.

  2. resolved Oct 16, 2025, 06:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 28, 2025

[External] Slow Response Times and Increased 4xx Errors - Gpayments

Detected by Pingoru
Aug 28, 2025, 09:35 AM UTC
Resolved
Aug 28, 2025, 11:11 AM UTC
Duration
1h 35m
Affected: Gpayments service
Timeline · 2 updates
  1. monitoring Aug 28, 2025, 09:35 AM UTC

    We're currently seeing slow response times and an increase in errors from Gpayments. Gpayments has confirmed they are investigating an incident on their end.

  2. resolved Aug 28, 2025, 11:11 AM UTC

    Gpayments have advised that the issue has been resolved, no errors have been observed since 6:50pm AEST.

Read the full incident report →

Minor February 12, 2025

Performance Degradation Resolved

Detected by Pingoru
Feb 12, 2025, 07:20 PM UTC
Resolved
Feb 12, 2025, 07:20 PM UTC
Duration
Affected: Paydock API
Timeline · 1 update
  1. resolved Feb 12, 2025, 07:20 PM UTC

    Temporary unavailability and degraded performance of POST//v1/charges/wallet and POST//v1/charges endpoints due to a configuration change to reinforce the Platform's security. Customers of the unaffected instances were still able to complete their transactions. The incident itself started at 16:38 PM UTC and finished at 17:47 PM UTC.

Read the full incident report →

Major January 22, 2025

Major outage due to configuration issue.

Detected by Pingoru
Jan 22, 2025, 11:26 AM UTC
Resolved
Jan 22, 2025, 11:26 AM UTC
Duration
Affected: Paydock API
Timeline · 1 update
  1. resolved Jan 22, 2025, 11:26 AM UTC

    On the 22/01/2025 Between 09:45 PM and 10:17PM AEDT We experienced a major outage affecting 50% of our instances, meaning that 50% of the instances continued to function correctly. However, the misconfiguration had a direct impact on customers attempting to make card and wallet payments. Customers on the affected instances were unable to complete transactions, which caused a significant disruption. That said, customers on unaffected instances were still able to transact normally, ensuring some continuity of service.

Read the full incident report →

Minor January 14, 2025

intermittent issues accessing Paydock Dashboard

Detected by Pingoru
Jan 14, 2025, 10:23 PM UTC
Resolved
Jan 14, 2025, 10:44 PM UTC
Duration
21m
Affected: Paydock Dashboard
Timeline · 2 updates
  1. investigating Jan 14, 2025, 10:23 PM UTC

    We are currently investigating the issue.

  2. resolved Jan 14, 2025, 10:44 PM UTC

    The Incident has been resolved.

Read the full incident report →

Major September 18, 2024

Incident - P3 Afterpay V1 Issue

Detected by Pingoru
Sep 18, 2024, 06:36 AM UTC
Resolved
Sep 18, 2024, 07:21 AM UTC
Duration
45m
Affected: Afterpay gateway
Timeline · 3 updates
  1. investigating Sep 18, 2024, 06:36 AM UTC

    We are experiencing intermittent issues with Afterpay V1 transactions, which appear to be related to an external issue with Afterpay. We are actively addressing this with their team.

  2. investigating Sep 18, 2024, 06:36 AM UTC

    We are continuing to investigate this issue.

  3. resolved Sep 18, 2024, 07:21 AM UTC

    This issue was a confirmed issue with Afterpay affecting Afterpay v1. The service was restored by Afterpay at 4:20 PM AEST.

Read the full incident report →