# \#outage

**URL:** https://forums.librehealth.io/tag/outage/53.md

[Latest](https://forums.librehealth.io/latest.md) · [Categories](https://forums.librehealth.io/categories.md) · [Tags](https://forums.librehealth.io/tags.md)

---

## [\[RESOLVED\] CI Runner is currently down](https://forums.librehealth.io/t/resolved-ci-runner-is-currently-down/5548)

<div class="topic-metadata">

**Author:** [@r0bby](https://forums.librehealth.io/u/r0bby)\
**Replies:** 1\
**Last updated:** [October 10, 2026, 2:06am UTC](https://forums.librehealth.io/t/resolved-ci-runner-is-currently-down/5548 "2026-10-10T02:06:41Z")

</div>

I am currently moving the Docker data directory to an external volume on the same VM that has more space than we currently have right now on the root filesystem. Will report back when it’s back up.

---

## [\[RESOLVED\]\[OUTAGE\] Chat is DOWN](https://forums.librehealth.io/t/resolved-outage-chat-is-down/3208)

<div class="topic-metadata">

**Author:** [@r0bby](https://forums.librehealth.io/u/r0bby)\
**Replies:** 1\
**Last updated:** [October 18, 2019, 11:24am UTC](https://forums.librehealth.io/t/resolved-outage-chat-is-down/3208 "2019-10-18T11:24:28Z")

</div>

We are aware that chat is down. An upgrade did not go as planned.

---

## [27 May 2018 LibreHealth-wide Outage report](https://forums.librehealth.io/t/27-may-2018-librehealth-wide-outage-report/2425)

<div class="topic-metadata">

**Author:** [@r0bby](https://forums.librehealth.io/u/r0bby)\
**Replies:** 0\
**Last updated:** [May 27, 2018, 7:02am UTC](https://forums.librehealth.io/t/27-may-2018-librehealth-wide-outage-report/2425 "2018-05-27T07:02:04Z")

</div>

There was a Distributed Denial of Service (DDoS) attack against our DNS provider. Information can be found here. As a result of this attack, DNS resolution of all of our domain names failed. We will be investigating how…

---

## [26 May 2018 Forums Outage: What happened?](https://forums.librehealth.io/t/26-may-2018-forums-outage-what-happened/2423)

<div class="topic-metadata">

**Author:** [@r0bby](https://forums.librehealth.io/u/r0bby)\
**Replies:** 0\
**Last updated:** [May 26, 2018, 8:20pm UTC](https://forums.librehealth.io/t/26-may-2018-forums-outage-what-happened/2423 "2018-05-26T20:20:21Z")

</div>

The forums were down from a period from 0600 UTC until just recently. It appears that Docker did not come back up immediately after the automated reboot necessary to apply security patches. I apologize for the long outa…

---

## [EHR Demo Server](https://forums.librehealth.io/t/ehr-demo-server/2045)

<div class="topic-metadata">

**Author:** [@r0bby](https://forums.librehealth.io/u/r0bby)\
**Replies:** 0\
**Last updated:** [January 23, 2018, 7:53am UTC](https://forums.librehealth.io/t/ehr-demo-server/2045 "2018-01-23T07:53:08Z")

</div>

The following servers are currently down due to an issue with the hypervisor. We are currently working to get it back up and running.

---

## [GItLab Outage on 1/31/17: Looking forward](https://forums.librehealth.io/t/gitlab-outage-on-1-31-17-looking-forward/498)

<div class="topic-metadata">

**Author:** [@r0bby](https://forums.librehealth.io/u/r0bby)\
**Replies:** 11\
**Last updated:** [February 3, 2017, 3:35am UTC](https://forums.librehealth.io/t/gitlab-outage-on-1-31-17-looking-forward/498 "2017-02-03T03:35:11Z")

</div>

It appears that gitlab made a few mistakes (mostly around backup procedures). They tweeted earlier today that they deleted production data by accident. Live notes on the recovery can be found here: https://docs.google.c…