История сбоев Pike13

1. 6 июля 2026 г. в 13:47 UTCinvestigating

   Операции с кредитными картами для некоторых провайдеров в настоящее время терпят неудачу. Мы изучаем ошибки подключения в платежном шлюзе.

2. 6 июля 2026 г. в 13:50 UTCinvestigating

   Шлюз NMI подтвердил, что у них есть проблемы с подключением. Вы можете ознакомиться здесь: https://status.transactiongateway.com/

3. 6 июля 2026 г. в 14:09 UTCidentified

   NMI работает над решением этой проблемы.

4. 6 июля 2026 г. в 14:57 UTCidentified

   За последние 10 минут мы не видели ошибок шлюза NMI. NMI пока не подтвердила, что они исправили эту проблему, поэтому мы продолжаем мониторинг.

5. 6 июля 2026 г. в 15:09 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

6. 6 июля 2026 г. в 15:17 UTCresolved

   NMI решила проблему подключения. Теперь это решено.

Автоматический перевод официального обновления инцидента.

1. 30 мая 2026 г. в 18:09 UTCinvestigating

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

2. 30 мая 2026 г. в 20: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. 30 мая 2026 г. в 21:46 UTCresolved

   This incident has been resolved.

1. 28 мая 2026 г. в 13:49 UTCinvestigating

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

2. 28 мая 2026 г. в 13:59 UTCresolved

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

1. 28 мая 2026 г. в 13:47 UTCinvestigating

   We are currently investigating this issue.

2. 28 мая 2026 г. в 13:58 UTCresolved

   The issue has been resolved.

1. 19 апреля 2026 г. в 14:15 UTCinvestigating

   We are currently investigating this issue.

2. 19 апреля 2026 г. в 14:31 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 апреля 2026 г. в 14:44 UTCresolved

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

1. 18 марта 2026 г. в 00: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. 18 марта 2026 г. в 00:29 UTCinvestigating

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

3. 18 марта 2026 г. в 02:13 UTCinvestigating

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

4. 18 марта 2026 г. в 02:41 UTCresolved

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

1. 9 марта 2026 г. в 15:25 UTCinvestigating

   We are currently investigating this issue.

2. 9 марта 2026 г. в 16: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. 9 марта 2026 г. в 18:17 UTCmonitoring

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

4. 9 марта 2026 г. в 19: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. 9 марта 2026 г. в 19:50 UTCresolved

   This incident has been resolved.

1. 20 декабря 2025 г. в 18: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. 17 декабря 2025 г. в 17:06 UTCinvestigating

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

2. 17 декабря 2025 г. в 17:20 UTCmonitoring

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

3. 17 декабря 2025 г. в 17:56 UTCresolved

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

1. 2 августа 2025 г. в 00:48 UTCinvestigating

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

2. 2 августа 2025 г. в 00:59 UTCinvestigating

   We are continuing to investigate this issue.

3. 2 августа 2025 г. в 01:09 UTCresolved

   Systems have returned to normal status.

1. 1 августа 2025 г. в 00:11 UTCinvestigating

   We are currently investigating this issue.

2. 1 августа 2025 г. в 00:26 UTCresolved

   This incident has been resolved.

1. 9 июля 2025 г. в 14:02 UTCinvestigating

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

2. 9 июля 2025 г. в 15:40 UTCinvestigating

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

3. 9 июля 2025 г. в 15:49 UTCinvestigating

   Reporting latency is currently approximately 24 hours behind.

4. 9 июля 2025 г. в 16: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. 9 июля 2025 г. в 18: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. 9 июля 2025 г. в 20: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. 9 июля 2025 г. в 23: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. 10 июля 2025 г. в 03:53 UTCmonitoring

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

9. 10 июля 2025 г. в 13:08 UTCmonitoring

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

10. 10 июля 2025 г. в 18:21 UTCmonitoring

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

11. 10 июля 2025 г. в 22:00 UTCmonitoring

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

12. 11 июля 2025 г. в 04:01 UTCresolved

    Reporting data latency has returned to normal.

1. 12 июня 2025 г. в 13:16 UTCinvestigating

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

2. 12 июня 2025 г. в 14:25 UTCresolved

   SmartWaiver restored their service about 25 minutes ago.

1. 5 февраля 2025 г. в 22:17 UTCresolved

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

1. 22 ноября 2024 г. в 00: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. 14 октября 2024 г. в 22:32 UTCinvestigating

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

2. 14 октября 2024 г. в 23: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. 14 октября 2024 г. в 23:28 UTCinvestigating

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

4. 15 октября 2024 г. в 03:08 UTCinvestigating

   The hardware replacement is in progress.

5. 15 октября 2024 г. в 03:25 UTCresolved

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

1. 14 октября 2024 г. в 15:37 UTCinvestigating

   We are currently investigating this issue.

2. 14 октября 2024 г. в 15:47 UTCresolved

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

1. 11 сентября 2024 г. в 18:48 UTCinvestigating

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

2. 11 сентября 2024 г. в 18:51 UTCinvestigating

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

3. 11 сентября 2024 г. в 19: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. 19 августа 2024 г. в 15:11 UTCinvestigating

   We are currently investigating this issue.

2. 19 августа 2024 г. в 15:11 UTCidentified

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

3. 19 августа 2024 г. в 15:34 UTCmonitoring

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

4. 19 августа 2024 г. в 15:39 UTCresolved

   This incident has been resolved.

5. 19 августа 2024 г. в 18:24 UTCpostmortem

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

1. 31 июля 2024 г. в 12:07 UTCinvestigating

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

2. 31 июля 2024 г. в 12:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 31 июля 2024 г. в 12:27 UTCmonitoring

   Systems are back up. Still investigating cause and stability.

4. 31 июля 2024 г. в 12:33 UTCresolved

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