- Level
- confirmed
- Worst impact
- Maintenance
- Components
- HEY
- Regions
- us
What to do
Check whether you use Basecamp HEY in us. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Check that everything you run on Basecamp came back after the window closed 2023-11-21 16:58 UTC.
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 4
- investigating
HEY is having some trouble. We're looking into the root cause and will keep you posted here. We're so sorry for the interruption, everyone.
provider
- identified
We've discovered the root cause and are actively working on a fix for the trouble with HEY. No ETA yet, but we're on the case. Stay tuned. Thanks for bearing with us, folks.
provider
- monitoring
HEY's back up and running. You may see some delayed emails. We're working to get those flowing.
provider
- resolved
HEY's back up and running. We're keeping an eye on things to make sure those emails are flowing smoothly again. Thanks for your patience folks.
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-7693b5b674
Is this Basecamp maintenance still going on?
No, it ended 2023-11-21 16:58 UTC.
How long did it last?
25m, from 2023-11-21 16:32 UTC to 2023-11-21 16:58 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.