Where does this status come from?

From Koyeb's own status page API at https://status.koyeb.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Koyeb's words.

How can my agent or app check Koyeb status?

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

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

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

Right now

No. Koyeb is operational.

No incidents reported.

Read from status.koyeb.com 59 s ago · every 120s

For agents

proceed

Proceed.

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

MCP: upstream_status {"service":"koyeb"}

Serverless containers and GPUs per region.

What Koyeb reports

Operational

Taken as is from Koyeb's own status page API. Incident titles and component names below are theirs.

Open status.koyeb.com

UpButler's independent probe

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

Koyeb components

17 operational

Europe

Frankfurt - FRAOperational
Paris - PAROperational

Control PanelOperational
APIOperational
Build / ProvisioningOperational
North AmericaOperational
EuropeOperational
Asia–Pacific - APACOperational
Third Party: Github → API RequestsOperational
Third Party: Github → WebhooksOperational
Third Party: Cloudflare → Cloudflare Sites and Services → APIOperational
Third Party: Docker → RegistryOperational
Third Party: Quay → RegistryOperational

North America

Washington, D.C. - WASOperational
San Francisco - SFOOperational

Asia–Pacific - APAC

Tokyo - TYOOperational
Singapore - SINOperational

Koyeb incidents, last 90 days

No finished incidents on record yet. UpButler keeps what Koyeb publishes for 90 days from the day it starts tracking a service.

Tell your outage from Koyeb's

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

Ask before you retry

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

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "koyeb",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Koyeb down right now?: No. As of 2026-10-10 05:12 UTC, Koyeb is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Koyeb's own status page API at https://status.koyeb.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Koyeb's words.
How can my agent or app check Koyeb status?: Fetch https://upbutler.com/status/koyeb/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":"koyeb"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Koyeb's?: Add "koyeb" to the dependencies of your UpButler workspace. When one of your monitors fails while Koyeb 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.

More in hosting and compute

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