How can my agent or app check netcup status?

Fetch https://upbutler.com/status/netcup/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":"netcup"}, on https://upbutler.com/mcp/public.

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

Add "netcup" to the dependencies of your UpButler workspace. When one of your monitors fails while netcup 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 netcup down?

netcup publishes no status we can read

Right now

Unknown. No machine-readable official status; see their status page.

No official machine-readable status

For agents

proceed

Proceed.

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

MCP: upstream_status {"service":"netcup"}

Root servers, VPS and web hosting in Germany and Austria.

What netcup says

www.netcup-status.de has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful.

Their site: www.netcup-status.de

What UpButler measured

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

netcup incidents, last 90 days

Without a machine-readable source there is no incident history to show. netcup keeps its own at www.netcup-status.de.

Get alerted when netcup goes down

netcup publishes no incidents we can read, so there is nothing to send an alert about. If you depend on it, monitor your own use of it: add a monitor with your key or URL.

Status badge

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

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

Tell your outage from netcup's

Declare that your project depends on netcup. When one of your monitors fails while netcup 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:
  - netcup

Ask before you retry

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

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "netcup",
  "verdict": "proceed",
  "status": "unknown",
  "reason": "No machine-readable official status; see their status page",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is netcup down right now?: We cannot tell. www.netcup-status.de has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful. Their own status page is at https://www.netcup-status.de.
Where does this status come from?: www.netcup-status.de has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful.
How can my agent or app check netcup status?: Fetch https://upbutler.com/status/netcup/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":"netcup"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or netcup's?: Add "netcup" to the dependencies of your UpButler workspace. When one of your monitors fails while netcup 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 netcup. Status and incident text belong to netcup and are read from their public status source; the probe result is UpButler's own measurement.