What is Contabo's uptime?

Over the last 90 days, Contabo reported 97.16% uptime on its official status page. That figure is calculated from the public incident timeline at https://contabo-status.com, each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Contabo's uptime history rolling forward in real time.

Has Contabo had outages in 2026?

Yes, Contabo has had 16 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last Contabo outage?

The most recent Contabo incident was "Security Incident – Investigating", which started on October 26, 2026 and was resolved on October 26, 2026. Pingoru captured this directly from https://contabo-status.com. See the full incident card above for affected components and the update timeline.

How often does Contabo have outages?

Based on the last 90 days, Contabo averages 5.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components: so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is Contabo's status page?

Contabo's official status page is https://contabo-status.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on, so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is Contabo down right now?

Contabo has degraded performance. Pingoru checks the official status page every 5 minutes and flips this headline the moment Contabo reports a change. Current status is based on 9 tracked services.

How does Pingoru know if Contabo is down?

We read https://contabo-status.com directly, using Contabo's own status page. If the vendor reports an incident, you see it within one check cycle, not after someone manually marks the page as down.

Where can I get notified when Contabo has an outage?

Create a free Pingoru account and add Contabo as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Contabo's status page says the service is up, but I'm having issues. What's wrong?

Three common reasons: • A real Contabo incident that hasn't been acknowledged on their public status page yet, vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers. These rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Contabo issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official Contabo status?

We use Contabo's own status page at https://contabo-status.com and cross-reference their homepage (https://contabo-status.com). Nothing is read in a way the vendor hasn't explicitly made public. We use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

What does "Degraded" mean?

Contabo is reporting degraded performance. Services are up but slower than usual, or a subset of requests is failing.

Is Contabo down?

Last checked 3m ago

Current status

Contabo has degraded performance

2 active incidents: Object Storage (EU region) – Service Disruption, PHP security advisory (CVE-2026-115560): mitigation recomme…

Get alerts when Contabo breaks → View Contabo outage history →

Free, no credit card

Official status page: contabo-status.com
Checked every 5 minutes
9 components tracked

Contabo is reporting degraded performance right now (last checked 3m ago). Services are up but slower or partially failing.

Real-time Contabo status, recent outages, and incident history: pulled directly from Contabo's official status page at contabo-status.com every 5 minutes. Pingoru tracks 9 Contabo services and has captured 19 incidents in the last 90 days (97.16% uptime). Get email, Slack, Discord, or webhook alerts the moment Contabo reports a new incident, free for 3 monitors, no credit card.

Users who monitor Contabo also follow these Status Pages services:

FACEIT View all 8,000+ providers

Contabo uptime 97.16% uptime · past 90 days

Mon Wed Fri

AugSepOct

Less More

Active incidents 2

Object Storage (EU region) – Service Disruption

Ongoing ● 3d 20h

Started Oct 26, 2026, 02:00 PM UTC
Timeline · 3 updates
- investigating · Oct 26, 2026, 02:00 PM UTC
  
  Customers using Object Storage in the EU region may currently be unable to access their storage, or may see errors. New Object Storage orders for this region cannot be completed at the moment. We are investigating and working on a fix. Next update: 16:30 CET
- monitoring · Oct 27, 2026, 06:02 PM UTC
  
  We are still experiencing performance issues affecting our object storage service, which may cause slower response times or occasional request timeouts. Our team is actively working to improve service stability and performance. We apologize for any inconvenience and appreciate your patience. Next update: 29.10.2026, 16:30 CET
- monitoring · Oct 29, 2026, 03:22 PM UTC
  
  Our technicians are continuing to work on improving the stability and performance of our object storage service in the EU region. We apologize for any inconvenience this may cause and sincerely appreciate your patience and understanding. Next update: 02.11.2026, 16:30 CET
Latest: Our technicians are continuing to work on improving the stability and performance of our object storage service in the EU region. We apologize for any inconvenience this may cause …
PHP security advisory (CVE-2026-115560): mitigation recommended

Ongoing ● 6d 22h

