Pinpoint 장애 기록

1. 2026년 9월 1일 오전 8:20 UTCinvestigating

   우리는 현재 "Sending"상태에 붙어있는 이메일에 영향을 미치는 문제를 조사하고 있습니다. 우리의 기술설계 팀은 문제점의 aware이고 적극적인 조사입니다. 우리는 더 많은 것을 배우고 해결책을 향해 일하는 것과 같이 새롭게 제공할 것입니다.

2. 2026년 9월 1일 오전 9:40 UTCidentified

   우리는 문제점을 확인했습니다 - 우리의 기술설계 팀은 현재 고침에 일하고 이 해결되었습니다 한 번 더 갱신을 제공할 것입니다.

3. 2026년 9월 1일 오전 10:30 UTCmonitoring

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

4. 2026년 9월 1일 오후 3:01 UTCresolved

   이 사건은 해결되었습니다.

5. 2026년 9월 2일 오전 11:07 UTCpostmortem

   ## **이메일 배달 중단 - 29 8 월 1 9 월 2026** ** 일어난 일 ** 토요일 29 8 월과 월요일의 오후 31 8 월 사이, 그리고 다시 23:30 BST 월요일 31 8 월까지 11:09 BST 화요일 1 9 월, 핀 포인트에서 보낸 이메일은 전달되지 않았습니다. 이 영향 받은 후보 통신, 알림 및 기타 아웃바운드 이메일 플랫폼. ** 원인 ** 두 파괴는 우리의 이메일 납품 공급자, Postmark에 기인했습니다. 계정 제한은 측면에 적용되었으며, 그 해상도를 따르고, 팀의 필수 매뉴얼 검토가 완료되지 않았습니다. 이 자리에 제한을 남았고 그 시스템을 통해 전송되지 않는 동안 우리의 이메일을 수락합니다. 오류가 우리에게 반환되지 않았다, 이는 왜 두 번째 혼란은 고객이보고 될 때까지 감지되지 않았다. Postmark는 오류가 발생했으며, 수정 및 검토 프로세스에 대한 변경 및 반복을 방지하기 위해 계정 설정을 확인했습니다. Pinpoint의 변경은 사건에 기여했습니다. ** 해결책 ** 화요일 아침에 우리의 엔지니어링 팀은 문제가 업스트림과 복원 된 배달을 확인했습니다. Postmark로 새로운 전송 채널을 통해 모든 이메일. 배달은 11:09 BST에 의해 작동 확인되었습니다. 중단 중에 영향을받는 모든 이메일이 전달되었습니다. 작은 수의 수신자는 복구의 결과로 일부 이메일의 중복 사본을받을 수 있습니다; 우리는이 발생 어떤 혼란에 대 한 사과. ** 우리가하는 것은 무엇입니까 ** * 우리는 윤곽을 통해 이메일 납품 수로를 즉각 전환하는 기능을 추가했습니다, 그래서 유사한 공급자 측 문제점은 시간 보다는 더 적은 분에서 주변에 작동될 수 있습니다. * 우리는 우리가 우리의 공급자에게서 받은 통보를 확장했습니다 그래서 계정 문제점은 시간의 밑에 우리의 팀의 더 넓은 그룹에 눈에 보입니다. * 우리는 납품 양에 감시를 추가하고 그래서 배달된 이메일에 있는 하락은 우리의 공급자가 과실을 보고하는지, 자주적으로 검출됩니다. * 우리는 Postmark와이 사건의 취급을 공식화하고 우리의 이메일 납품 배열을 더 넓게 검토하고 있습니다. 우리는 당신을 기인하고 당신의 후보자를 방해에 대 한 미안 해요. 질문이 있거나 믿지 않은 특정 이메일이 전달되지 않은 경우 고객 성공 관리자 또는 [[email protected]](mailto:[email protected])로 문의하십시오.

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

1. 2026년 8월 3일 오후 2:33 UTCmonitoring

   우리의 지원 공급자, 핀 (이전 Intercom)는, 현재 서비스 outage를 경험하고 있습니다. 그 결과, 우리는 일시적으로 메시지 지원에 응답 할 수 없습니다. 우리는 Fin의 상태 페이지 : https://www.finstatus.com/us-hosting을 통해 긴밀하게 상황을 모니터링하고 서비스가 복원되기 때문에 귀하의 질문에 응답 할 것입니다. 당신의 인내와 이해에 감사드립니다.

