Status

What is live, checked from your browser.

This page asks the platform health endpoint on this origin whether the web runtime is answering, and shows exactly what came back. It does not claim monitoring that does not exist.

What this check covers — and what it does not

Web runtime — GET /api/health

Checking

Asking the health endpoint on this origin for its status.

Scope of the check

  • EndpointGET /api/health on this origin
  • What it provesThis web runtime answered and returned {"status":"ok"}
  • What it does not proveDatabase, queue, workers, payments or provider connections
  • HistoryNone — no uptime record is kept
  • External probeNone — the check runs from your browser only

The health route deliberately reads no configuration, database or provider state, so it can never leak or depend on secrets. That also means it can only ever tell you that the web runtime is up.

Area by area

The state of each part of the platform right now.

AreaStateNote
Website and dashboardLivehostingsurge.com, the customer dashboard and the health endpoint checked above.
Platform API, CLI and MCPLiveREST API under /api/v1, the hostingsurge CLI and the MCP server at /mcp with OAuth sign-in for AI clients.
Deployments and hostingLiveGit push-to-deploy, uploads and Docker images, build and runtime logs, rollback, environment variables, cron jobs and deploy hooks.
Domains and SSLLiveCustom domains with ownership verification, the exact DNS records to add, automatic certificates and redirects.
DatabasesLivePostgreSQL, MySQL, MariaDB, Redis and MongoDB with scheduled backups and restore.
WordPressLiveManaged sites with updates, hardening, health checks and backups.
Imports and migrationsLiveVercel, Netlify, any Git host, WordPress backups, cPanel, SFTP/FTP, database dumps and website snapshots, each checked on a preview URL.
EmailLiveMailboxes, aliases and IMAP import; transactional sending is enabled per organization after review.
AI builderEarly accessRolling out to accounts step by step.
BillingImplemented, not liveThe credit ledger, verified top-ups and subscription fulfillment are implemented. No price catalog is published yet, so no purchase can be completed.
Branch previews, deployment protection, uptime checks and notificationsIn developmentBeing added now; they appear in the dashboard when they ship.

How to read platform state honestly

A few rules the platform applies everywhere — they are the reason some states look different from a marketing page.

Queued is not live

A deployment or build that is queued, requested or building is displayed in exactly that state. Nothing is shown as published before it is.

Not configured is not a bug

When a provider key or connection is missing, the platform says not_configured and stops. It does not invent a result or retry forever.

A failure stays a failure

A failed build or run records the failure and its category. A build artifact receipt exists only after the bytes have been hashed, stored and read back.

No invented numbers

There is no uptime percentage, incident history or customer count on this page, because none of those exist yet to report.

Build on what is live today.

The docs show where every feature lives in the dashboard and the CLI; the developers page covers the API.

There is no uptime history, incident feed, SLA or third-party probe behind this page. Those are in development, and this page will link them when they exist.