Ashby incident

Some SSO sign-ins may fail

Major Resolved View vendor source →

Ashby experienced a major incident on July 16, 2026 affecting Single Sign On, lasting 2h 20m. The incident has been resolved; the full update timeline is below.

Started
Jul 16, 2026, 08:40 AM UTC
Resolved
Jul 16, 2026, 11:00 AM UTC
Duration
2h 20m
Detected by Pingoru
Jul 16, 2026, 08:40 AM UTC

Affected components

Single Sign On

Update timeline

  1. identified Jul 16, 2026, 08:40 AM UTC

    We are investigating intermittent failures when signing in to Ashby using SSO. Affected users may see a login error and need to retry. Other sign-in methods and the rest of Ashby are operating normally. Our team is actively monitoring and working to restore full SSO reliability, and we will post another update as we learn more.

  2. identified Jul 16, 2026, 09:12 AM UTC

    We are continuing to monitor an issue where some users may intermittently experience a failed or timed-out login when signing in via SSO because of an issue in our upstream provider. If you hit an error signing in via SSO, please retry. Other login methods, including magic-link sign-in, are unaffected. We are actively monitoring and will post another update as the situation changes.

  3. monitoring Jul 16, 2026, 10:57 AM UTC

    Our upstream provider has resolved the incident affecting SSO sign-ins. Users should now be able to log in normally. We are continuing to monitor recovery and will provide another update if the situation changes.

  4. resolved Jul 16, 2026, 11:00 AM UTC

    This incident has been resolved.