2. 2026년 8월 3일 오후 4:42 UTCresolved

   지원 업데이트 - 해결 Fin (이전 Intercom)은 수정을 배포했으며, 문제가 이제 해결 될 것으로 나타났습니다. 우리 팀은 다시 지원 inbox에 액세스하고 쿼리에 응답합니다. 우리는 어떤 변화든지에서 바싹 상황을 감시하는 것을 계속할 것입니다. 이 문제가 해결 된 동안 당신의 인내심을 주셔서 감사합니다.

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

1. 2026년 6월 5일 오후 12:33 UTCmonitoring

   We're currently experiencing an issue with our LinkedIn integration that may affect customers using RSC (Recruiter System Connect) features. You may notice delays in data syncing to Pinpoint, including in-mail messages and candidate exports. This will only impact customers using LinkedIn RSC features only. Core Pinpoint functionality is unaffected. We've identified the root cause and have a fix ready to deploy. We expect to roll this out this evening (UK time).

2. 2026년 6월 6일 오전 12:30 UTCresolved

   This incident has been resolved.

1. 2026년 5월 13일 오전 6:29 UTCinvestigating

   We are currently experiencing a service disruption caused by an issue with our primary database. While users are still able to log in and view data in Pinpoint, some actions that involve saving or updating information are temporarily unavailable. Our team has identified the root cause and is actively working to restore full functionality. We will provide further updates as the situation progresses.

2. 2026년 5월 13일 오전 6:54 UTCmonitoring

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

3. 2026년 5월 13일 오전 6:58 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026년 5월 13일 오전 7:04 UTCresolved

   This incident has been resolved.

5. 2026년 5월 13일 오후 2:16 UTCpostmortem

   **Duration:** Approximately 4 hours of intermittent disruption \(03:00 – 06:51 UTC\), with two distinct impact windows. ## What Happened Pinpoint experienced an unexpected service disruption in the early hours of 13 May. The incident had two impact windows: an initial period of unavailability between approximately 03:00 and 04:00 UTC, and a follow-on period between approximately 05:39 and 06:51 UTC during which users attempting to modify certain types of records \(predominantly scorecard submissions\) encountered errors. No data was lost or corrupted, and no background jobs were delayed. ## Timeline \(UTC\) * 03:00 Initial impact begins; application unavailable. * 04:00 Initial impact resolves; engineering team investigating. * 05:39 Second impact window begins; errors on a subset of record updates. * 06:29 Status page warning posted. * 06:51 Second impact window resolves. * 07:04 Incident marked as resolved. ## Why It Happened The disruption was caused by an unexpected interaction between a routine internal database operation and an active background process. This combination of events is an outlier we had not previously encountered or anticipated. The root cause has been fully investigated and is understood. ## What We're Doing About It * **Additional Monitoring** We have put additional monitoring in place to detect this specific class of interaction much earlier, before it can cause customer impact. * **Increased Database Capacity** We have provisioned additional database capacity to further reduce the likelihood of recurrence. _We sincerely apologise for the disruption and appreciate your patience._

1. 2026년 3월 19일 오후 12:01 UTCinvestigating

   We’re aware of a current issue causing 503 errors and are investigating urgently.

2. 2026년 3월 19일 오후 12:21 UTCresolved

   This has been resolved. A full post mortem will follow soon.

