As of 11/11/2026, 01:01
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.
(18/10/2026, 19:13) · Resolved after 1 h 42 min
Resolved
Resolved. Websites with a database or persistent storage only run on the servers next to the database, and PHP websites serve images, stylesheets and scripts with cache headers. Load times have been normal since the move. If you run a PHP website, the cache applies from your next deploy; clicking "Deploy now" is enough.
(18/10/2026, 18:19) · Resolved after 2 h 58 min
Resolved
Resolved. All cron jobs have run without errors for over an hour. New is the "Command" type: cron scripts run directly in the container as on classic hosting (e.g. php cron/task.php), with no token in the call. Exit code and output are shown under Cron jobs → History.
(18/10/2026, 16:40) · Resolved after 1 h 37 min
Resolved
Resolved. We checked the whole flow with a test payment at Mollie: the payment is reported and assigned correctly. There were no paid Mollie top-ups that went uncredited, so nobody lost any balance.
(18/10/2026, 16:37) · Resolved after 1 h 39 min
Resolved
Resolved. Sign-up and password reset now consistently require and state at least 10 characters.
(18/10/2026, 16:36) · Resolved after 1 h 41 min
Resolved
Resolved. The confirmation email can be requested again after signing up, in the dashboard and when ordering. If you could not confirm your address so far, just request a new email.
(18/10/2026, 16:23) · Resolved after 4 min
Resolved
The fix is live. All links in our emails lead to the right page again, including in emails you already received. If you could not confirm your email address, just open the link from the email again. If it has expired, you can request a new confirmation email when you sign in.
(17/10/2026, 21:53) · Resolved after 3 h 31 min
Resolved
Resolved. All three database nodes are in sync again; deploys and databases work normally. Duration: about 3 ½ hours.
Deploy now has its own row on this page and is checked every minute, so an outage like this shows up here right away.
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.