Anthology incident

ApplyYourself (AY) application down-Global

Critical Resolved View vendor source →

Anthology experienced a critical incident on May 22, 2025, lasting 11h 25m. The incident has been resolved; the full update timeline is below.

Started
May 22, 2025, 12:52 PM UTC
Resolved
May 23, 2025, 12:17 AM UTC
Duration
11h 25m
Detected by Pingoru
May 22, 2025, 12:52 PM UTC

Update timeline

  1. investigating May 22, 2025, 12:52 PM UTC

    Our engineers began investigating an issue where users are unable to access AY application. this is impacting US region. The site does not load, and users can experience errors. We will provide update as soon as more information becomes available.

  2. investigating May 22, 2025, 01:22 PM UTC

    Our technical team is still investigating the AY application availability issue. We will provide a new update as soon as it is available.

  3. investigating May 22, 2025, 02:12 PM UTC

    Our dedicated team is actively addressing this issue, employing all measures to swiftly diagnose and rectify the issues. We understand the importance of uninterrupted service and sincerely apologize for any inconvenience this might cause.

  4. identified May 22, 2025, 02:57 PM UTC

    Our technical team has identified an issue with the underlying infrastructure supporting the AY application. To resolve this, we are temporarily taking the application offline across all regions for approximately 60 minutes. We understand the importance of seamless service and appreciate your patience as we work to restore full functionality. An update will be provided within the next hour or sooner.

  5. identified May 22, 2025, 04:35 PM UTC

    We have identified the issue and continue to work to resolve this issue as quickly as possible and No ETA for now

  6. identified May 22, 2025, 05:34 PM UTC

    The cause of the issue has been identified. We are actively working on multiple parallel paths to mitigate this issue. We will provide you with another update by 3:00 PM EDT or as soon as more information becomes available.

  7. identified May 22, 2025, 06:57 PM UTC

    Our engineers are continuing to work towards a fix for this issue. At this time, customers may still experiencing the issue. We will provide another update by 5:00 PM EDT or as soon as more information becomes available.

  8. identified May 22, 2025, 08:57 PM UTC

    Several of the affected systems have recovered and work continues with the remaining environments that are still experiencing the issue. We will provide you with another update by 6:00 PM EDT or as soon as more information becomes available.

  9. monitoring May 22, 2025, 10:02 PM UTC

    Our technical Team has fixed the issue and we are monitoring the results.

  10. resolved May 23, 2025, 12:17 AM UTC

    This incident has been resolved and it was observed that clients are operating normally.