All Systems Operational

[dataforest Backbone] Interxion FRA8 Operational
90 days ago
100.0 % uptime
Today
Edge Network (affects all locations) Operational
90 days ago
100.0 % uptime
Today
DDoS Protection (affects all locations) Operational
90 days ago
100.0 % uptime
Today
Dedicated Servers (40G / 100G / 400G) Operational
90 days ago
100.0 % uptime
Today
Facilites Operational
90 days ago
100.0 % uptime
Today
[Datacenter] maincubes FRA01 Operational
90 days ago
99.99 % uptime
Today
Datacenter Routing and Switching Infrastructure Operational
90 days ago
100.0 % uptime
Today
Ceph Cluster Operational
90 days ago
100.0 % uptime
Today
Virtual Servers Operational
90 days ago
99.99 % uptime
Today
Managed Servers Operational
90 days ago
100.0 % uptime
Today
Dedicated Servers Operational
90 days ago
100.0 % uptime
Today
Plesk Web Hosting Operational
90 days ago
100.0 % uptime
Today
TeamSpeak3 Servers Operational
90 days ago
100.0 % uptime
Today
Network Storage Operational
90 days ago
100.0 % uptime
Today
Colocation Racks Operational
90 days ago
100.0 % uptime
Today
Facilites Operational
90 days ago
100.0 % uptime
Today
[Datacenter] firstcolo FRA4 Operational
90 days ago
99.99 % uptime
Today
Datacenter Routing and Switching Infrastructure Operational
90 days ago
99.99 % uptime
Today
Dedicated Servers Operational
90 days ago
99.99 % uptime
Today
Colocation Racks Operational
90 days ago
100.0 % uptime
Today
Facilites Operational
90 days ago
100.0 % uptime
Today
General Services Operational
90 days ago
100.0 % uptime
Today
Avoro CP & Support Operational
90 days ago
100.0 % uptime
Today
PHP-Friends CRM & Support Operational
90 days ago
100.0 % uptime
Today
Hotline Operational
90 days ago
100.0 % uptime
Today
Dedicated Control Panel Operational
90 days ago
100.0 % uptime
Today
IPMI VPN Operational
90 days ago
100.0 % uptime
Today
DDoS Manager Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Apr 17, 2026

No incidents reported today.

Apr 16, 2026

No incidents reported.

Apr 15, 2026

No incidents reported.

Apr 14, 2026

No incidents reported.

Apr 13, 2026

No incidents reported.

Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

Apr 10, 2026

No incidents reported.

Apr 9, 2026
Completed - The scheduled maintenance has been completed.
Apr 9, 13:05 CEST
Verifying - Rack X13, UV-R, is complete. This was the last rack. We have verified all affected servers, and they have started as expected.
If your server is not reachable, please verify your server's console output via IPMI in the Dedicated Server Control Panel and resolve any software-side issues that may prevent the system from booting. If you suspect a hardware fault, please contact our support team via ticket.

Apr 9, 11:51 CEST
Update - Rack X08, UV-R, is complete. We have verified all affected servers, and they have started as expected. We are now proceeding with the next feed according to the timeline.
Apr 9, 11:26 CEST
Update - Rack X07, UV-R, is complete. We have verified all affected servers, and they have started as expected. We are now proceeding with the next feed according to the timeline.
Apr 9, 10:50 CEST
Update - Rack X05, UV-W, is complete. We have verified all affected servers, and they have started as expected. We are now proceeding with the next feed according to the timeline.
Apr 9, 10:18 CEST
Update - Rack X05, UV-V, is complete. We have verified all affected servers, and they have started as expected. We are now proceeding with the next feed according to the timeline.
Apr 9, 09:58 CEST
In progress - As the maintenance has started on schedule, customers are reminded to shut down their servers themselves according to the previously communicated timeline. Please do not manually power on any affected server(s), as this will be handled by us. We will provide an update as each rack is completed.

(We were unable to set the maintenance status to in progress earlier due to an outage affecting our external status page provider, Atlassian.)

Apr 9, 09:48 CEST
Scheduled - Deutsch / German
(English version below)

