- Level
- confirmed
- Worst impact
- Degraded
- Components
- HEY
- Regions
- us
- Down Index
- 19of 100
What to do
Check whether you use Basecamp HEY in us. 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 21m it lasted.
Anything that failed between 2024-08-14 21:45 UTC and 2024-08-14 22:06 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 3
- investigating
We're looking into the root cause and will keep you posted here. We're so sorry for the interruption, everyone.
provider
- monitoring
We've discovered the root cause and are actively working on a fix. HEY should be back up. Thanks for bearing with us, folks.
provider
- resolved
HEY's back up and running. We're keeping a close eye on things. Sorry again for the interruption.
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-c4f48aede5
Is Basecamp still down?
No, this incident was resolved 2024-08-14 22:06 UTC. For Basecamp's live state, see https://down.guide/basecamp.
How long did it last?
21m, from 2024-08-14 21:45 UTC to 2024-08-14 22:06 UTC, by the times Basecamp posted.
What was affected?
Basecamp named HEY in us.
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.