Some customers unable to log in via SSO
Last updatepostmortemOct 27 · 16:42 UTC
Summary: Between approximately 19:45 and 22:10 UTC on October 15, 2026, customers signing in through single sign-on (SSO) with certain identity providers were unable to log in to FloQast, with some sign-in attempts failing intermittently.
Root Cause: A release containing an enhancement to the sign-in process included two changes that interacted poorly with some identity providers. The first changed how sign-in requests are identified, producing identifiers that some providers rejected. The second was a software library upgrade that changed how stored identity provider certificate settings are read, causing sign-ins to fail where existing settings were not in the format the updated library expected. Pre-release validation did not reproduce the behavior of these providers, so the issue was not identified before the release reached production.
Immediate Resolution: Both changes were rolled back, and the previous version was redeployed across all regions, restoring SSO sign-in for affected customers shortly thereafter.
Follow-up Actions: We are expanding our pre-release testing to include end-to-end sign-in scenarios against a range of identity providers, and broadening test coverage to reflect a wider range of customer configurations. We are also standardizing how stored identity provider certificate settings are handled, and further strengthening our release safeguards and change tracking. The sign-in improvements from this release will be re-introduced only after they have been fully validated against these scenarios.
Reported by FloQast on their status page.