# Server down

**URL:** <https://forum.beeminder.com/t/server-down/426>\
**Category:** Bugabee\
**Created:** [January 15, 2015, 2:23pm UTC](https://forum.beeminder.com/t/server-down/426 "2015-01-15T14:23:51Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![ghf](https://avatars.discourse-cdn.com/v4/letter/g/ac91a4/32.png) [@ghf](https://forum.beeminder.com/u/ghf)\
**Post date:** [January 15, 2015, 2:23pm UTC](https://forum.beeminder.com/t/server-down/426/1 "2015-01-15T14:23:51Z")

</div>

There were problems with page loading at 16:22 Time Zone: EET

---

<div class="post-metadata">

**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\
**Post date:** [January 16, 2015, 1:54am UTC](https://forum.beeminder.com/t/server-down/426/2 "2015-01-16T01:54:39Z")

</div>

EET is 10 hours ahead of Portland so 16:22 EET should be 06:22 in this graph from Pingdom:

![](https://sea1.discourse-cdn.com/flex019/uploads/beeminder/182/f5995b6cfd3584ed.png)

We clearly need to address those response time spikes but they don’t correspond to the downtime you saw. So I’m at a loss on this. Please do keep reporting such things though; hugely appreciated!

---

<div class="post-metadata">

**Author:** ![philip](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/philip/32/1505_2.png) [@philip](https://forum.beeminder.com/u/philip)\
**Post date:** [January 16, 2015, 8:55am UTC](https://forum.beeminder.com/t/server-down/426/3 "2015-01-16T08:55:27Z")

</div>

For info: we tweet outages and other such events at [@beemstat](http://twitter.com/beemstat)

---

<div class="post-metadata">

**Author:** ![ghf](https://avatars.discourse-cdn.com/v4/letter/g/ac91a4/32.png) [@ghf](https://forum.beeminder.com/u/ghf)\
**Post date:** [May 6, 2015, 7:58am UTC](https://forum.beeminder.com/t/server-down/426/4 "2015-05-06T07:58:01Z")

</div>

There were problems with page loading at 10:57 Time Zone: EET

---

<div class="post-metadata">

**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\
**Post date:** [May 6, 2015, 9:54pm UTC](https://forum.beeminder.com/t/server-down/426/5 "2015-05-06T21:54:34Z")

</div>

Thanks for reporting! That would’ve been 1:57am Pacific time. Pingdom doesn’t show any problems then but @insti also saw problems at 12:31am Pacific time. So I’m pretty sure we’re having some kind of intermittent performance issues we need to deal with. Keep letting us know; thanks again!

---

<div class="post-metadata">

**Author:** ![ghf](https://avatars.discourse-cdn.com/v4/letter/g/ac91a4/32.png) [@ghf](https://forum.beeminder.com/u/ghf)\
**Post date:** [December 27, 2015, 2:07pm UTC](https://forum.beeminder.com/t/server-down/426/6 "2015-12-27T14:07:34Z")

</div>

There were problems with page loading at 16:00 Time Zone: EET

---

<div class="post-metadata">

**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\
**Post date:** [December 27, 2015, 2:15pm UTC](https://forum.beeminder.com/t/server-down/426/7 "2015-12-27T14:15:23Z")

</div>

Confirmed. Thank you! [http://twitter.com/beemstat](http://twitter.com/beemstat)

---

<div class="post-metadata">

**Author:** ![ghf](https://avatars.discourse-cdn.com/v4/letter/g/ac91a4/32.png) [@ghf](https://forum.beeminder.com/u/ghf)\
**Post date:** [December 27, 2015, 2:35pm UTC](https://forum.beeminder.com/t/server-down/426/8 "2015-12-27T14:35:11Z")

</div>

Shall we try later? At what hour?

---

<div class="post-metadata">

**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\
**Post date:** [December 27, 2015, 3:30pm UTC](https://forum.beeminder.com/t/server-down/426/9 "2015-12-27T15:30:07Z")

</div>

Back now. Really sorry about the prolonged downtime – about 2 hours it seems. And not clear that Linode is out of the woods yet: [http://twitter.com/beemstat](http://twitter.com/beemstat)
