Service Incidents

Last update - 1:18 PM (ET)
The issue is now resolved.

Initial report - 1:04 PM (ET)
We observed slowdowns on the Folks platform, primarily affecting login.

Our technical teams have been mobilized to identify the cause and implement fixes.

Thank you for your understanding.

Last update - 16:54 (ET)
Following our analysis, we were able to trace the issue to an internal task progress tracking mechanism. Status validation was generating a high load, which led to an overload when the service was restarted.

Although the queue was managed and reset, we identified the contributing factors and implemented the necessary changes to prevent recurrence.

Update - 2:02 PM (ET)
Login issues have been resolved. Certain requests causing slowdowns have been identified and are currently being addressed. Overall performance is improving.

Update - 12:45 PM (ET)
Improvements have been observed since this morning, but some users are still experiencing slowdowns. The team is continuing its investigation to identify the root cause and fully stabilize the situation.

Update - 9:25 AM (ET)
The situation has partially improved following actions taken by the development team. However, some slowdowns persist and continue to be reported by certain clients.

Initial report - 8:30 AM (ET)
We observed slowdowns on the Folks platform, primarily affecting navigation and, in some cases, login.

Our technical teams were mobilized to identify the cause and implement fixes. Further updates will be shared as needed.

Thank you for your understanding.

Last update - 3:50 PM (ET)
We have received confirmation that sending data to Nethris is functional again.

Update - 1:50 PM (ET)
Our teams have confirmed that Folks is indeed sending authentication requests, but these are not successful on the payroll system side.

During the authentication attempt, an abnormally long delay ends with a 504 error (timeout).

Temporarily, it appears that the following systems are affected:
- Nethris

Initial report - 10:30 AM (ET)
During the employee export, an error originating from the Content Delivery Network (CDN) prevented the generation and sending of the file.
In other words, the connection with the external service could not be established.

Example of error displayed in Folks:

2025-09-XX 10:18:00 - Login…
2025-09-XX 10:20:01 - An error occurred while processing your request.
Reference #221.e962a17.XXXXXXXXXXXXXXXXXXX
https://errors.edgesuite.net/221.e962aXXXXXXXXXXXXXXXX

Last update - 4:00 PM (ET)
The issue has now been resolved.

Initial report - 11:30 AM (ET)
You may currently see this message when clicking on the link to our classic ATS in Folks.

Our development team is working to resolve the issue as quickly as possible.

While waiting for a full resolution, we invite you to use the following link (entering your account name) to access your ATS space:

https://folkshr.app/cvirtuose/[account-name]/fr/recruiter/login

If you do not know your account name, right-click + Inspect on the following box in your company profile.

Las update - 10:15 (EST)
The ATS will be back online within 30 minutes. Investigations will be carried out to understand the cause of the problem.

Initial report - 9:30 (EST)
We are currently experiencing technical difficulties preventing users from logging in to Glow.

Our technical teams are actively investigating and working to identify solutions to resolve the issue. We will share updates as soon as possible.

Thank you for your understanding.

Last update - 4:09 PM (EST)
The situation has been resolved.

Update - 3:17 PM (EST)
Loading performance appears to be slightly improving.

Update - 2:20 PM (EST)
The technical team will switch Folks to an alternative service in an attempt to bypass the issue.

Initial report - 2:00 PM (EST)
We are currently experiencing moderate to significant delays in accessing our platform.

While the exact cause has not yet been confirmed, early indications suggest a link to a third-party service: unpkg.com, a content delivery network (CDN) used to load files from npm packages.

Our technical teams are actively investigating and working to identify solutions to stabilize loading speeds. We will share updates as soon as possible.

Thank you for your understanding.