- Level
- confirmed
- Worst impact
- Degraded
- Components
- api.stitchdata.com, app.stitchdata.com
- Down Index
- 21of 100
What to do
Check whether you use Stitch api.stitchdata.com, app.stitchdata.com. 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 56m it lasted.
Anything that failed between 2020-01-16 21:29 UTC and 2020-01-16 22:25 UTC may need a replay.Subscribe to Stitch's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=stitch works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Stitch 3
- identified
An update to an internal database has caused server errors while accessing information about connections in Stitch accounts. Our engineering team has identified the issue and is working to address it now.
provider
- monitoring
A fix has been deployed and application access is returning to normal. We're continuing to monitor behavior.
provider
- resolved
Connections have remained accessible and stable since this fix was deployed.
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-52139e5dbc
Is Stitch still down?
No, this incident was resolved 2020-01-16 22:25 UTC. For Stitch's live state, see https://down.guide/stitch.
How long did it last?
56m, from 2020-01-16 21:29 UTC to 2020-01-16 22:25 UTC, by the times Stitch posted.
What was affected?
Stitch named api.stitchdata.com, app.stitchdata.com.
What caused it?
Stitch hasn't published a root cause. If it does, it shows here.
Where does this come from?
Stitch's official status page, https://status.stitchdata.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.