Major incident
FloQast: Users unable to sign in with SSO on the APAC Database
Nov 3, 2026, 22:24 UTC
started
23:00 UTC
resolved
36 min
duration
Affected: Platform - APAC
Current status of FloQast: Operational — live FloQast status
Timeline
- Nov 3, 2026, 22:24 UTCinvestigatingWe are investigating reports that customers on our APAC Database are unable to sign in using SSO. We will provide an update here as soon as we have more information.
- Nov 3, 2026, 22:34 UTCidentifiedThe issue has been identified and a fix is being implemented.
- Nov 3, 2026, 23:00 UTCresolvedThis incident has been resolved.
Updates as published by FloQast (original).
Other services with incidents at the same time
- Vanta 23:14 UTC · Incorrect security-training and background-check test results
- Twilio 22:51 UTC · MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks in United States
- Ably 22:40 UTC · eu-west-1 NLB issues
- Vanta 22:18 UTC · Missing check results for GitHub pull requests
- Grafana Cloud 22:00 UTC · October usage report visualization issue
- Cursor 21:40 UTC · 3 "Slow clones from GH due to Github degradation"
- OpenText 21:39 UTC · Fax2Mail and Core Messaging - Email experienced processing delays
- Hostinger 21:39 UTC · Emergency Server US-1419 Maintenance
More FloQast incidents
- October 15, 2026 Some customers unable to log in via SSO
- June 2, 2026 Egnyte Connection Errors