When I Work experienced a major incident on May 23, 2025 affecting Web App and API and 1 more component, lasting 16d 23h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 23, 2025, 03:58 PM UTC
We are aware of issues impacting the app and are investigating further. We will provide an update here as soon as we have additional information.
- monitoring May 23, 2025, 09:59 PM UTC
We continue to see improvements from the fixes we have implemented and are continuing to monitor.
- investigating May 24, 2025, 02:34 AM UTC
We are aware of issues impacting the app and are investigating further.
- monitoring May 24, 2025, 03:46 AM UTC
A fix has been implemented and we continue to monitor.
- investigating May 24, 2025, 01:17 PM UTC
We are experiencing intermittent performance issues with logging in, creating/publishing shifts, time off requests, and clocking in/out. We are investigating the root cause of the inconsistent app performance.
- investigating May 24, 2025, 10:27 PM UTC
We are still experiencing intermittent performance issues with logging in, creating/publishing shifts, time off requests, and clocking in/out. We will provide more updates when we have them.
- investigating May 25, 2025, 01:15 PM UTC
We are seeing improvements with the intermittent performance issues and continue to investigate.
- investigating May 25, 2025, 10:08 PM UTC
We are still seeing improvements with the intermittent performance issues and continue to keep a close eye.
- investigating May 26, 2025, 01:15 PM UTC
We continue to see improvements with the intermittent performance issues. If you are experiencing an issue, please contact our Care team for further troubleshooting.
- investigating May 27, 2025, 01:15 PM UTC
We continue to see improvements. If you are experiencing an issue, please contact our Care team for further troubleshooting.
- investigating May 27, 2025, 10:09 PM UTC
We continue to see improvements from our releases. If you are experiencing an issue with logging in or any other unintended behavior, please contact our Care team for further troubleshooting.
- investigating May 28, 2025, 01:30 PM UTC
Performance has improved for the majority of customers. If you are experiencing an issue, please get in touch with our Care team for further investigation.
- investigating May 28, 2025, 09:28 PM UTC
Performance has improved for the majority of customers. If you are experiencing an issue with logging in or loading, retry the action a few minutes later. If you need assistance, please reach out to our Care team.
- investigating May 29, 2025, 01:53 PM UTC
Performance has improved. If you are experiencing an issue with logging in or loading, retry the action a few minutes later. If you need assistance, please reach out to our Care team.
- investigating May 29, 2025, 11:52 PM UTC
Performance has improved. If you are experiencing an issue with logging in or loading, retry the action a few minutes later. If you need assistance, please reach out to our Care team.
- investigating May 30, 2025, 09:00 PM UTC
Performance has improved. If you are experiencing an issue with logging in or loading, retry the action a few minutes later. If you need assistance, please reach out to our Care team.
- investigating Jun 02, 2025, 01:47 PM UTC
Intermittent performance issues have improved for the majority of customers. If you are experiencing an issue with logging in or loading, retry the action a few minutes later. If you need further assistance, please reach out to our Care team.
- investigating Jun 03, 2025, 07:48 PM UTC
If you are experiencing an issue with logging in or loading, retry the action a few minutes later. If you need further assistance, please reach out to our Care team for further investigation.
- monitoring Jun 06, 2025, 01:40 PM UTC
We have released multiple fixes to address performance issues, including upgrading our Database Services. We are monitoring the results.
- resolved Jun 09, 2025, 03:01 PM UTC
The performance issues that some accounts were experiencing have been resolved. We appreciate your patience and understanding as we worked on this.