Historial de interrupciones de Pike13

1. July 6, 2026 at 1:47 PM UTCinvestigating

   Las transacciones de tarjetas de crédito para algunos proveedores están actualmente fallando. Estamos investigando errores de conexión en la puerta de pago.

2. July 6, 2026 at 1:50 PM UTCinvestigating

   La puerta de entrada NMI ha confirmado que tienen problemas de conectividad. Puede seguir por aquí: https://status.transactiongateway.com/

3. July 6, 2026 at 2:09 PM UTCidentified

   NMI está trabajando en solucionar su problema.

4. July 6, 2026 at 2:57 PM UTCidentified

   No hemos visto ningún error de gateway NMI en los últimos 10 minutos. El NMI no ha confirmado que fijaron esta cuestión todavía, así que seguimos monitoreando.

5. July 6, 2026 at 3:09 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

6. July 6, 2026 at 3:17 PM UTCresolved

   NMI ha fijado su problema de conectividad. Esto ya está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. May 30, 2026 at 6:09 PM UTCinvestigating

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

2. May 30, 2026 at 8:55 PM UTCmonitoring

   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. May 30, 2026 at 9:46 PM UTCresolved

   This incident has been resolved.

1. May 28, 2026 at 1:49 PM UTCinvestigating

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

2. May 28, 2026 at 1:59 PM UTCresolved

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

1. May 28, 2026 at 1:47 PM UTCinvestigating

   We are currently investigating this issue.

2. May 28, 2026 at 1:58 PM UTCresolved

   The issue has been resolved.

1. April 19, 2026 at 2:15 PM UTCinvestigating

   We are currently investigating this issue.

2. April 19, 2026 at 2:31 PM UTCinvestigating

   We are continuing to investigate this issue.

3. April 19, 2026 at 2:44 PM UTCresolved

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

1. March 18, 2026 at 12:23 AM UTCinvestigating

   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. March 18, 2026 at 12:29 AM UTCinvestigating

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

3. March 18, 2026 at 2:13 AM UTCinvestigating

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

4. March 18, 2026 at 2:41 AM UTCresolved

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

1. March 9, 2026 at 3:25 PM UTCinvestigating

   We are currently investigating this issue.

2. March 9, 2026 at 4:15 PM UTCmonitoring

   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. March 9, 2026 at 6:17 PM UTCmonitoring

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

4. March 9, 2026 at 7:50 PM UTCmonitoring

   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. March 9, 2026 at 7:50 PM UTCresolved

   This incident has been resolved.

1. December 20, 2025 at 6:22 PM UTCresolved

   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.

1. December 17, 2025 at 5:06 PM UTCinvestigating

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

2. December 17, 2025 at 5:20 PM UTCmonitoring

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

3. December 17, 2025 at 5:56 PM UTCresolved

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

1. August 2, 2025 at 12:48 AM UTCinvestigating

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

2. August 2, 2025 at 12:59 AM UTCinvestigating

   We are continuing to investigate this issue.

3. August 2, 2025 at 1:09 AM UTCresolved

   Systems have returned to normal status.

1. August 1, 2025 at 12:11 AM UTCinvestigating

   We are currently investigating this issue.

2. August 1, 2025 at 12:26 AM UTCresolved

   This incident has been resolved.

1. July 9, 2025 at 2:02 PM UTCinvestigating

   We are currently investigating an issue with reporting data not being updated.

2. July 9, 2025 at 3:40 PM UTCinvestigating

   The issue has been resolved. Replication is catching up. Stay tuned here for updates on latency reduction until fully caught up.

3. July 9, 2025 at 3:49 PM UTCinvestigating

   Reporting latency is currently approximately 24 hours behind.

4. July 9, 2025 at 4:32 PM UTCinvestigating

   Data latency in reporting continues to slowly decrease. We are constantly monitoring the situation and will update this page at least once every four hours with the current latency until reporting data reaches expected parameters. We expect full resolution by end of day today.