3. 2026년 3월 19일 오후 1:37 UTCpostmortem

   **Date:** 19 March 2026 **Duration:** Approximately 35 minutes \(11:46 to 12:21 UTC\). ### What Happened Pinpoint experienced a service outage beginning at approximately 11:46 UTC on 19 March. Users were unable to access the platform and received 503 errors. Full service was restored by approximately 12:21 UTC. No data was lost or corrupted. ### Timeline \(UTC\) * **11:46** - Automated monitoring alerts triggered for service unavailability. * **11:47** - Engineering team began investigating. * **12:01** - Status page updated to reflect the incident. * **12:10** - Root cause identified as a database firewall misconfiguration introduced during an infrastructure change. * **12:20** - Fix applied; service restored. * **12:21** - Incident marked as resolved. ### Why It Happened During an infrastructure configuration change, a database firewall rule was inadvertently applied with an overly restrictive scope. This prevented our application servers from connecting to the primary database, causing all requests to fail. ### What We're Doing About It * **Immediate fix:** The firewall configuration has been corrected and verified. * **Hardening:** We are making production database firewall rules explicitly immutable and tightening API token permissions to prevent unexpected firewall modifications. We sincerely apologise for the disruption and appreciate your patience.

1. 2026년 3월 18일 오전 8:22 UTCidentified

   We are aware of an issue affecting the resume/CV preview within the platform. Resumes may appear blank or display a browser blocking message when viewed inline. **Downloading resumes is unaffected** — you can continue to access candidate resumes using the download button. Our team has identified the cause and a fix is being deployed soon. We expect normal service to be restored shortly. We apologise for the inconvenience and will update this page once the fix is live.

2. 2026년 3월 18일 오전 9:16 UTCmonitoring

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

3. 2026년 3월 18일 오전 10:02 UTCresolved

   > What happened Users were unable to preview CVs and cover letters within the platform. The preview area appeared blank or showed a "blocked by browser" message. Downloading resumes continued to work normally throughout. > What caused it A security update was deployed overnight to protect admins from potentially harmful files. While the protection worked as intended, it had an unintended side effect - it also prevented the resume preview from loading correctly in all browsers. > What we did Identified the cause within minutes of being alerted Deployed a fix to restore normal resume previewing > What's next We have applied an alternative security protection using a different approach that doesn't affect the preview.

1. 2026년 3월 3일 오전 10:47 UTCresolved

   Component: Pinpoint → Partial Outage Investigating - 05:00 UTC: > We are aware that some users may be unable to perform actions that involve saving or updating data. Our engineering team is actively investigating. Identified - 06:45 UTC: > The auto-scaling configured on our primary database infrastructure failed to provision additional storage in response to increased load. As a result, the database entered read-only mode, preventing write operations. We are provisioning additional storage to restore full functionality. Monitoring - 06:57 UTC: > Additional storage has been provisioned and write operations have been restored. Our team is monitoring to confirm full stability across all services. Resolved - 07:01 UTC: > The issue has been fully resolved and all services are operating normally. We apologise for the disruption and are reviewing our auto-scaling configuration to prevent recurrence.

1. 2026년 2월 12일 오후 2:05 UTCinvestigating

   We are currently experiencing a full service outage. All requests are returning 503 errors. Our engineering team is actively investigating and working to restore service as quickly as possible.

2. 2026년 2월 12일 오후 2:09 UTCinvestigating

   We are currently experiencing a major service disruption. Most requests are returning 503 errors, though limited service is available through a single server. Our engineering team is actively investigating and working to restore full capacity.

3. 2026년 2월 12일 오후 2:18 UTCidentified

   We are continuing to recover from a service disruption that caused 503 errors. Additional servers have been brought back online and service is improving. Our engineering team is working to restore full capacity.

4. 2026년 2월 12일 오후 2:26 UTCmonitoring

   Service has been mostly restored following an earlier outage. Some users may experience minor intermittent slowness. Our team continues to monitor as we return to full normal operation.

5. 2026년 2월 12일 오후 2:46 UTCmonitoring

   Service has stabilised following the earlier outage. Our servers are back online and performing as expected. Our team will continue to monitor the situation.

6. 2026년 2월 12일 오후 3:02 UTCresolved

   The earlier service outage has been resolved. Our servers are back online and operating normally. We apologise for the disruption and are taking steps to prevent this from recurring.

