As of 11/11/2026, 00:46
99.08 %
Availability, 90 days
citexnode.com, signing in and everything you click in the dashboard.
The interface behind the dashboard.
MySQL databases, reachable at mysql.citexnode.de.
Confirmations, password resets and renewal reminders.
ns1.citexnode.de – answers DNS queries for domains on our nameservers.
ns2.citexnode.de – second nameserver at a different provider, copies every zone from ns1 automatically.
Whether ns1 and ns2 serve the same state for every domain on our nameservers.
Our customers' status pages on statuscx.eu and their own domains.
Der zweite Standort, seit dem 23.08. in Betrieb.
Die Maschine für neu angelegte Game-Server.
Die Maschine für neu angelegte TeamSpeak-Musikbots.
Die Maschine für die TeamSpeak-Musikbots. Hier läuft dein Bot, wenn im Dashboard node5 daneben steht.
TeamSpeak-Server am Standort Köln.
TeamSpeak-Server am Standort Frankfurt am Main.
Our customers' websites and apps behind the edge (Caddy) on the web cluster.
Building and rolling out new versions after a git push (deployd, BuildKit).
The MariaDB databases of Deploy projects (Galera cluster across three nodes).
Project volumes and files (GlusterFS, replicated).
First node of the web cluster.
Second node of the web cluster.
Third node of the web cluster.
reseller.citexnode.com: signing in, ordering, services, invoices and the admin area.
The API for reseller shops: catalogue, orders and instances via API key.
Hourly usage metering, monthly invoices and collection via Mollie.
Automatic deploys from GitHub repositories (Git, webhooks, API). Mirrors githubstatus.com.
For Deploy projects behind the Cloudflare proxy (CDN, DNS, SSL, network). Mirrors cloudflarestatus.com.
Topping up credit and reseller invoices through our payment provider Mollie (card, PayPal, bank transfer and more). Mirrors status.mollie.com.
One bar per day – hover or tap for details. The worse of check measurements and incident reports counts; outages count fully towards the percentage, partial outages half.
Measured from here against api.citexnode.com, averaged per time slot.
(25/10/2026, 04:15) · Resolved after 2 d 10 h
Resolved
Custom vServers are fully available again. Ordering new vServers and managing existing servers through the dashboard are working normally again. The certificate change on our virtualization hosts has been completed successfully.
We continue to monitor the platform to ensure all services remain stable.
(25/10/2026, 02:09) · Resolved after 5 min
Resolved
The automated check is passing again. The component is reachable.
(25/10/2026, 02:00) · Resolved after 2 h 1 min
Resolved
All services have been stable since 01:15 UTC. The backup is now permanently throttled so it no longer slows down normal operation.
(24/10/2026, 23:00) · Resolved after 2 min
Resolved
The automated check is passing again. The component is reachable.
(24/10/2026, 23:00) · Resolved after 2 min
Resolved
The automated check is passing again. The component is reachable.
(24/10/2026, 22:57) · Resolved after 2 min
Resolved
The automated check is passing again. The component is reachable.
(24/10/2026, 21:58) · Resolved after 2 min
Resolved
The automated check is passing again. The component is reachable.
(24/10/2026, 00:37) · Resolved after 6 min
Resolved
The automated check is passing again. The component is reachable.
(23/10/2026, 21:23) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(23/10/2026, 21:16) · Resolved after 2 h 54 min
Resolved
There have been no further stalls since the brief storage hang at 21:16–21:19 CEST, and all systems are running normally. This incident is resolved. If your server is still stopped since then, please restart it from the dashboard.
(23/10/2026, 19:28) · Resolved after 8 min
Resolved
The automated check is passing again. The component is reachable.
(23/10/2026, 19:20) · Resolved after 4 h 50 min
Resolved
The TeamSpeak servers in Cologne have been running stably since the provider finished its maintenance. This incident is resolved.
(22/10/2026, 21:56) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 21:56) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 21:38) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 21:38) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:34) · Resolved after 3 h 9 min
Resolved
Resolved. The host was unreachable from about 18:20 to 19:03 CEST after a faulty change to its network configuration (the previous update mistakenly said 17:10). The fix is now permanent and has survived a reboot of the host. All services are running normally again. Sorry for the disruption.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 27 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 33 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 27 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 27 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:32) · Resolved after 27 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 18:01) · Resolved after 2 min
Resolved
The automated check is passing again. The component is reachable.
(22/10/2026, 00:15) · Resolved after 2 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 19:50) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 19:45) · Resolved after 2 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 19:01) · Resolved after 27 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 18:53) · Resolved after 2 h 12 min
Resolved
Resolved: ns1.citexnode.de and ns2.citexnode.de have been running stably for almost two hours and are now also monitored on this status page. Domains can be switched to our nameservers again.
(21/10/2026, 16:52) · Resolved after 3 h 9 min
Resolved
Resolved: GitHub has been running normally again for over an hour, webhooks are delivered without delay and deploys from GitHub repositories start as usual. If a push during the disruption did not trigger a deploy, it can be started manually from the dashboard.
(21/10/2026, 14:26) · Resolved after 6 h 39 min
Resolved
Resolved: all affected services have been running stably for over an hour on the patched PHP versions – the Deploy project on PHP 8.5.12, the mail server on PHP 8.2.35 and the Looking Glass on PHP 8.4.27. Webmail and the mail administration are reachable again. Thank you for your patience.
(21/10/2026, 14:23) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 13:08) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 12:17) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 12:15) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 12:15) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 10:39) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 10:39) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 10:30) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 09:48) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 09:48) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(21/10/2026, 02:22) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(20/10/2026, 21:31) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(20/10/2026, 02:42) · Resolved after 3 min
Resolved
The automated check is passing again. The component is reachable.
(20/10/2026, 02:05) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(20/10/2026, 02:05) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(20/10/2026, 02:05) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(20/10/2026, 02:05) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(19/10/2026, 20:46) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(19/10/2026, 18:43) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(19/10/2026, 18:42) · Resolved after 1 min
Resolved
The automated check is passing again. The component is reachable.
(19/10/2026, 10:20) · Resolved after 2 h 56 min
Resolved
Resolved. The BuildKit cache is capped at 8 GB on every build host, web-04 has joined as a fourth build host, and deployd 0.4.3 now waits up to 5 minutes for nodes to pull the image during rollout instead of 90 seconds. A follow-up bug where every deploy of a project was rolled back immediately after one failed rollout is fixed as well. New builds complete again; please restart any failed builds once.
We send you an e-mail when an incident starts, changes or is resolved – and 24 hours before every maintenance. Every mail has a one-click unsubscribe.
Refreshes itself every 30 seconds.