Aktuell kann es auf dem Host ferdinand zu einer Einschränkung der Performance kommen. Dort läuft aktuell eine Kampagne von postmitherz.org über die wir uns sehr freuen, die aber teilweise zu hohen Lastspitzen führt. Wir haben für den Host daher bereits einen eigenen Server Node freigemacht um für den Zeitraum (bis 18.12.) der Kampagne möglichst viel Spielraum zu geben.

Solltest du dennoch ein Problem mit deiner Seite feststellen, schreib bitte unserem Support und wir suchen gemeinsam nach einer Lösung.

The host crashed due to the storage problems and is in the process of rebooting right now.

we observe partial failures on fr3

One node with the following Hosts crashed, we are in the process of restoring them right now:

• europa
• eurydome
• farbauti
• euporie
• dione
• halimed
• caliban

We have received reports that our IPv6 network 2a00:d0c0:200::/48 (FRA3) is unreachable from some networks. We are investigating the issue. IPv4 connectivity should be unaffected.

The hosts eukelade, ijiraq, reinmuth, alnilam, kojima, euanthe are down because the underlying piece of hardware crashed. We are rebooting it on a different one.

The host crashed and is in the process of rebooting right now.

We added some RAM and the host is in the process of rebooting right now.

We added some RAM and the host is in the process of rebooting right now.

We are having some storage issues on the system that impacted the performance but were resolved within 15 minutes, we are still investigating the situation.

The host was reported unreachable by monitoring at 08:19. The vm had run out of RAM. We added some RAM and the host finished the process of rebooting now and everything seems to be running operationally again.

We observe that IPv4 connectivity is currently impacted. IPv6 connectivity is unaffected.

The web server on aegaeon.uberspace.de fails to start. We're investigating.

MariaDB on helin.uberspace.de crashed. It was restarted successfully at 11:50 CEST.

The cluster node hosting aries.uberspace.de is crashed. We're migrating the VM to another cluster node.

The network 95.143.172.0/24 at our datacenter FRA4 is currently experiencing an outage. We're investigating.

IPv6 connectivity at our FRA4 datacenter is currently impacted and showing packet loss. IPv4 is working fine. The root cause has been identified already and our operations team is working on a fix.

Due to maintenance work, it is possible that the network connections to some of our hosts might be temporarily disrupted (a list of hosts will follow).

Multiple host are currently unreachable, we are investigating.

A full list will follow ASAP.

the nginx on centaurus has stopped, web access is not available, we are investigating

We forgot to reload the mail services when we recently renewed their TLS certificates. If your mail client complains about an expired IMAP/POP3/SMTP certificate, please restart the mail client and potentially your computersystem. We restarted the services with the new certificate on 23 Apr 2023.

We are investigating a network outage on FRA4, the following hosts are affected:

acamar.uberspace.de
achernar.uberspace.de
aldebaran.uberspace.de
antares.uberspace.de
antila.uberspace.de
apus.uberspace.de
aquila.uberspace.de
ara.uberspace.de
aries.uberspace.de
auriga.uberspace.de
bootes.uberspace.de
caelum.uberspace.de
canis.uberspace.de
canopus.uberspace.de
capella.uberspace.de
carina.uberspace.de
cassiopeia.uberspace.de
centaurus.uberspace.de
cepheus.uberspace.de
cetus.uberspace.de
circinus.uberspace.de
columba.uberspace.de
corvus.uberspace.de
crater.uberspace.de
crux.uberspace.de
cygnus.uberspace.de
delphinus.uberspace.de
dorado.uberspace.de
draco.uberspace.de
fomalhaut.uberspace.de
fulu.uberspace.de
grus.uberspace.de
hamal.uberspace.de
hercules.uberspace.de
horologium.uberspace.de
hydrus.uberspace.de
indus.uberspace.de
jarnsaxa.uberspace.de
juliet.uberspace.de
lacerta.uberspace.de
leo.uberspace.de
lepus.uberspace.de
libra.uberspace.de
lupus.uberspace.de
lynx.uberspace.de
menkar.uberspace.de
mensa.uberspace.de
monoceres.uberspace.de
musca.uberspace.de
norma.uberspace.de
octans.uberspace.de
pavo.uberspace.de
perseus.uberspace.de
phoenix.uberspace.de
pictor.uberspace.de
puppis.uberspace.de
rigel.uberspace.de
sagitta.uberspace.de
sculptor.uberspace.de
serpens.uberspace.de
sirius.uberspace.de
triangulum.uberspace.de
tucana.uberspace.de
ursa.uberspace.de
vega.uberspace.de
vela.uberspace.de
volans.uberspace.de
vulpecula.uberspace.de