7. 2026년 2월 13일 오전 10:53 UTCpostmortem

   **Date:** 12 February 2026 **Duration:** Approximately 30 minutes \(14:00 - 14:35 UTC\), with a brief secondary disruption during recovery. ### What Happened Pinpoint experienced a service outage beginning at approximately 14:00 UTC on 12 February. Most users were unable to access the platform and received 504 timeout errors, though partial capacity meant some requests were still being served. Full service was restored by approximately 14:35 UTC. Some outbound emails were delayed due to background workers also being affected. All queued emails were delivered by approximately 16:15 UTC. No data was lost or corrupted. ### Timeline \(UTC\) * **14:00** - Automated monitoring alerts triggered for service unavailability. * **14:02** - Engineering team began investigating. * **14:08** - Root cause identified as a network configuration conflict introduced by a third-party infrastructure provider. * **14:20** - Initial fix applied; service stabilising. * **14:22** - Third-party provider's automation reinstated the conflicting configuration, causing a brief secondary disruption. * **14:30** - Fix reapplied with additional safeguards to prevent recurrence. * **14:35** - Full service restored. * **16:15** - All delayed outbound emails delivered. ### Why It Happened A third-party infrastructure provider applied an automated network configuration change to our servers. The change was overly broad and conflicted with our own networking configuration, causing the majority of inbound traffic to be dropped. During initial recovery, the provider's automation re-applied the conflicting change before we implemented stronger protections. ### What We're Doing About It * **Immediate Safeguards:** Protections are in place to prevent this specific change from affecting our infrastructure again. * **Removing the Dependency:** We are accelerating work to bring the affected networking functionality fully in-house, removing the third-party dependency entirely. We sincerely apologise for the disruption and appreciate your patience.

1. 2025년 11월 28일 오후 12:03 UTCinvestigating

   We’re currently investigating reports of missing records (including interviews, comments, messages and scorecards) as a result of the earlier reported infrastructure incident. The platform is operating normally, and no further service disruption is expected. Our team is actively working to identify and restore the affected data. We’ll provide updates as soon as we have more information. Thank you for your patience.

2. 2025년 11월 30일 오후 7:30 UTCresolved

   We have identified the missing records within the platform and restored the affected data. If you have any questions or require assistance please reach out to our support team via the in-app chat function

1. 2025년 11월 28일 오전 10:33 UTCidentified

   We are currently experiencing platform issues affecting candidate index pages as well as some actions across the platform including editing or deleting certain types of records (e.g cancelling and re-scheduling candidate interviews). This follows a planned infrastructure update completed last night. We’ve identified some unexpected issues related to the change and are implementing adjustments to ensure full stability. This work involves a few coordinated steps and is expected to take around 30 minutes. We’re treating this with the highest priority and will continue to provide updates. Thank you for your patience, and we apologize for the disruption.

2. 2025년 11월 28일 오전 11:31 UTCresolved

   This incident has been resolved. > What happened Following a planned infrastructure update last night, some customers experienced errors when performing certain actions on the platform, particularly around candidate pages and interview scheduling. We identified the root cause and restored full service by reverting to our previous database infrastructure. > Current status The platform is now fully operational. All features are working normally. > Data impact Due to an issue between both database providers when we restored service, there's a short window (between 10:16 and 10:57 UTC this morning) where some changes made on the platform may not yet be reflected. No data has been lost, we have complete records of everything that happened during this window and are working to restore any affected changes to the live system. The status of data reconciliation is being tracked here: https://status.pinpoint.support/incidents/9v65gddb3y1n > A note on our recovery standards We maintain internal Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) as part of our commitment to platform reliability. The 41-minute data gap from this incident falls outside the standards we set for ourselves, and we take that seriously. While no data was lost, we're treating this as a priority learning for our infrastructure processes going forward, and feedback for our vendors and their practices. A full post-mortem will follow on Monday.

1. 2025년 7월 30일 오전 11:22 UTCmonitoring

   Earlier today, our platform experienced a temporary disruption due to a sudden and highly unusual surge in external traffic, significantly beyond anything we’ve seen before. This caused intermittent 503 errors and degraded performance for approximately 15 minutes. We acted quickly to contain the issue and restore full service, including scaling our infrastructure and working closely with our edge network provider to bolster caching and traffic protection systems. Service is now fully operational and stable. We’re continuing to implement further safeguards to ensure that similar patterns of abnormal traffic cannot affect platform availability in the future. While today’s disruption was limited in scope and duration, we recognise the importance of uninterrupted access to Pinpoint - and are treating this with the seriousness it deserves. We’ll continue monitoring closely and share any further updates here as needed.