In einigen Dedicated-Server-Racks ersetzen wir Stromverteilereinheiten (PDUs) eines Modells, das in der Vergangenheit durch eine ungewöhnlich hohe Ausfallquote aufgefallen ist. Damit reduzieren wir das Risiko unerwarteter Ausfälle. Betroffen sind vier von 48 dataforest-Racks an diesem Standort, in denen ausschließlich dedizierte Server bereitgestellt werden.

Diese Ankündigung ist ausnahmsweise zweisprachig. Weitere Updates veröffentlichen wir auf Englisch.

Wer betroffen ist:
Betroffen sind manche Systeme am Standort "fc-fra4". Server an den Standorten "mc-fra01", "ix-fra8" und "eqx-fr4" sind nicht betroffen.

Bei Servern mit redundanter Stromversorgung (laut Vertrag / Produktbeschreibung) ist kein Ausfall zu erwarten, da alle betroffenen Racks über zwei Stromfeeds verfügen.

Server mit nur einem Netzteil, die in einem der betroffenen Racks untergebracht und an einer der unten genannten Unterverteilungen angeschlossen sind, werden während der Wartung stromlos sein und müssen vorher sauber heruntergefahren werden, um Datenverlust und Dateisystemschäden zu vermeiden. Betroffene Managed Dedicated Server fahren wir herunter.

So prüfen Sie, ob Ihr Server betroffen ist:
Im Kundenbereich bzw. unter https://dedicated.dataforest.cloud sehen Sie den Namen Ihres Servers. In den letzten Tagen haben wir Server in betroffenen Racks um ihre jeweilige Unterverteilung ergänzt. Ein Server ist nur dann betroffen, wenn er sich in einem der unten genannten Racks befindet und zugleich das Kürzel "-UV-R", "-UV-V" oder "-UV-W" trägt, zum Beispiel "root1234.fc-fra4-UV-R". Bitte prüfen Sie daher unbedingt beide Kriterien. Ist nur eines davon erfüllt, ist Ihr Server nicht betroffen. Server, die im Rahmen der Wartung an UV-P betroffen waren, sind hier ausdrücklich nicht erneut betroffen. Wir haben die Arbeiten so aufeinander abgestimmt, dass kein nicht-redundanter Server zweimal abgeschaltet werden muss.

Ablauf der Wartung:
Im angegebenen Wartungsfenster werden die betroffenen PDUs bzw. Stromfeeds nacheinander abgeschaltet und getauscht. Die Ausfallzeit pro Slot wird voraussichtlich etwa 30 Minuten betragen. Ihre betroffenen Server müssen Sie vor Beginn des jeweiligen Slots selbst herunterfahren. Andernfalls würden diese durch die Stromabschaltung hart ausgeschaltet.

Wir informieren während der Wartung hier über die Wiederherstellung der einzelnen Stromfeeds. Server starten mit unserer Standard-BIOS-Konfiguration nach Wiederherstellung der Stromversorgung automatisch. Server, die sich nicht automatisch einschalten, prüfen wir selbstständig. Bitte greifen Sie in diesen Prozess nicht manuell ein.

Welche Racks / Stromfeeds wann betroffen sind:

09:30 Uhr: Rack X05, UV-V
10:00 Uhr: Rack X05, UV-W
10:30 Uhr: Rack X07, UV-R
11:00 Uhr: Rack X08, UV-R
11:30 Uhr: Rack X13, UV-R

Sie können das Rack Ihres Servers anhand der Switchport-Statistiken zuordnen.

Wie Sie sich vorbereiten sollten:
- Abonnieren Sie diese Statusseite, um Updates zu erhalten.
- Planen Sie bei Bedarf einen eigenen Shutdown und die Downtime ein.
- Informieren Sie Ihre Nutzer bzw. Kunden.
- Führen Sie möglichst vorab einen Test-Reboot durch und prüfen Sie, ob alle benötigten Dienste automatisch starten.
- Prüfen Sie per IPMI, ob im BIOS "Restore on AC Power Loss -> Power On" gesetzt ist. Diese Einstellung setzen wir standardmäßig, empfehlen aber eine zusätzliche Kontrolle. Auf Wunsch übernimmt unser Support diese Prüfung für Sie. Bitte melden Sie sich hierfür spätestens bis zum 08.04.2026.
- Prüfen Sie RAID und Backups und erstellen Sie unmittelbar vor der Wartung ein aktuelles vollständiges Backup.