Started Oct 23, 2026, 12:00 PM UTC
Timeline · 2 updates
- investigating · Oct 23, 2026, 12:00 PM UTC
  
  Status: Investigating impact The PHP project has published an informational advisory about a further vulnerability (CVE-2026-115560). It is a potential remote code execution vector in PHP’s session handling. The PHP project rates it as unlikely to occur in practice, because it requires an unusual combination of configuration and application code. We are aware of the advisory and are currently investigating the impact on our products and customers. To be on the safe side, we recommend that customers apply the mitigation recommended by the PHP project now: set session.upload_progress.enabled=0 in your PHP configuration and restart PHP. If you already applied this setting following the PHP advisory of 21 October 2026 (CVE-2026-109619), no further action is needed. A full fix will follow in the next regular PHP release. We also continue to recommend updating to the fixed PHP versions 8.5.12, 8.4.27, 8.3.36 or 8.2.35 (the fixes for the 21 October advisory). We will update this notice as soon as we have more information. How to apply the mitigation Self-managed servers (VPS/VDS/Dedicated, no control panel) Edit the relevant php.ini (or a conf.d override) and set session.upload_progress.enabled = 0. Restart PHP-FPM or Apache (e.g. systemctl restart php8.x-fpm or systemctl restart apache2). Check with php -i | grep upload_progress or a phpinfo() page. Set this in php.ini or the FPM pool/server config. The PHP project advises against relying on ini_set() or .user.ini, because the setting must apply before request parsing. cPanel/WHM In WHM, go to Software → MultiPHP INI Editor. Choose the PHP version and open Editor Mode. Add or set session.upload_progress.enabled = 0 and save. Repeat for every installed PHP version. Restart PHP-FPM if the change is not applied automatically. Customers without WHM access can use cPanel’s MultiPHP INI Editor per domain. Server-wide configuration by the administrator is preferred, see the note below. Plesk Server-wide: Tools & Settings → PHP Settings, select the PHP version, and add session.upload_progress.enabled=0 under Additional configuration directives (or edit the php.ini tab). Per subscription: Websites & Domains → [domain] → PHP Settings, add the same line under Additional configuration directives, then click Apply. Repeat for every PHP version in use.
- monitoring · Oct 23, 2026, 02:31 PM UTC
  
  The mitigation (session.upload_progress.enabled=0) is implemented on all our webspace systems.
Latest: The mitigation (session.upload_progress.enabled=0) is implemented on all our webspace systems.

Recent outages & incidents

Past 90 days

Security Incident – Investigating

Resolved 3h 11m

Started Oct 26, 2026, 12:30 PM UTC · Resolved Oct 26, 2026, 03:41 PM UTC
Timeline · 1 update
- investigating · Oct 26, 2026, 12:30 PM UTC
  
  We detected unauthorized access to systems hosting VDS. Affected systems are isolated and under investigation. Affected customers will be notified directly by email. As a precaution, we recommend rotating SSH keys, passwords, and API tokens used on your VDS. We only communicate via this page - Next update: 15:00 CET
Latest: We detected unauthorized access to systems hosting VDS. Affected systems are isolated and under investigation. Affected customers will be notified directly by email. As a precautio…
Legacy customer control panel taken offline as a precaution

Resolved 56m

Started Oct 21, 2026, 11:25 AM UTC · Resolved Oct 21, 2026, 12:21 PM UTC
Timeline · 1 update
- investigating · Oct 21, 2026, 11:25 AM UTC
  
  As a precaution, we have taken our legacy customer control panel offline. It runs on PHP and is affected by two critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619), for which active exploitation has been reported. We have no evidence that customer data or systems have been affected. Impact: You cannot log in to the legacy control panel until further notice. Your servers, VPS, storage and other services are not affected and continue to run normally. Workaround: Manage your services via new.contabo.com or the API. If you need an action that is only available in the legacy panel, please contact support. Recommended actions: If you run PHP applications on your own Contabo services, apply the PHP security update as soon as your distribution or vendor releases it. Configuration workarounds are ineffective. Be alert to phishing emails asking you to log in or “verify” your account. We never ask for your password by email. Next steps: We will restore the legacy panel once the patch has been applied and verified, and will post updates here.
Latest: As a precaution, we have taken our legacy customer control panel offline. It runs on PHP and is affected by two critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619), …
Shared web hosting (cPanel) suspended due to PHP vulnerabilities

Resolved 1d 7h

Started Oct 21, 2026, 11:00 AM UTC · Resolved Oct 22, 2026, 06:29 PM UTC
Timeline · 3 updates
- investigating · Oct 21, 2026, 11:00 AM UTC
  
  Two critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619) are being actively exploited. As a precaution, we have suspended our shared web hosting (cPanel) until it is patched. Hosted websites and the cPanel interface are unavailable. We have no evidence that customer data or systems have been affected. Not affected: Running servers, VPS (including cloud-init installations), VDS, storage and other services continue as normal. Email sending and receiving should still work, although webmail is not accessible. If you run PHP applications on your own Contabo services, apply the PHP security update as soon as it is available. Configuration workarounds are ineffective. Please do not open Support tickets for this matter at the moment. Web hosting will be restored once the patch is applied and verified. We will update this page as soon as we have news.
- monitoring · Oct 21, 2026, 03:48 PM UTC
  
  We expect updates to be released at around 7pm UTC and start patching as soon as they are available.
- monitoring · Oct 21, 2026, 08:57 PM UTC
  
  All web hosting services are fully patched and available. The issue has been resolved.
Latest: All web hosting services are fully patched and available. The issue has been resolved.
Important security update: patching of all VPS/VDS hosts (CVE-2026-99999)

Resolved 7d 1h

