Pike13 had 21 outages in the last 2 years totaling 68h 22m of downtime — averaging 0.9 incidents per month.
There were 21 Pike13 outages since June 27, 2024 totaling 68h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have contacted Celero about connectivity issues that started 5:00am PDT today.
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.
This incident has been resolved.
Something isn't working right now. We're checking into it and will update you with more information ASAP.
We're back. Front Desk is up and running. Sorry for any trouble.
We are currently investigating this issue.
The issue has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The incident has been resolved. Systems are back to normal. We are investigating root cause and prevention steps.
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.
SmartWavier status can be viewed at https://status.smartwaiver.com/.
SmartWaiver says they have identified the problem and are working to resolve it. No estimated time to resolution yet.
There have been no waiver errors in the past 20 minutes. SmartWaiver says they have fixed the issue.
We are currently investigating this issue.
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.
Backfill of historical activities is progressing starting with most recent history to oldest. It will take several hours.
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.
This incident has been resolved.
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.
Our engineers are investigating slow performance and page load times across the platform.
Performance has returned to normal, but we are continuing to monitor and investigate.
This incident has been resolved. The primary impact was to search (searching for clients, searching for staff member, etc.).
Something isn't working right now. We're checking into it and will update you with more information ASAP.
We are continuing to investigate this issue.
Systems have returned to normal status.
External partner SmartWaiver is having issues. This is preventing Pike13 users from signing waivers. https://status.smartwaiver.com/
SmartWaiver restored their service about 25 minutes ago.
Server pool failed to scale up with increasing load. Fixed.
Between 4:19pm and 4:22pm US Pacific Time, there was an intense spike in load on the database that cause Pike13 applications to stop responding.
Pike13 had been intermittently slow throughout the day. We are investigating.
We are going to replace the hardware for the database in 10 minutes from now. There will be a 5-minute outage.
Slightly delayed while complete a full database backup first. Estimated time of outage now 11:00pm EDT.
The hardware replacement is in progress.
Maintenance complete. Systems operating normally now. We will be monitoring for recurrence of the intermittent slowness.
We are currently investigating this issue.
Database restart. All system operational. Continuing to monitor performance.
Something isn't working right now. We're checking into it and will update you with more information ASAP.
There does not appear to be any operational impact, but we are checking to be certain.
One of the servers in the Reporting API cluster had connectivity issues and was removed from rotation. The other servers in the cluster were able to handle all of the traffic, which is the purpose of having the redundancy. Everything working normally.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
After further analysis, it has been determined that this issue only affected Pike13 Support staff. No customers or clients were impacted.
Something isn't working right now. We're checking into it and will update you with more information ASAP.
We are continuing to investigate this issue.
Systems are back up. Still investigating cause and stability.
We're back. Pike13 is up and running. Sorry for any trouble.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Data processing into Reporting is very delayed. We are working on the problem.
We are continuing to work on this issue.
The issue has been resolved. They system is catching up. Next update will be when latency is back to normal.
The Reporting system is now fully caught up and operating normally.
Something isn't working right now. We're checking into it and will update you with more information ASAP.
This alarm is regarding the Reporting API.
Systems are still functioning normally. One of the servers in the cluster failed and must be replaced, but the other servers are carrying the load.
The issue has been identified and a fix is being implemented.
The unhealthy server has been replaced. All systems back to normal. There was no outage associated with this incident. Only a temporary reduction in capacity and redundancy.