- Level
- confirmed
- Worst impact
- Degraded
- Components
- Login
- Down Index
- 9of 100
What to do
Check whether you use Quip Login. 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 0m it lasted.
Anything that failed between 2023-10-31 20:33 UTC and 2023-10-31 20:33 UTC may need a replay.Subscribe to Quip's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=quip works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Quip 1
- resolved
From October 26, 2023 at 2:17 PM PDT to October 31, 2023 at 3:19 PM PDT, users were unable to log in to Quip via the Sign In With Salesforce SSO method. All other login methods were fully operational. During this window, Sign In With Salesforce was temporarily disabled while our team addressed a potential security vulnerability related to this login method. The vulnerability was not exploited and is now fully patched. Sign In With Salesforce is fully operational.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-8debfa3f7d
Is Quip still down?
No, this incident was resolved 2023-10-31 20:33 UTC. For Quip's live state, see https://down.guide/quip.
How long did it last?
0m, from 2023-10-31 20:33 UTC to 2023-10-31 20:33 UTC, by the times Quip posted.
What was affected?
Quip named Login.
What caused it?
Quip hasn't published a root cause. If it does, it shows here.
Where does this come from?
Quip's official status page, https://status.quip.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.