2. 2025년 7월 30일 오후 2:36 UTCresolved

   This incident has been resolved.

1. 2025년 7월 22일 오전 6:38 UTCinvestigating

   We experienced an unexpected outage with our primary database between 01:50 22nd July & 03:40 22nd July. Service has now been restored using a backup. However, the backup we restored from was approximately 24 hours old, which means any data written to the system between 01:00 BST 21st July and 01:00 22nd July is currently missing. We are in the process of restoring our database to a more recent back-up snapshot (from 01:00 BST 22nd July) so that the aforementioned missing data from yesterday is restored. Once this second restore has finished, any records created since 01:00 BST 22nd July will be missing from the system. We are actively working to ensure that this small amount of missing data from today is then also restored. All missing data is recoverable, it currently just exists in separate database back-ups. Once our second restore finishes the final part of our restoration involves reconciling the two back-ups. This process is complex and may take some time to complete. We will continue to provide further updates as progress continues. Service Availability: Fully restored. Data: Any records created or updated during the affected period (last 24 hours) are not yet visible. Next Steps: We are working to recover and restore this missing data. We sincerely apologise for the inconvenience this has caused and appreciate your patience while we work to fully resolve the issue.

2. 2025년 7월 22일 오전 8:07 UTCinvestigating

   Database Outage Update: Recovery in Progress, Data Backfill Required We are still in the process of restoring our database to a more recent back-up snapshot (from 01:00 BST 22nd July) so that the aforementioned missing data from yesterday is fully restored. Once this second restore has finished, any records created since 01:00 BST 22nd July will still be missing from the system. We will then proceed with restoring this small amount of missing data from today. All missing data is recoverable, it currently just exists in separate database back-ups. Once our second restore finishes the final part of our restoration involves reconciling the two back-ups. Service Availability: Fully restored. Data: Any records created or updated during the affected period (last 24 hours) are not yet visible. Next Steps: We are working to recover and restore this missing data. We sincerely apologise for the inconvenience this has caused and appreciate your patience while we work to fully resolve the issue.

3. 2025년 7월 22일 오전 8:57 UTCinvestigating

   Database Outage Update: Recovery in Progress, Data Backfill Required We have now restored our database to a more recent back-up snapshot (from this morning at 01:00 BST, 22nd July). Any and all records that were in any way created or modified yesterday (from 01:00 BST, 21st July onwards) are now visible once again in the system. We are now working to restore all data that was created or modified from 01:00 BST 22nd July (early hours of this morning) up until the point we restored our database just moments ago. All missing data is recoverable, it currently just exists in separate database back-ups, and we are working as fast as we can to reconcile the two back-ups. Service Availability: Fully restored. Data: Any records created or updated during the affected period (last 24 hours) are now visible. Next Steps: We are working to recover and restore data that was created or modified since 01:00 BST, July 22nd this morning. Important Note on Performance: - During this recovery process, system performance will be slower than usual. This is because we are temporarily running all operations through a single database while we work to fully restore normal infrastructure. - We are also experiencing significant slowdowns with the processing of all custom reports We sincerely apologise for the inconvenience this has caused and appreciate your patience while we work to fully resolve the issue.

4. 2025년 7월 22일 오전 10:12 UTCinvestigating

   Database Outage Update: Recovery in Progress, Data Backfill Required We are now working to restore all data that was created or modified from 01:00 BST 22nd July (early hours of this morning) up until the point we restored our database at 08:57 BST today. All missing data is recoverable, it currently just exists in separate database back-ups, and we are working as fast as we can to reconcile the two back-ups. Service Availability: Fully restored. Data: Any records created or updated during the affected period (last 24 hours) are now visible. Next Steps: We are working to recover and restore data that was created or modified since 01:00 BST, July 22nd this morning. Important Note on Performance: - We have returned to normal database infrastructure, meaning the previously reported performance slowdowns should begin to improve load is shared across multiple databases. - We are also experiencing significant slowdowns with the processing of all custom reports We sincerely apologise for the inconvenience this has caused and appreciate your patience while we work to fully resolve the issue.