5. July 9, 2025 at 6:26 PM UTCmonitoring

   Latency continues to decrease slowly as the system processes all of the data from yesterday. It will decrease more rapidly once all of the data from peak activity hours yesterday has been processed. We still expect reporting to be fully caught up to normal latency by the end of the day today.

6. July 9, 2025 at 8:13 PM UTCmonitoring

   Reporting data is now loaded up to 4:30pm EDT yesterday (July 8). It still needs to process the remainder of July 8, and of course catch up on July 9.

7. July 9, 2025 at 11:54 PM UTCmonitoring

   Reporting data is now loaded up to 6:20pm EDT yesterday (July 8). Slow going as it churns through peak-time data.

8. July 10, 2025 at 3:53 AM UTCmonitoring

   Latency is dropping more rapidly. The system has now moved on to processing data from today (July 9).

9. July 10, 2025 at 1:08 PM UTCmonitoring

   Reporting data is now loaded up to July 9 6:15pm EDT. Still a ways to go.

10. July 10, 2025 at 6:21 PM UTCmonitoring

    Reporting data is now loaded up through end of day July 9 EDT.

11. July 10, 2025 at 10:00 PM UTCmonitoring

    Reporting data is now loaded up through today (July 10) 1:15pm EDT. Nearly caught up now.

12. July 11, 2025 at 4:01 AM UTCresolved

    Reporting data latency has returned to normal.

1. June 12, 2025 at 1:16 PM UTCinvestigating

   External partner SmartWaiver is having issues. This is preventing Pike13 users from signing waivers. https://status.smartwaiver.com/

2. June 12, 2025 at 2:25 PM UTCresolved

   SmartWaiver restored their service about 25 minutes ago.

1. February 5, 2025 at 10:17 PM UTCresolved

   Server pool failed to scale up with increasing load. Fixed.

1. November 22, 2024 at 12:39 AM UTCresolved

   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.

1. October 14, 2024 at 10:32 PM UTCinvestigating

   Pike13 had been intermittently slow throughout the day. We are investigating.

2. October 14, 2024 at 11:19 PM UTCinvestigating

   We are going to replace the hardware for the database in 10 minutes from now. There will be a 5-minute outage.

3. October 14, 2024 at 11:28 PM UTCinvestigating

   Slightly delayed while complete a full database backup first. Estimated time of outage now 11:00pm EDT.

4. October 15, 2024 at 3:08 AM UTCinvestigating

   The hardware replacement is in progress.

5. October 15, 2024 at 3:25 AM UTCresolved

   Maintenance complete. Systems operating normally now. We will be monitoring for recurrence of the intermittent slowness.

1. October 14, 2024 at 3:37 PM UTCinvestigating

   We are currently investigating this issue.

2. October 14, 2024 at 3:47 PM UTCresolved

   Database restart. All system operational. Continuing to monitor performance.

1. September 11, 2024 at 6:48 PM UTCinvestigating

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

2. September 11, 2024 at 6:51 PM UTCinvestigating

   There does not appear to be any operational impact, but we are checking to be certain.

3. September 11, 2024 at 7:02 PM UTCresolved

   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.

1. August 19, 2024 at 3:11 PM UTCinvestigating

   We are currently investigating this issue.

2. August 19, 2024 at 3:11 PM UTCidentified

   The issue has been identified and a fix is being implemented.

3. August 19, 2024 at 3:34 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. August 19, 2024 at 3:39 PM UTCresolved

   This incident has been resolved.

5. August 19, 2024 at 6:24 PM UTCpostmortem

   After further analysis, it has been determined that this issue only affected Pike13 Support staff. No customers or clients were impacted.

1. July 31, 2024 at 12:07 PM UTCinvestigating

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

2. July 31, 2024 at 12:19 PM UTCinvestigating

   We are continuing to investigate this issue.

3. July 31, 2024 at 12:27 PM UTCmonitoring

   Systems are back up. Still investigating cause and stability.

4. July 31, 2024 at 12:33 PM UTCresolved

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