- Level
- confirmed
- Worst impact
- Degraded
- Components
- HEY
- Down Index
- 17of 100
What to do
Check whether you use Basecamp HEY. 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 20m it lasted.
Anything that failed between 2020-09-11 16:24 UTC and 2020-09-11 16:44 UTC may need a replay.Subscribe to Basecamp's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=basecamp works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Basecamp 2
- monitoring
We're seeing some delays with inbound emails in HEY that were sent between 15:45-16:05 UTC (10:45-11:05am CST). The root cause has been fixed, but you may see some delays in emails if they were sent to you in this 20 minute span.
provider
- resolved
This incident has been resolved.
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-7a26015fa1
Is Basecamp still down?
No, this incident was resolved 2020-09-11 16:44 UTC. For Basecamp's live state, see https://down.guide/basecamp.
How long did it last?
20m, from 2020-09-11 16:24 UTC to 2020-09-11 16:44 UTC, by the times Basecamp posted.
What was affected?
Basecamp named HEY.
What caused it?
Basecamp hasn't published a root cause. If it does, it shows here.
Where does this come from?
Basecamp's official status page, https://www.37status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.