5. 2025년 7월 22일 오후 12:29 UTCinvestigating

   Database Outage Update: Recovery in Progress, Data Backfill Required We are still working on restoring all data that was created or modified from 01:00 BST 22nd July (early hours of this morning) up until the point we restored our database at 08:57 BST today. All missing data is recoverable, it currently just exists in separate database back-ups, and we are working as fast as we can to reconcile the two back-ups. Service Availability: Fully restored. Data: Any records created or updated during the affected period (last 24 hours) are now visible. Next Steps: We are working to recover and restore data that was created or modified since 01:00 BST, July 22nd this morning. We sincerely apologise for the inconvenience this has caused and appreciate your patience while we work to fully resolve the issue.

6. 2025년 7월 23일 오전 6:20 UTCinvestigating

   Database Outage Update: Recovery in Progress, Data Backfill Required Most of the data that was created or modified between 01:00 BST 22nd July and 09:00 BST 22nd July has been restored and is now visible in the platform. This includes all records with the exception of new job applications, which we are currently processing. We expect that data to be restored within the next hour. Service Availability: Fully restored. Data: Any records created or updated during the affected period (between 01:00 BST 22nd July and 09:00 BST 22nd July) with the exception of job application data is now visible in the system. Next Steps: We are now restoring remaining job application data that was created or modified between 01:00 BST, July 22nd and 09:00 BST. We sincerely apologise for the inconvenience this has caused and appreciate your patience while we work to fully resolve the issue.

7. 2025년 7월 23일 오전 7:07 UTCresolved

   Database Outage Update: Recovery in Progress, Data Backfill Required All remaining data that was created or modified between 01:00 BST 22nd July and 09:00 BST 22nd July has been restored and is now visible in the platform. Service Availability: Fully restored. Data: Any records created or updated during the affected period (between 01:00 BST 22nd July and 09:00 BST 22nd July) is now visible in the system. We sincerely apologise for the inconvenience this has caused and appreciate your patience while we work to fully resolve the issue.

1. 2025년 7월 22일 오전 1:33 UTCinvestigating

   We are investigating an outage with our primary database that is affecting the whole platform.

2. 2025년 7월 22일 오전 2:40 UTCmonitoring

   A fix has been implemented and we are monitoring the the application. You may experience degraded performance

3. 2025년 7월 23일 오전 8:29 UTCresolved

   The outage has been resolved, and all services are operational. A full post-mortem will follow.

4. 2025년 7월 23일 오전 8:29 UTCpostmortem

   **Date:** 22 July 2025 **Duration:** 8 hours 34 minutes \(01:07 – 09:41 BST\) ### **What Happened** Pinpoint experienced a significant service disruption affecting our primary database, admin/API services, and careers site from 1:07 AM to 9:41 AM BST on 22 July. During this period, customers experienced complete service unavailability for approximately 2 hours and 45 minutes, followed by functionality with temporarily outdated data until full restoration was completed. ### **Timeline \(BST\)** * **01:07** – Service disruption began; database connectivity issues detected * **01:09** – Emergency response initiated; services marked as unavailable * **01:45** – Initial database restoration commenced * **03:45** – Services restored with backup data from the previous day * **09:21** – Second restoration initiated with more recent backup * **09:41** – Full service restoration completed with current data * **10:00\+** – Performance optimisation measures implemented * **23:50\+** – Restoration of some delayed data from 3:00-9:41 AM ### **Why It Happened** The incident occurred during a trial of a new database vendor's migration service. While testing their system, operations intended for a test environment were unexpectedly redirected to our production database, resulting in the unintended removal of data. The database vendor's system includes advanced features designed to help companies migrate data safely. However, the behaviour of these features during our testing phase was not clearly indicated in their interface. This led to test operations affecting our live production data instead of remaining isolated in the test environment, where they belonged. ### **What We're Doing About It** * **Immediate Recovery Completed:** All services have been fully restored. We are working to restore data created during the early morning hours of Tuesday. * **Enhanced Monitoring:** We are implementing additional safeguards to detect and prevent unintended database operations, including alerts for any bulk data modifications. * **Vendor Collaboration:** We are working closely with the database vendor to improve their user interface and documentation, ensuring that system behaviour is communicated during all operational phases. We apologise for this disruption to your service. We understand the critical nature of your recruitment processes and the impact this may have had on scheduled interviews and daily operations.

