Anthology incident

Connect ApplyYourself and AppReview applications down-Global

Critical Resolved View vendor source →

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

Started
May 22, 2025, 03:03 PM UTC
Resolved
Jun 12, 2025, 09:07 PM UTC
Duration
21d 6h
Detected by Pingoru
May 22, 2025, 03:03 PM UTC

Update timeline

  1. investigating May 22, 2025, 03:03 PM UTC

    Our technical team has identified an issue with the underlying infrastructure supporting the Connect, AY, and AR applications. To resolve this, we are temporarily taking these applications 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.

  2. identified May 22, 2025, 04:34 PM UTC

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

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

  4. identified May 22, 2025, 06:56 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.

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

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

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

  7. resolved Jun 12, 2025, 09:07 PM UTC

    This incident has been resolved.