Platform status · live · reloads on refresh

All monitored systems operational

Live platform health for every Gluecron surface — database, autopilot, git protocol, AI review, and the synthetic monitor.

100.0%
24h uptime
99.9%
30d uptime
99.9%
90d uptime
2
Days since last incident
5h 46m
Process uptime
0
Alerts · 24h
4/4
Monitored services up

How uptime is measured: computed from recorded incidents — rolling 24h / 30-day / 90-day windows, overlapping incidents merged, an open incident counted up to now. Figures measure from Aug 9, 2026; windows reaching further back cover only the period since then. Incidents are filed by the in-process synthetic monitor. The off-box incident writer is not currently armed, so an outage that takes the whole box down may not appear in these figures — they are a floor on downtime, not a ceiling.

Components

Per-service health

Real-time status of every platform surface.

All operational
Service24h uptimeStatus

Database

Postgres (Neon) — primary datastore

100.0%Operational

API

REST + Git Smart HTTP — verified by serving this page

100.0%Operational

Git Push / Smart HTTP

Clone, fetch, push — same process as the API

100.0%Operational

AI Review

Claude-powered pull request analysis — no health probe yet

Not monitored

CI Runner

Continuous integration pipeline — no health probe yet

Not monitored

Autopilot

Periodic platform-maintenance loop

100.0%Running

History

Incident history

Most recent 10 incidents. Updated as events are filed and resolved.

All resolved
DateIncidentSeverityStatusResolved

17 services degraded

Automated synthetic monitoring detected 17 failing checks. Explore — expected status 200, got 502; Desktop extension download — expected status 200, got 502; Health endpoint — expected status 200, got 502; journey:authed-session — /dashboard returned 502 for a valid session; journey:explore-data — /explore returned 502; journey:login-form — login handler returned 502 on a bad password; Home page — expected status 200, got 502; Sign-in — expected status 200, got 502; Web app manifest — expected status 200, got 502; MCP server — expected status 200, got 502; Pricing page — expected status 200, got 502; Readiness endpoint — expected status 200, got 502; Registration — expected status 200, got 502; robots.txt — expected status 200, got 502; Status page — expected status 200, got 502; Service worker — expected status 200, got 502; Version API — expected status 200, got 502.

CriticalResolved

Last 24h

Synthetic monitor

Automated probes that returned a red result.

All green

No alerts in the last 24h.

Every synthetic probe is green. We log every red result here with timestamps and error text.

Estate

Estate watch

Other Gluecron-operated products, probed from this box. Their outages are shown for honesty but are not gluecron.com incidents and never count toward the uptime figures above.

10 red
  • estate:gatetest.ai

    Unable to connect. Is the computer able to access the url?

  • estate:gatetest.ai

    Unable to connect. Is the computer able to access the url?

  • estate:gatetest.ai

    Unable to connect. Is the computer able to access the url?

  • estate:gatetest.ai

    Unable to connect. Is the computer able to access the url?

  • estate:gatetest.ai

    Unable to connect. Is the computer able to access the url?

  • estate:gatetest.ai

    Unable to connect. Is the computer able to access the url?

  • estate:gatetest.ai

    Unable to connect. Is the computer able to access the url?

  • estate:gatetest.ai

    Unable to connect. Is the computer able to access the url?

  • estate:gatetest.ai

    Unable to connect. Is the computer able to access the url?

  • estate:gatetest.ai

    Unable to connect. Is the computer able to access the url?

Numbers

Platform stats

28
Developers
50
Repositories
37
Public repos
3,723
Gate runs
42.4%
Green rate
5h 46m
Uptime

Autopilot

Latest tick

Per-task results from the most recent autopilot sweep.

69 ticks this process
  • Finished2026-09-01T14:07:01.807Z
  • Total ticks this process69
  • mirror-syncok24ms
  • merge-queueok52ms
  • weekly-digestok24ms
  • advisory-rescanok24ms
  • wait-timer-releaseok27ms
  • scheduled-workflowsok25ms
  • auto-merge-sweepok138ms
  • ai-build-from-issuesok182ms
  • sleep-mode-digestok25ms
  • stale-pr-sweepok28ms
  • stale-issue-sweepok52ms
  • pr-risk-rescoreok26ms
  • account-purgeok25ms
  • playground-purgeok25ms
  • ai-proactive-monitorok1ms
  • ci-healerok2818ms
  • spec-to-prok191ms
  • synthetic-monitorok1697ms
  • surface-monitorok0ms
  • first-run-journeyok207ms
  • dependency-probesok0ms
  • monitoring-retentionok0ms
  • selfcheckok0ms
  • migration-watcherok0ms
  • daily-standupok25ms
  • pr-live-cleanupok51ms
  • weekly-standupok1ms
  • pr-test-generatorok26ms
  • advancement-scannerok1ms
  • auto-release-notesok0ms
  • pr-sandbox-cleanupok0ms
  • dev-env-idle-sweepok50ms
  • preview-expiryok50ms
  • agent-lease-expiryok25ms
  • onboarding-dripok26ms
  • dep-update-sweepok0ms
  • smart-digestok0ms
  • ai-loop-sweepok0ms
  • truth-ledgerok0ms
  • medicok468ms
  • paging-drillok0ms

Alerts

Subscribe to status alerts

Get an email when a new incident is filed or resolved. Unsubscribe any time — one click, no questions asked.

We'll send a confirmation link. No spam, ever.

Liveness: /healthz · Readiness: /readyz · Metrics: /metrics · Platform JSON: /api/platform-status