Service Incidents

Resolution
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.

Update – 10h15 (EST)

Glow will be back online within 30 minutes. Investigations will be carried out to understand the cause of the problem.

Initial Report – 9h30 (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.

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.