Pike13 Outage History

Pike13 is up right now

Pike13 had 10 outages in the last 2 years totaling 50h 21m of downtime — averaging 0.4 incidents per month.

There were 10 Pike13 outages since July 9, 2025 totaling 50h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pike13.com

Minor May 30, 2026

Celero Surcharging Gateway Connectivity Issues

Detected by Pingoru
May 30, 2026, 06:09 PM UTC
Resolved
May 30, 2026, 09:46 PM UTC
Duration
3h 37m
Affected: Payment Processing
Timeline · 3 updates
  1. investigating May 30, 2026, 06:09 PM UTC

    We have contacted Celero about connectivity issues that started 5:00am PDT today.

  2. monitoring May 30, 2026, 08:55 PM UTC

    Connectivity errors have ceased as of 30 minutes ago, but we have not yet received confirmation from Celero that the the issue is fully resolved.

  3. resolved May 30, 2026, 09:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 28, 2026

Minor Outage

Detected by Pingoru
May 28, 2026, 01:49 PM UTC
Resolved
May 28, 2026, 01:59 PM UTC
Duration
10m
Timeline · 2 updates
  1. investigating May 28, 2026, 01:49 PM UTC

    Something isn't working right now. We're checking into it and will update you with more information ASAP.

  2. resolved May 28, 2026, 01:59 PM UTC

    We're back. Front Desk is up and running. Sorry for any trouble.

Read the full incident report →

Minor May 28, 2026

Outage

Detected by Pingoru
May 28, 2026, 01:47 PM UTC
Resolved
May 28, 2026, 01:58 PM UTC
Duration
10m
Affected: Your Pike13 Website
Timeline · 2 updates
  1. investigating May 28, 2026, 01:47 PM UTC

    We are currently investigating this issue.

  2. resolved May 28, 2026, 01:58 PM UTC

    The issue has been resolved.

Read the full incident report →

Critical April 19, 2026

Pike13 Outage

Detected by Pingoru
Apr 19, 2026, 02:15 PM UTC
Resolved
Apr 19, 2026, 02:44 PM UTC
Duration
29m
Affected: Your Pike13 WebsiteAPI
Timeline · 3 updates
  1. investigating Apr 19, 2026, 02:15 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 19, 2026, 02:31 PM UTC

    We are continuing to investigate this issue.

  3. resolved Apr 19, 2026, 02:44 PM UTC

    The incident has been resolved. Systems are back to normal. We are investigating root cause and prevention steps.

Read the full incident report →

Major March 18, 2026

SmartWaiver issues

Detected by Pingoru
Mar 18, 2026, 12:23 AM UTC
Resolved
Mar 18, 2026, 02:41 AM UTC
Duration
2h 17m
Affected: 3rd Party Integration
Timeline · 4 updates
  1. investigating Mar 18, 2026, 12:23 AM UTC

    Our partner SmartWaiver is having technical issues. Waivers in Pike13, which all use the SmartWaiver service, are not working. We have opened a support ticket with them.

  2. investigating Mar 18, 2026, 12:29 AM UTC

    SmartWavier status can be viewed at https://status.smartwaiver.com/.

  3. investigating Mar 18, 2026, 02:13 AM UTC

    SmartWaiver says they have identified the problem and are working to resolve it. No estimated time to resolution yet.

  4. resolved Mar 18, 2026, 02:41 AM UTC

    There have been no waiver errors in the past 20 minutes. SmartWaiver says they have fixed the issue.

Read the full incident report →

Critical March 9, 2026

Database outage

Detected by Pingoru
Mar 09, 2026, 03:25 PM UTC
Resolved
Mar 09, 2026, 07:50 PM UTC
Duration
4h 25m
Affected: Your Pike13 WebsitePayment ProcessingAPIClient App
Timeline · 5 updates
  1. investigating Mar 09, 2026, 03:25 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 09, 2026, 04:15 PM UTC

    The database outage is over. Historical activities records will not display currently. We are starting the process of back filling those records into the rebuilt table.

  3. monitoring Mar 09, 2026, 06:17 PM UTC

    Backfill of historical activities is progressing starting with most recent history to oldest. It will take several hours.

  4. monitoring Mar 09, 2026, 07:50 PM UTC

    Activities data has been restored from present back to November 1, 2025. The restore is continuing and is processing approximately 1 million records per minute going backwards in historical order. All records going all the way back to the year 2012 will be restored by tomorrow.

  5. resolved Mar 09, 2026, 07:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 20, 2025

Background Processes Stalled

Detected by Pingoru
Dec 20, 2025, 06:22 PM UTC
Resolved
Dec 20, 2025, 03:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Dec 20, 2025, 06:22 PM UTC

    Background processes exhausted system memory. We restarted services and background jobs caught up by 9:15am PST. We have added more redundancy to prevent future occurrences. We have also improved system monitoring for this event so that we will have faster resolution in the future.

Read the full incident report →

Minor December 17, 2025

Slowness across platform

Detected by Pingoru
Dec 17, 2025, 05:06 PM UTC
Resolved
Dec 17, 2025, 05:56 PM UTC
Duration
50m
Affected: Your Pike13 WebsiteAPI
Timeline · 3 updates
  1. investigating Dec 17, 2025, 05:06 PM UTC

    Our engineers are investigating slow performance and page load times across the platform.

  2. monitoring Dec 17, 2025, 05:20 PM UTC

    Performance has returned to normal, but we are continuing to monitor and investigate.

  3. resolved Dec 17, 2025, 05:56 PM UTC

    This incident has been resolved. The primary impact was to search (searching for clients, searching for staff member, etc.).

Read the full incident report →

Critical August 2, 2025

Major Outage

Detected by Pingoru
Aug 02, 2025, 12:48 AM UTC
Resolved
Aug 02, 2025, 01:09 AM UTC
Duration
20m
Affected: Your Pike13 WebsiteAPIReporting
Timeline · 3 updates
  1. investigating Aug 02, 2025, 12:48 AM UTC

    Something isn't working right now. We're checking into it and will update you with more information ASAP.

  2. investigating Aug 02, 2025, 12:59 AM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 02, 2025, 01:09 AM UTC

    Systems have returned to normal status.

Read the full incident report →