Wenn Ihr Server nach der Wartung nicht erreichbar ist:
Prüfen Sie zunächst diesen Statuspost. Sobald die Wartung aus unserer Sicht erfolgreich abgeschlossen ist, kontrollieren Sie bitte per IPMI im Dedicated-Server-Controlpanel die Bildschirmausgabe Ihres Systems und beheben gegebenenfalls Softwareprobleme, die den Start verhindern. Wenn Sie einen Hardwaredefekt vermuten, kontaktieren Sie unseren Support per Ticketsystem.

Wie dataforest vorbereitet ist:
- Top-of-Rack-Switches sind redundant an Strom und Netzwerk angebunden. Das heißt: Auch wenn Sie nur einen Uplink gebucht haben, verfügt Ihr Switch über zwei Stromfeeds und zwei Coreswitch-Uplinks. dataforest implementiert grundsätzlich "doppelte Redundanz", wo immer dies sinnvoll möglich ist.
- Unser Ersatzteillager wird aufgestockt, um eventuelle Defekte schnell beheben zu können.
- dataforest-Mitarbeiter sind vor Ort und koordinieren die Arbeiten mit den Dienstleistern.

Vielen Dank für Ihre Mithilfe.

English / Englisch

In several dedicated server racks, we are replacing power distribution units (PDUs) of a model that has shown an unusually high failure rate in the past. This reduces the risk of unexpected failures. Four out of 48 dataforest racks at this site are affected. These racks host dedicated servers only.

This announcement is exceptionally bilingual. Further updates will be published in English.

Who is affected:
Some systems at the "fc-fra4" site are affected. Servers at "mc-fra01", "ix-fra8", and "eqx-fr4" are not affected.

For servers with redundant power supply (according to contract / product description), no outage is expected, as all affected racks have two power feeds.

Single-PSU servers that are located in one of the affected racks and connected to one of the affected power subdistributions listed below will lose power during the maintenance and must be shut down cleanly in advance to avoid data loss and filesystem corruption. We will shut down affected Managed Dedicated Servers ourselves.

How to check whether your server is affected:
In the customer area or at https://dedicated.dataforest.cloud, you can see your server name. During the last few days, we have added the corresponding power subdistribution to servers in affected racks. A server is only affected if it is located in one of the racks listed below and at the same time carries the suffix "-UV-R", "-UV-V", or "-UV-W", for example "root1234.fc-fra4-UV-R". Please make sure to verify both criteria. If only one of them applies, your server is not affected. Servers that were affected during the maintenance on UV-P are explicitly not affected again here. We coordinated the work so that no non-redundant server has to be powered off twice.

How the maintenance will proceed:
During the announced maintenance window, the affected PDUs or power feeds will be taken out of service and replaced one after another. The outage per slot is expected to be approximately 30 minutes. You must shut down your affected servers yourself before the beginning of the respective slot. Otherwise, they would be hard powered off by the maintenance.

During the maintenance, we will use this status post to report the restoration of the individual rack power feeds. Servers will automatically power on once power has been restored, based on our standard BIOS configuration. Servers that do not power on automatically will be checked by us. Please do not interfere manually with this process.

Which racks / power feeds are affected and when:

09:30: Rack X05, UV-V
10:00: Rack X05, UV-W
10:30: Rack X07, UV-R
11:00: Rack X08, UV-R
11:30: Rack X13, UV-R

You can identify your server's rack based on the switch port statistics.

How to prepare:
- Subscribe to this status page to receive updates.
- If necessary, plan a manual shutdown and the resulting downtime.
- Inform your users or customers.
- Perform a test reboot beforehand if possible and verify that all required services start automatically.
- Check via IPMI whether your BIOS is configured to power on automatically after AC power is restored ("Restore on AC Power Loss -> Power On"). We set this by default, but strongly recommend verifying it. Our support team can perform this check for you on request. Please contact us no later than 2026-04-08.
- Check your RAID integrity and backup concept, and create a fresh full backup immediately before the maintenance.