1. 2025년 6월 26일 오후 3:16 UTCinvestigating

   We're currently investigating an issue affecting the Candidate Search functionality. Users are experiencing errors with no results returned when attempting to search for candidates. This only affects the All Candidates page. Our engineering team is actively working to identify the root cause and restore full service as quickly as possible. We’ll provide an update as soon as more information is available. We apologise for the inconvenience and appreciate your patience.

2. 2025년 6월 26일 오후 3:21 UTCidentified

   We've identified the root cause of the Candidate Search issue and have a fix prepared. The patch will be deployed within the next 60 minutes. We'll continue to monitor progress closely and provide an update once the fix is fully in place and search functionality is confirmed to be stable. Thank you for your continued patience.

3. 2025년 6월 26일 오후 4:40 UTCmonitoring

   We’ve deployed a fix for the candidate search issue and candidate search functionality has been restored. Our team is continuing to monitor the system closely.

4. 2025년 6월 26일 오후 6:54 UTCresolved

   This incident has been resolved.

1. 2025년 5월 1일 오후 2:31 UTCinvestigating

   We are currently investigating the issue.

2. 2025년 5월 1일 오후 2:45 UTCinvestigating

   We have identified an issue with our primary database cluster and are working with our infrastructure provider to determine the root cause.

3. 2025년 5월 1일 오후 3:04 UTCidentified

   The issue has been identified and a fix is being implemented

4. 2025년 5월 1일 오후 3:21 UTCmonitoring

   A fix has been rolled out. All services are currently operational and we are continuing to monitor.

5. 2025년 5월 1일 오후 4:19 UTCresolved

   This has been resolved. A full post mortem will follow soon.

6. 2025년 5월 2일 오후 3:21 UTCpostmortem

   **Date:** 1 May 2025 **Duration:** 50 minutes \(15:11 – 16:01\) ### **What Happened** Pinpoint experienced a complete admin/API service outage and a partial careers site outage, lasting from 3:11 PM to 4:01 PM BST on 1 May. During this 50-minute window, users could not access the platform and were presented with error messages when attempting to log in or use any part of the service. ### **Timeline \(BST\)** **15:11** – Monitoring alerts triggered for a service interruption. **15:13** – Root cause identified as database connection failures. **15:20** – Contacted managed database provider; issue confirmed as infrastructure-related. **15:45** – Provider identified a disk controller failure and began working on remediation; we started a cluster migration ourselves in case of further provider issues. **15:50** – We escalated the issue with the provider due to a lack of failover activation. **16:00** – Provider migrated the database to new hardware; connectivity restored. **16:01** – Full service restoration confirmed across all components. ### **Why It Happened** The root cause was a hardware failure on the part of our managed database provider. Specifically, a critical disk controller in their storage infrastructure failed, resulting in incorrect disk space reporting at the database level. This led our primary database instance to believe it had run out of storage space, and it began rejecting all connections, including those from our application servers. Although our agreement with the provider includes premium-grade redundancy and automated failover mechanisms, these safeguards failed to activate due to an undetected fault in their failover detection logic. As a result, traffic was not redirected to the standby replica, and manual intervention from their engineering team was required to restore normal operations. Unfortunately, this intervention took longer than acceptable, contributing to the total duration of the outage. ### **What We’re Doing About It** * **Hardware Migration Completed:** Our provider has successfully migrated our primary database to a new, healthy hardware environment. Service has been fully restored and is operating normally. * **Evaluating New Providers:** We chose our current provider for their strong reputation and reliability, but in light of this incident, we’re reassessing our options to ensure our infrastructure meets the highest standards of resilience and support. * **Working with Current Provider:** We’re working with our current provider’s engineering and account teams to understand why their failover system did not function as promised and to ensure such a failure does not recur prior to us migrating to an alternative provider. We sincerely apologise for the disruption and appreciate your patience as we work to strengthen our platform's stability.

