- Level
- confirmed
- Worst impact
- Degraded
- Components
- api.stitchdata.com, app.stitchdata.com
- Down Index
- 25of 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 4h 9m it lasted.
Anything that failed between 2022-07-20 13:31 UTC and 2022-07-20 17:40 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
Some extraction jobs are failing to start at the scheduled time. We have identified the issue and are working to implement a fix.
provider
- monitoring
A fix has been applied and we are currently monitoring extraction jobs as they return to their normal schedules.
provider
- resolved
Extraction jobs have consistently begun at their normal schedules during our monitoring window. No data has been lost as a result of this incident.
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-51021481b1
Is Stitch still down?
No, this incident was resolved 2022-07-20 17:40 UTC. For Stitch's live state, see https://down.guide/stitch.
How long did it last?
4h 9m, from 2022-07-20 13:31 UTC to 2022-07-20 17:40 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.