If your server is not reachable after the maintenance:
Please check this status post first. Once the maintenance has been marked as successfully completed from our side, please verify your server's console output via IPMI in the Dedicated Server Control Panel and resolve any software-side issues that may prevent the system from booting. If you suspect a hardware fault, please contact our support team via ticket.

How dataforest is prepared:
- Top-of-rack switches are connected redundantly to both power and network. This means that even if you only ordered one uplink, your switch still has two power feeds and two core switch uplinks. dataforest generally implements "double redundancy" wherever this is reasonably possible.
- We are increasing our spare parts stock so that any potential defects can be resolved quickly.
- dataforest staff will be on site and coordinate the work with the involved service providers.

Thank you for your cooperation.

Mar 28, 20:27 CET
Apr 8, 2026

No incidents reported.

Apr 7, 2026
Completed - The scheduled maintenance has been completed.
Apr 7, 02:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 24, 13:00 CET
Scheduled - In the next few days, we will continue the previously announced network upgrades to further improve the availability and resilience of our network. We do not anticipate any service interruptions.

What we are doing
We will:
- take a new dark fiber between maincubes FRA01 and our Equinix FR4 PoP into production
- add new DDoS filters to our scrubbing cluster
- migrate additional physical and logical interfaces in line with our modernized network design
- upgrade our connectivity with a new transit carrier (GTT) and several private peerings at our Equinix PoP (Zet.net, Rostelecom, Google, BiMajLink, Bytedance / TikTok)
- shift more load to our new Equinix PoP and its local carriers and peerings

If a connection must be taken out of service during the maintenance, traffic will be rerouted gracefully beforehand. Redundancy and available bandwidth will be reduced temporarily, but sufficient capacity will remain and all services are expected to stay online.

Expected impact
No service interruption is expected at any datacenter, but it cannot be ruled out entirely. Brief periods of slightly higher latency or minor packet loss may occur during some changes, but any impact is expected to be limited.

Routing from and to various locations will change as part of this maintenance. These routing changes are intended to improve the overall network quality. If you notice a persistent degradation in quality (e.g. packet loss or high latency), please reach out to our support.

Affected customers
This maintenance affects the network infrastructure behind all dataforest services and locations. No customer action is required.

Fallback plan
Should any action cause an unforeseen disruption or significant packet loss, we will roll back the relevant change. This should restore normal connectivity within 1-5 minutes, depending on the exact impact. We will also update this status post transparently. If an issue occurs, please allow us a few minutes to publish an update before contacting us.

Mar 24, 00:00 CET
Apr 6, 2026

No incidents reported.

Apr 5, 2026

No incidents reported.

Apr 4, 2026
Completed - The scheduled maintenance has been completed.
Apr 4, 23:53 CEST
Verifying - We have reverted the update and monitoring the situation.
Apr 4, 23:46 CEST
Update - We currently see some issues with new connections and performing a rollback from the update.
Apr 4, 23:36 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 4, 23:00 CEST
Scheduled - We will carry out maintenance on our DDoS protection infrastructure.

What we are doing
We will deploy software updates to our redundant DDoS scrubbing cluster. Filter appliances will be taken out of production and updated one by one to ensure mitigation capacity is always sufficient. After each update, functionality will be verified before we move on to the next filter.

Expected impact
No customer impact is expected at any datacenter, but it cannot be ruled out entirely. Idle (inactive) connections and sessions may time out; active ones should not, as they are expected to remain synchronized during the startup of a new software release. If you notice anything unusual – such as timeouts of active sessions or the inability to connect to your server – please contact our support immediately. We will continue monitoring new tickets for a while after the maintenance.

Affected customers
All IP prefixes routed through our DDoS protection (which is the default) are affected by this maintenance. Only prefixes that have been explicitly configured to bypass our DDoS protection (which we do not recommend) are unaffected. In any case, no customer action is required.

Fallback plan
Should the update fail and cause issues, we will disconnect the filters within a few seconds and update this status post transparently. In that case, mitigation of attacks will not be possible for 30-60 minutes while we prepare a rollback.

Apr 3, 21:57 CEST
Apr 3, 2026

No incidents reported.