Partial degradation

Checked Sep 1, 2026, 1:08 PM

Platform status

GrowBridge system status

At least one publicly reachable service is slow or returning an error.

What this page checks: live reachability of the 4 GrowBridge components with a public web address — probed fresh, server-side, on every load. A green “Up” means that request succeeded just now.

What it doesn’t tell you: this isn’t an uptime guarantee or SLA, it doesn’t track incident history beyond the optional panel below, and it never reflects your own grow room’s sensors or hardware — only shared GrowBridge infrastructure. It also can’t show every backend component; see “Not shown here” below for why.

Publicly monitored

The 4 services with a public address

Each row is a live probe from this page load — not a cached or historical value.

Marketing site

growbridge.io — product info, connect, and docs

UpHTTP 200 · 120ms

GrowBridge app

app.growbridge.io — sign-in and command center

UpHTTP 200 · 283ms

Sensor API

api.growbridge.io — hardware readings and integrations

UpHTTP 200 · 95ms

Content CMS

cms.growbridge.io — editorial content and dashboard broadcasts

IssueHTTP 404 · 339ms
How this works

Every time this page is requested, the server sends a real HTTP request to each service below (HEAD first, falling back to GET if a service doesn’t support HEAD) and records whether it succeeded, the status code, and how long it took.

Results are cached for up to 2 minutes so repeated visits don’t hammer the services being checked. No credentials, grower data, or sensor readings are read or sent anywhere on this page.

  • Long-term 7/30/90-day history (right) comes from a separate UptimeRobot account, not this page’s own probes.
  • UptimeRobot’s monitor list doesn’t necessarily match this page’s 4 rows one-to-one.

Uptime history

Full history
Monitor7d30d90dNow
Sensor APIup
Sensor API100.00%100.00%99.98%up
GrowBridge appup
GrowBridge app100.00%100.00%99.98%up
Marketing siteup
Marketing site100.00%100.00%100.00%up
Not shown here

What this page can’t check, and why

GrowBridge runs on 6 Railway services and a Neon Postgres database behind the 4 services above. 5 of those Railway services have no public network address at all — by design, for the ones that don’t need one — so there is nothing this page could probe honestly. They’re listed here instead of pretending a check ran.

Ingest worker

Railway service — polls connected growers’ hardware and writes sensor_readings continuously.

No public HTTP endpoint. Liveness is tracked internally via a per-tick heartbeat, checked in the product’s own admin system health, not published here.

Backfill worker

Railway service — drains queued "Sync history" jobs so large historical pulls never block the API.

No public HTTP endpoint. Liveness is tracked internally via queue depth, checked in the product’s own admin system health, not published here.

Grow journal cron

Railway cron job — composes each grower’s daily journal once at 06:00 UTC, then exits.

Runs once a day and exits — there is no persistent process to probe between runs.

Voice — text to speech

Railway service — self-hosted Kokoro speech synthesis behind Ask Rance’s voice replies.

Private-network-only by design (no public domain is configured) — reachable only from the backend API, never from the open internet.

Voice — speech to text

Railway service — self-hosted transcription behind Ask Rance’s voice input.

Private-network-only by design (no public domain is configured) — reachable only from the backend API, never from the open internet.

Database (Neon Postgres)

The system of record for sensor history, grow profiles, and journals.

Has no public HTTP surface to probe directly. Its reachability is implied by the sensor API, dashboard, and CMS checks above — each one depends on it.