Started Oct 15, 2026, 05:33 PM UTC · Resolved Oct 22, 2026, 06:34 PM UTC
Timeline · 5 updates
- investigating · Oct 15, 2026, 05:33 PM UTC
  
  We are aware of CVE-2026-99999, a critical Linux kernel vulnerability (CVSS 9.3) that was publicly disclosed on 15 October 2026. It affects the host systems underlying all VPS and VDS products. We have been tracking it since publication and are working to patch our entire server fleet as quickly as possible, with fixes deployed gradually as they become available. Customers should expect VPS or VDS to restart during this period. We will keep interruptions as brief as possible. We recommend keeping recent backups and making sure services start automatically after a reboot. Full details available on our helpdesk.
- monitoring · Oct 19, 2026, 02:49 PM UTC
  
  VPS host system updates are nearly complete, and VDS host systems will follow next. Following the updates, some host systems are currently unreachable. Our team is working to restore them as quickly as possible. The following host systems are known to be affected: 15404, 24812, 13888, 31940, 24580, 22541, 15915, 28472, 24601, 20800, 28261, 27593, 18343, 18194, 28372, 17176, 17575, 17289
- monitoring · Oct 20, 2026, 07:28 AM UTC
  
  Patches are at 99% done. The following host systems are currently known to be unreachable after the patches: 14950, 14930, 14964, 15915, 27593, 17289, 18194, 17575, 15404, 18343, 31940, 24812. Our team is working to restore them as quickly as possible.
- monitoring · Oct 20, 2026, 03:08 PM UTC
  
  The majority of system are up and running again, the following host systems are currently known to be unreachable after the patches: 13841
- monitoring · Oct 22, 2026, 10:53 AM UTC
  
  All patches are 100% done. We currently work hard on bringing back the last remaining down VPS host: 18343.
Latest: All patches are 100% done. We currently work hard on bringing back the last remaining down VPS host: 18343.
Scheduled Maintenances: SYD

Resolved 2h 51m

Started Oct 14, 2026, 12:34 PM UTC · Resolved Oct 14, 2026, 03:25 PM UTC
Timeline · 1 update
- monitoring · Oct 14, 2026, 12:34 PM UTC
  
  Description Planned Maintenance – Sydney (SYD) Data Centre The data centre operator in Sydney (SYD) will perform an exceptional maintenance on Thursday, 15 October 2026, from 6:00 PM to 9:00 PM AEDT (07:00 – 10:00 UTC). We do not expect any downtime. Estimated duration 0 minutes Affected systems SYD
Latest: Description Planned Maintenance – Sydney (SYD) Data Centre The data centre operator in Sydney (SYD) will perform an exceptional maintenance on Thursday, 15 October 2026, from 6:00 …

See the full Contabo outage history

13 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Contabo outage history →

Or sign up free to get alerts when Contabo breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · Contabo Status · 9 components checked every 5 minutes

35incidents recorded

35last 12 months

18last 90 days

3 daystypical duration, 12 months

The longest incident in the last year, System migration on May 18, 2026, ran for 18 days. 2 maintenance windows announced in the same period.

Most affected components, last 12 months

US Central1

Latest incidents

Object Storage (EU region) – Service Disruption October 26, 2026 · still open · degraded service
Customers using Object Storage in the EU region may currently be unable to access their storage, or may see errors. New Object Storage orders for this region…
Security Incident – Investigating October 26, 2026 · 3 hours · degraded service
We detected unauthorized access to systems hosting VDS. Affected systems are isolated and under investigation. Affected customers will be notified directly by…
PHP security advisory (CVE-2026-115560): mitigation recommended October 23, 2026 · still open · degraded service
Status: Investigating impact The PHP project has published an informational advisory about a further vulnerability (CVE-2026-115560). It is a potential remote…

Outage history

Past 90 days · 18 incidents View full outage history →

Object Storage (EU region) – Service Disruption Ongoing

Started Oct 26, 2026, 02:00 PM UTC · ● 3d 20h
Security Incident – Investigating Resolved

Started Oct 26, 2026, 12:30 PM UTC · Resolved Oct 26, 2026, 03:41 PM UTC · 3h 11m
PHP security advisory (CVE-2026-115560): mitigation recommended Ongoing

Started Oct 23, 2026, 12:00 PM UTC · ● 6d 22h
Legacy customer control panel taken offline as a precaution Resolved

Started Oct 21, 2026, 11:25 AM UTC · Resolved Oct 21, 2026, 12:21 PM UTC · 56m
Shared web hosting (cPanel) suspended due to PHP vulnerabilities Resolved

Started Oct 21, 2026, 11:00 AM UTC · Resolved Oct 22, 2026, 06:29 PM UTC · 1d 7h
Important security update: patching of all VPS/VDS hosts (CVE-2026-99999) Resolved

Started Oct 15, 2026, 05:33 PM UTC · Resolved Oct 22, 2026, 06:34 PM UTC · 7d 1h
Scheduled Maintenances: SYD Resolved

Started Oct 14, 2026, 12:34 PM UTC · Resolved Oct 14, 2026, 03:25 PM UTC · 2h 51m
Degraded Performance - CEPH Cluster: non-critical Resolved

Started Oct 14, 2026, 12:28 PM UTC · Resolved Oct 14, 2026, 03:25 PM UTC · 2h 57m