There are currently problems logging in to our webmailer (webmail.uberspace.de) with a @username.uber.space or @uber.space domain, we are working on it.

On friday april 7 one of our backup raid controllers lost two of its four disks. We were unable to repair the damage with the remaining 2 disks in a sufficient way and decided to start over with the backups for the affected hosts. Due to the crash there are no backups available from april 7 and earlier for the following hosts:

bestla
bergelmir
bianca
caliban
callirrhoe
carpo
eirene
fairydust
johnson
pizarro
sanguin

The original data on these hosts and the backups on other hosts were not affected by this. New backups for the affected hosts are running since april 8.

We are investigating an outage of our cluster on FRA4, the following hosts are affected:

acamar.uberspace.de
achernar.uberspace.de
aldebaran.uberspace.de
antares.uberspace.de
antila.uberspace.de
apus.uberspace.de
aquila.uberspace.de
ara.uberspace.de
aries.uberspace.de
auriga.uberspace.de
bootes.uberspace.de
caelum.uberspace.de
canis.uberspace.de
canopus.uberspace.de
capella.uberspace.de
carina.uberspace.de
cassiopeia.uberspace.de
centaurus.uberspace.de
cepheus.uberspace.de
cetus.uberspace.de
circinus.uberspace.de
columba.uberspace.de
corvus.uberspace.de
crater.uberspace.de
crux.uberspace.de
cygnus.uberspace.de
delphinus.uberspace.de
dorado.uberspace.de
draco.uberspace.de
fomalhaut.uberspace.de
fulu.uberspace.de
grus.uberspace.de
hamal.uberspace.de
hercules.uberspace.de
horologium.uberspace.de
hydrus.uberspace.de
indus.uberspace.de
jarnsaxa.uberspace.de
juliet.uberspace.de
lacerta.uberspace.de
leo.uberspace.de
lepus.uberspace.de
libra.uberspace.de
lupus.uberspace.de
lynx.uberspace.de
menkar.uberspace.de
mensa.uberspace.de
monoceres.uberspace.de
musca.uberspace.de
norma.uberspace.de
octans.uberspace.de
pavo.uberspace.de
perseus.uberspace.de
phoenix.uberspace.de
pictor.uberspace.de
puppis.uberspace.de
rigel.uberspace.de
sagitta.uberspace.de
sculptor.uberspace.de
serpens.uberspace.de
sirius.uberspace.de
triangulum.uberspace.de
tucana.uberspace.de
ursa.uberspace.de
vega.uberspace.de
vela.uberspace.de
volans.uberspace.de
vulpecula.uberspace.de

Our Manual and the Lab on out Netflify instance are down at the moment.

We are currently encountering a Network Error on our Cluster in FRA4, we are investigating.

We added several new disks to our storage cluster which results in quite some data being moved around. This results in temporarily impacted disk performance. We slowed down the data migration progress in order to lower the impact already. Usual disk performance is about to be restored soon.

We are currently upgrading MySQL/MariaDB. The database as well as the mysql-binary is unavailable for a couple of minutes during the update.

We are currently having performance issues on musca.uberspace.de because of a long running maintenance process.

The host crashed and is in the process of rebooting right now.