Pike13 장애 기록

1. 2026년 7월 6일 PM 1:47 UTCinvestigating

   일부 공급자의 신용 카드 거래는 현재 실패하고 있습니다. 결제 게이트웨이에서 연결 오류를 조사하고 있습니다.

2. 2026년 7월 6일 PM 1:50 UTCinvestigating

   NMI 게이트웨이는 연결 문제가 있음을 확인했습니다. 다음을 따라갈 수 있습니다: https://status.transactiongateway.com/

3. 2026년 7월 6일 PM 2:09 UTCidentified

   NMI는 문제 해결에 노력하고 있습니다.

4. 2026년 7월 6일 PM 2:57 UTCidentified

   지난 10 분 동안 NMI 게이트웨이 오류가 없습니다. NMI는 아직이 문제를 해결하지 않았으므로 여전히 모니터링하고 있습니다.

5. 2026년 7월 6일 PM 3:09 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

6. 2026년 7월 6일 PM 3:17 UTCresolved

   NMI는 연결 문제를 해결했습니다. 이것은 이제 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 30일 PM 6:09 UTCinvestigating

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

2. 2026년 5월 30일 PM 8:55 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. 2026년 5월 30일 PM 9:46 UTCresolved

   This incident has been resolved.

1. 2026년 5월 28일 PM 1:49 UTCinvestigating

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

2. 2026년 5월 28일 PM 1:59 UTCresolved

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

1. 2026년 5월 28일 PM 1:47 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 5월 28일 PM 1:58 UTCresolved

   The issue has been resolved.

1. 2026년 4월 19일 PM 2:15 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 4월 19일 PM 2:31 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 4월 19일 PM 2:44 UTCresolved

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

1. 2026년 3월 18일 AM 12:23 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. 2026년 3월 18일 AM 12:29 UTCinvestigating

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

3. 2026년 3월 18일 AM 2:13 UTCinvestigating

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

4. 2026년 3월 18일 AM 2:41 UTCresolved

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

1. 2026년 3월 9일 PM 3:25 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 3월 9일 PM 4:15 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. 2026년 3월 9일 PM 6:17 UTCmonitoring

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

4. 2026년 3월 9일 PM 7:50 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. 2026년 3월 9일 PM 7:50 UTCresolved

   This incident has been resolved.

1. 2025년 12월 20일 PM 6:22 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. 2025년 12월 17일 PM 5:06 UTCinvestigating

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

2. 2025년 12월 17일 PM 5:20 UTCmonitoring

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

3. 2025년 12월 17일 PM 5:56 UTCresolved

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

1. 2025년 8월 2일 AM 12:48 UTCinvestigating

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

2. 2025년 8월 2일 AM 12:59 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 8월 2일 AM 1:09 UTCresolved

   Systems have returned to normal status.

1. 2025년 8월 1일 AM 12:11 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 8월 1일 AM 12:26 UTCresolved

   This incident has been resolved.

1. 2025년 7월 9일 PM 2:02 UTCinvestigating

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

2. 2025년 7월 9일 PM 3:40 UTCinvestigating

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

3. 2025년 7월 9일 PM 3:49 UTCinvestigating

   Reporting latency is currently approximately 24 hours behind.

4. 2025년 7월 9일 PM 4:32 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. 2025년 7월 9일 PM 6:26 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. 2025년 7월 9일 PM 8:13 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. 2025년 7월 9일 PM 11:54 UTCmonitoring

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

8. 2025년 7월 10일 AM 3:53 UTCmonitoring

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

9. 2025년 7월 10일 PM 1:08 UTCmonitoring

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

10. 2025년 7월 10일 PM 6:21 UTCmonitoring

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

11. 2025년 7월 10일 PM 10:00 UTCmonitoring

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

12. 2025년 7월 11일 AM 4:01 UTCresolved

    Reporting data latency has returned to normal.

1. 2025년 6월 12일 PM 1:16 UTCinvestigating

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

2. 2025년 6월 12일 PM 2:25 UTCresolved

   SmartWaiver restored their service about 25 minutes ago.

1. 2025년 2월 5일 PM 10:17 UTCresolved

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

1. 2024년 11월 22일 AM 12:39 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. 2024년 10월 14일 PM 10:32 UTCinvestigating

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

2. 2024년 10월 14일 PM 11:19 UTCinvestigating

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

3. 2024년 10월 14일 PM 11:28 UTCinvestigating

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

4. 2024년 10월 15일 AM 3:08 UTCinvestigating

   The hardware replacement is in progress.

5. 2024년 10월 15일 AM 3:25 UTCresolved

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

1. 2024년 10월 14일 PM 3:37 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 10월 14일 PM 3:47 UTCresolved

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

1. 2024년 9월 11일 PM 6:48 UTCinvestigating

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

2. 2024년 9월 11일 PM 6:51 UTCinvestigating

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

3. 2024년 9월 11일 PM 7:02 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. 2024년 8월 19일 PM 3:11 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 8월 19일 PM 3:11 UTCidentified

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

3. 2024년 8월 19일 PM 3:34 UTCmonitoring

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

4. 2024년 8월 19일 PM 3:39 UTCresolved

   This incident has been resolved.

5. 2024년 8월 19일 PM 6:24 UTCpostmortem

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

1. 2024년 7월 31일 PM 12:07 UTCinvestigating

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

2. 2024년 7월 31일 PM 12:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 7월 31일 PM 12:27 UTCmonitoring

   Systems are back up. Still investigating cause and stability.

4. 2024년 7월 31일 PM 12:33 UTCresolved

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