# \[Resolved? issue\] Beeminder downtime

**URL:** <https://forum.beeminder.com/t/resolved-issue-beeminder-downtime/12789>\
**Category:** Bugabee\
**Created:** [June 3, 2026, 9:06am UTC](https://forum.beeminder.com/t/resolved-issue-beeminder-downtime/12789 "2026-06-03T09:06:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![shanaqui](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/shanaqui/32/3513_2.png) [@shanaqui](https://forum.beeminder.com/u/shanaqui)\
**Post date:** [June 3, 2026, 9:06am UTC](https://forum.beeminder.com/t/resolved-issue-beeminder-downtime/12789/1 "2026-06-03T09:06:25Z")

</div>

Beeminder is down! I have so far got hold of Danny, but we have no idea what the problem is. But we know!

---

<div class="post-metadata">

**Author:** ![shanaqui](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/shanaqui/32/3513_2.png) [@shanaqui](https://forum.beeminder.com/u/shanaqui)\
**Post date:** [June 3, 2026, 9:08am UTC](https://forum.beeminder.com/t/resolved-issue-beeminder-downtime/12789/2 "2026-06-03T09:08:59Z")

</div>

We are currently back up (at least for me) but since we don’t know what happened, we don’t know if that will last.

---

<div class="post-metadata">

**Author:** ![shanaqui](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/shanaqui/32/3513_2.png) [@shanaqui](https://forum.beeminder.com/u/shanaqui)\
**Post date:** [June 3, 2026, 9:37am UTC](https://forum.beeminder.com/t/resolved-issue-beeminder-downtime/12789/3 "2026-06-03T09:37:31Z")

</div>

So we aren’t any the wiser and I’m having problems even logging into my Linode account to see if there are any alerts there, due to Linode not sending me a code; since we’re now back up, it might be a matter of waiting for the other workerbees to wake up (rather than waking them up actively) to dig in further to what might have happened.

---

<div class="post-metadata">

**Author:** ![shanaqui](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/shanaqui/32/3513_2.png) [@shanaqui](https://forum.beeminder.com/u/shanaqui)\
**Post date:** [June 3, 2026, 11:11am UTC](https://forum.beeminder.com/t/resolved-issue-beeminder-downtime/12789/4 "2026-06-03T11:11:39Z")

</div>

All stable so far, so nobody else has been woken up to handle the problem.

I still can’t get into Linode, so no idea if the explanation waits there that our machine was restarted or something like that (though I received no emails about it). More info will have to await the more technical folks and might even happen after I clock off for the day, but at the moment we’re on our feet.

---

<div class="post-metadata">

**Author:** ![shanaqui](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/shanaqui/32/3513_2.png) [@shanaqui](https://forum.beeminder.com/u/shanaqui)\
**Post date:** [June 3, 2026, 12:55pm UTC](https://forum.beeminder.com/t/resolved-issue-beeminder-downtime/12789/5 "2026-06-03T12:55:20Z")

</div>

Probably down again! We’re cutting over to the poppy page successfully each time after a few moments, so that’s something.

I have stepped away for lunch and based on the behaviour I’d _guess_ that it’s likely we’ll be back up again shortly even without intervention, but I did ping the others.

There is no specific evidence that this is anything on our end, and might be something to do with a quirk of Linode that we’ve seen before, where other people sharing our data centre take us down with them under heavy load, but that is a complete guess at this moment.

---

<div class="post-metadata">

**Author:** ![shanaqui](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/shanaqui/32/3513_2.png) [@shanaqui](https://forum.beeminder.com/u/shanaqui)\
**Post date:** [June 4, 2026, 11:04am UTC](https://forum.beeminder.com/t/resolved-issue-beeminder-downtime/12789/6 "2026-06-04T11:04:19Z")

</div>

As far as I know we’ve seen no more of this since yesterday, and still no evidence of anything on our side.

So… probably resolved? I’m sorry I don’t have a more satisfying and meaty update dissecting what happened!