1. 2025년 3월 18일 오전 10:05 UTCinvestigating

   During routine maintenance to our search infrastructure, an update to the indexed data did not apply correctly, resulting in the inability to search for job applications in the admin application.

2. 2025년 3월 18일 오전 10:05 UTCidentified

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

3. 2025년 3월 18일 오전 10:58 UTCmonitoring

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

4. 2025년 3월 18일 오후 12:18 UTCresolved

   This incident has been resolved.

1. 2025년 2월 16일 오후 4:40 UTCidentified

   During routine maintenance to our search infrastructure, an update to the indexed data did not apply correctly, resulting in the inability to search for some resources in the admin application, such as candidates.

2. 2025년 2월 17일 오전 10:41 UTCidentified

   We have identified the cause of the issue and are steadily rolling out the fix.

3. 2025년 2월 18일 오전 11:02 UTCidentified

   We have restored functionality to 95% of searchable resources and continue to roll out the fix for the remainder.

4. 2025년 2월 18일 오후 4:29 UTCresolved

   We have finished rolling out the fix for our search backend, and all search components are 100% functional again.

5. 2025년 2월 27일 오후 3:32 UTCpostmortem

   We apologise for last week’s disruption to our typically swift and flexible search functionality. This was caused by routine maintenance of our search infrastructure over the weekend of February 15th and 16th, which encountered unexpected issues during data migration. The resolution of the issue was further complicated by the larger-than-anticipated size of some datasets and the difficulty of certain technical processes in keeping up. On Tuesday, February 18th, we also deployed several bug fixes that sped up our data processing and ensured that search failures did not make the UI unusable in some circumstances. Rest assured, the team has thoroughly reviewed the incident, and changes are already in the pipeline to prevent similar occurrences.

1. 2024년 9월 16일 오후 12:59 UTCinvestigating

   We're experiencing an intermittent delay in requests being completed and are currently looking into the issue.

2. 2024년 9월 16일 오후 1:27 UTCinvestigating

   The platform is currently stable, however there is currently a delay in background task processing whilst we continue to investigate the root cause.

3. 2024년 9월 16일 오후 2:46 UTCmonitoring

   The platform is stable, and background task processing has returned to normal levels. We are continuing to monitor our systems.

4. 2024년 9월 16일 오후 4:14 UTCresolved

   This incident has been resolved.

1. 2023년 8월 9일 오전 11:40 UTCidentified

   We are currently experiencing an intermittent network issue due through our hosting provider, Digital Ocean. We are currently tracking the issue and will provide further updates as more become available. The issue can be tracked here: https://status.digitalocean.com/incidents/q4b09b022nmh

2. 2023년 8월 9일 오후 12:12 UTCidentified

   There is currently an ongoing networking issue affecting all of our hosting providers services. From our investigation we can see that this is preventing some requests from being made to and from the Pinpoint servers.

3. 2023년 8월 9일 오후 12:15 UTCmonitoring

   Our own monitoring systems inform us that we are no longer experiencing any network issues. We are continuing to monitor the situation closely and will provide an update in due course.

4. 2023년 8월 9일 오후 12:26 UTCidentified

   We have just seen a reoccurrence of the issue.

5. 2023년 8월 9일 오후 3:07 UTCmonitoring

   Our hosting provider has rolled out a fix and is monitoring to ensure stability.

6. 2023년 8월 9일 오후 4:03 UTCresolved

   Our hosting provider has confirmed full resolution of the issue impacting network connectivity.

1. 2022년 11월 6일 오후 10:16 UTCresolved

   Web servers are currently not configured to serve requests.

2. 2022년 11월 6일 오후 10:17 UTCpostmortem

   As part of routine maintenance we were installing security updates on our web servers. The process for this involved systematically removing them from serving requests, installing the updates and then adding them back into the load balancer so that they could continue to process requests. A configuration issue lead to updated servers not being added back into the load balancer. Our development team were quick to recognise and rectify the issue. Our internal processes have changed in order to prevent this happening again in the future.