Is Contabo down right now?

Partly. As of 2026-10-10 07:13 UTC, Contabo is having issues, with an open incident: "Network Connectivity Issues - US Central DC". This page reads the status again every 5 minutes.

Where does this status come from?

From Contabo's own incident feed at https://contabo-status.com. UpButler reads it once for everyone (not once per visitor) every 5 minutes with conditional requests, and shows it unchanged: incident titles and component names are Contabo's words.

Can I get an alert when Contabo goes down?

Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Contabo reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/contabo/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.

How can my agent or app check Contabo status?

Fetch https://upbutler.com/status/contabo/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"contabo"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Contabo's?

Add "contabo" to the dependencies of your UpButler workspace. When one of your monitors fails while Contabo has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Contabo down?

Contabo is having issues

Right now

Partly. Network Connectivity Issues - US Central DC.

Last checked 5 min ago (2026-10-10 07:13 UTC) from contabo-status.com · every 300s

For agents

proceed

Proceed, expect slow or flaky responses.

GET upbutler.com/status/contabo/status.agent.json

MCP: upstream_status {"service":"contabo"}

VPS, dedicated servers and object storage.

What Contabo says

Degraded· 1 open incident

Taken as is from Contabo's own incident feed. Incident titles and component names below are theirs.

Open contabo-status.com

What UpButler measured

There is no keyless endpoint of Contabo that says anything useful, so UpButler does not probe it. To check your own Contabo account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Contabo

Network Connectivity Issues - US Central DCinvestigating · impact minor
Since 2026-10-09 08:17 UTC
Description We are currently investigating a network connectivity issue affecting some sectors of our US Central Data Center. We will provide further updates as more information becomes available. Estimated duration 0 minutes Update 09.10.2026 10:32 am (UTC+2) Connectivity should be back to normal again. Waiting for final confirmation. Update 09.10.2026 02:47 pm (UTC+2) Everything is confirmed to be back to normal.
Running Maintenances: Singapore 2maintenance in progress
Since 2026-10-10 01:00 UTC
Description Scheduled Maintenance — Singapore 2 October 10, 2026 · 03:00 CET – October 10, 2026 · 17:00 CET We will be performing scheduled maintenance on the power infrastructure in our Singapore 2 data center. During this maintenance window, servers in this location will be temporarily unavailable. Estimated duration 840 minutes Affected systems Singapore 2

Text written by Contabo, shown unchanged.

Contabo incidents, last 90 days

2026-07-13: no record
2026-07-14: no record
2026-07-15: no record
2026-07-16: no record
2026-07-17: no record
2026-07-18: no record
2026-07-19: no record
2026-07-20: no record
2026-07-21: no record
2026-07-22: no record
2026-07-23: no record
2026-07-24: no record
2026-07-25: no record
2026-07-26: no record
2026-07-27: no record
2026-07-28: no record
2026-07-29: no record
2026-07-30: no record
2026-07-31: no record
2026-08-01: no record
2026-08-02: no record
2026-08-03: no record
2026-08-04: no record
2026-08-05: no record
2026-08-06: no record
2026-08-07: no record
2026-08-08: no record
2026-08-09: no record
2026-08-10: no record
2026-08-11: no record
2026-08-12: no record
2026-08-13: no record
2026-08-14: no record
2026-08-15: no record
2026-08-16: no record
2026-08-17: no record
2026-08-18: no record
2026-08-19: no record
2026-08-20: no record
2026-08-21: no record
2026-08-22: no record
2026-08-23: no record
2026-08-24: no record
2026-08-25: no record
2026-08-26: no record
2026-08-27: no record
2026-08-28: no record
2026-08-29: no record
2026-08-30: no record
2026-08-31: no record
2026-09-01: no record
2026-09-02: no record
2026-09-03: no record
2026-09-04: no record
2026-09-05: no record
2026-09-06: no record
2026-09-07: no record
2026-09-08: no record
2026-09-09: no record
2026-09-10: no record
2026-09-11: no record
2026-09-12: no record
2026-09-13: no record
2026-09-14: no record
2026-09-15: no record
2026-09-16: no record
2026-09-17: no record
2026-09-18: no record
2026-09-19: no record
2026-09-20: no record
2026-09-21: no record
2026-09-22: no record
2026-09-23: no record
2026-09-24: no record
2026-09-25: no record
2026-09-26: no record
2026-09-27: no record
2026-09-28: no record
2026-09-29: no record
2026-09-30: no record
2026-10-01: no record
2026-10-02: no record
2026-10-03: no record
2026-10-04: no record
2026-10-05: no record
2026-10-06: no record
2026-10-07: no record
2026-10-08: no record
2026-10-09: minor incident
2026-10-10: minor incident

2026-07-132 of 2 days with an incidenttoday

Each bar is a day, coloured by the worst incident Contabo reported. It is their incident record, not a measurement of uptime.

No finished incidents on record yet since 2026-10-09. UpButler keeps what Contabo publishes for 90 days from the day it starts tracking a service.

Get alerted when Contabo goes down

No account. One email when Contabo reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Contabo as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Contabo's current status in a README or an internal wiki. It updates by itself.

[![Contabo status](https://upbutler.com/status/contabo/badge.svg)](https://upbutler.com/status/contabo)

Tell your outage from Contabo's

Declare that your project depends on Contabo. When one of your monitors fails while Contabo has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - contabo

Ask before you retry

curl -s https://upbutler.com/status/contabo/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "contabo",
  "verdict": "proceed",
  "status": "degraded",
  "reason": "Network Connectivity Issues - US Central DC",
  "retryAfterSec": null,
  "incident": {
    "title": "Network Connectivity Issues - US Central DC",
    "url": "https://contabo-status.com#216"
  },
  "probe": null
}

Questions

Is Contabo down right now?: Partly. As of 2026-10-10 07:13 UTC, Contabo is having issues, with an open incident: "Network Connectivity Issues - US Central DC". This page reads the status again every 5 minutes.
Where does this status come from?: From Contabo's own incident feed at https://contabo-status.com. UpButler reads it once for everyone (not once per visitor) every 5 minutes with conditional requests, and shows it unchanged: incident titles and component names are Contabo's words.
Can I get an alert when Contabo goes down?: Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Contabo reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/contabo/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Contabo status?: Fetch https://upbutler.com/status/contabo/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"contabo"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Contabo's?: Add "contabo" to the dependencies of your UpButler workspace. When one of your monitors fails while Contabo has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Contabo. Status and incident text belong to Contabo and are read from their public status source; the probe result is UpButler's own measurement.