No incidents reported
8:00 AM PDT - 9:01 AM PDT (1h1min duration)
Fly.io has reported that services have been fully restored.
9:10 AM PDT - 11:15 AM PDT (2h5min duration)
Resolved API response times have been stable at normal levels. No customer data was affected.
7:52 AM PDT - 8:15 AM PDT (23min duration)
Elevated error rate on web app and API
The app and api have been stable since 10:56 AM EDT. This incident is resolved. Total impact was approximately 7 minutes. No data was lost.
5:01 AM PDT - 5:20 AM PDT (20min duration)
Elevated API latency and intermittent errors
Between 12:01 and 12:11 UTC, a subset of API requests experienced slow response times, and a small number of requests failed with errors.
The cause was a single large report execution that consumed excessive memory on our API servers, causing them to restart. Each restart was brief (approximately 20 seconds), and remaining servers continued serving traffic throughout. The service was never fully unavailable.
Approximately 0.3% of requests during this window returned an error. The report execution has been stopped and all servers returned to normal operation. No data was lost, and no customer action is required.
6:50 AM PDT - 7:47 AM PDT (57min duration)
Single sign-on failures for SAML users
Users signing in through SAML single sign-on were unable to start a new session. Users with an active session were unaffected until it needed to refresh.
10:52 PM PDT - 10:52 PM PDT (0min duration)
Brief errors loading personal schedule data
Between 01:45 and 01:52 AM ET on August 13, a small number of users saw errors loading their own shifts, timecard, provider, and team details in the web and mobile apps. Affected requests returned an error rather than incorrect data, and retrying after the window succeeded.
No data was lost or corrupted, and the public API was not affected.