Some SSO sign-ins may fail

What to do

• Check whether you use Ashby Single Sign On. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 21m it lasted.

  Anything that failed between 2026-07-16 08:40 UTC and 2026-07-16 11:00 UTC may need a replay.

• Subscribe to Ashby's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=ashby works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Ashby 4

1. identifiedJul 16, 2026, 8: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. The issue is caused by an incident in an upstream provider. Our team is actively monitoring the situation and will post another update as we learn more.

   provider

2. identifiedJul 16, 2026, 9: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. If you're currently logged in, avoid logging out while the issue persists. Other login methods, including magic-link sign-in, are unaffected. We are actively monitoring and will post another update as the situation changes.

   provider

3. monitoringJul 16, 2026, 10:44 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.

   provider

4. resolvedJul 16, 2026, 11:00 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.