Skip to main content

Technical Incidents

  • Last updated:

Current Status

365Talents platform is working properly with no known production incident.

For any inquiry, please contact support@365talents.com.

Previous Incidents

This section lists previous incidents and is available for reference. This page is up-to-date from June 3rd 2026.

2026-03-06

  • Incident Description: Platforms not available to all users.
  • Details: An activity spike on our infrastructure node pools saturated their resources, preventing them from handling user requests. As a result, users were unable to access their platform.
  • Timeline:
  • Incident Start: June 3rd 2026, 10h42 Paris time
  • Incident end: June 3rd 2026, 10h52 Paris time
  • Incident restart : June 3rd 2026, 11h20 Paris time
  • Incident end : June 3rd 2026, 11h25 Paris time

  • Root Cause : An activity spike on our infrastructure node pools saturated their resources, preventing them from handling user requests. An automated remediation triggered a reboot of the affected nodes, however a dysfunction prevented them from rejoining the pool once restarted. The issue then propagated across all nodes, causing a full service outage.

    Remediation applied: vertical scale-up of node instances, doubling their capacity to prevent further resource saturation.

    Ongoing: investigation into the root cause of the activity spike and the node rejoin failure. The situation is being actively monitored.

2024-09-26

  • Incident Description: Performance issues on all production platforms
  • Details: The performance of the platforms are currently degraded resulting in the application being slow to respond.
  • Timeline:
  • Incident Start: September 26th 2024, 15:40
  • 17:23 Update : Performance is coming back to normal since 17:05. 365Talents continues monitoring the situation.
  • Incident End: September 26th 2024, 17:49
  • Root Cause: Physical unavailability of some Azure datacenter components that led to to extreme slowness and timeouts, notably on Microsoft Azure Kubernetes Service.

2024-09-20 & 2014-09-23

  • Incident Description: Out of memory issue
  • Details: Platform was unreachable intermittently during the incident and the maintenance page was displayed.
  • Timeline:
  • First incident
    • Incident Start: September 20th 2024, 10:00
    • Incident End: September 20th 2024, 11:26
  • Second incident
    • Incident Start: September 23rd 2024, 10:00
    • Incident End: September 23rd 2024, 10:20
  • Root Cause: A component of our platform was overloaded with scheduled background load and ran out of memory.

2023-04-19

  • Incident Description: Bad Performance on User Profile & Opportunities
  • Details: User profile and opportunities pages performance were degraded for the duration of the incident, resulting in few cases in unavailable pages. No loss of data occurred. Other features worked perfectly for the whole incident duration. A mitigation has been deployed at 4pm, disabling a feature on user profiles, called "conversational suggestions", which resulted in back-to-normal performance across the whole application. Moreover, profile completion rate ("Top Profile", "Good profile", etc.) was displayed as "Empty profile" for every user, which also impacted the "Completed profiles" indicator on the dashboard.\
    All features are now enabled, including conversational suggestions. Profile completion rates on dashboards are now correct.
  • Timeline:
  • Incident Start: April 19th, 12:11
  • Incident Mitigated: April 19th, 16:10
  • Incident End: April 21st, 11:55
  • Root Cause: Micro-service performance related issue. The service providing user profiles to the conversational suggestions service sent too much data due to a technical update, which resulted in bad performance for those two services. This situation escalated to other components in the system, resulting in bad performance across other areas of the platform.

2023-03-15

  • Incident Description: Matching Explanations Unavailable
  • Details: Matching explanations were unavailable for the duration of the incident, impacting all pages using this feature (opportunities "suggested for you", "other" opportunities pages, "staffing an opportunity" and "project a collaborator"). No loss of data occurred. Other features worked perfectly for the whole incident duration.
  • Timeline:
  • Incident Start: March 15th, 9:00
  • Incident End: March 15th, 12:10
  • Root Cause: The service providing the feature experience an outage due to a technical deployment issue, now fixed.