Website
Canonical public site hosted on AWS Amplify.
A successful public-page response measures reachability at the check time, not continuing uptime or every site feature.
Live public read-only check
Current health not fully verified
SolveLang operations
System status
Recent public health observations, capability evidence, and manually curated incidents are separate. A page response does not verify customer-specific behavior.
Reporting mode: live observations + manual incident history
Public read-only checks are bounded snapshots, not an SLA. They expire; missing, failed, future-dated, or expired observations become unverified. Incident history remains manually curated. No uptime percentage is inferred.
Incident record last revised . This is not a last-seen heartbeat.
Current observations and component boundaries
Current health not fully verifiedLive check has not completed yet — treat status as unverified.
Production API health
Public API /health endpoint.
This checks the public health response only. It does not verify account authentication, persistence, billing, or customer requests.
Live public read-only check
Current health not fully verified
Studio public page
Hosted Workflow Intelligence Studio page.
Page availability does not verify account saving, browser-local projects, or authenticated persistence.
Live public read-only check
Current health not fully verified
Browser Preview public page
Pinned WebAssembly safe-core preview at /run/.
Page availability does not execute the preview or verify its runtime contract.
Live public read-only check
Current health not fully verified
Repository Audit public page
Public Repository Audit example surface.
Page availability does not verify analysis correctness.
Live public read-only check
Current health not fully verified
Solve Graph public page
Public Solve Graph example surface.
Page availability does not verify graph correctness.
Live public read-only check
Current health not fully verified
Account authentication and persistence
Customer account and Studio account-saving behavior.
Live probe: the API checks its customer account store with a read-only request and reports healthy only when the store answers. It does not sign anyone in, and it does not read or expose customer records.
Live public read-only check
Current health not fully verified
Checkout, payment, and webhooks
Production subscription billing capability.
Live probe: the API confirms subscription billing is enabled and Stripe answers a read-only request. It does not create charges, and it does not prove webhook delivery; a completed checkout is the payment proof.
Live public read-only check
Current health not fully verified
Support automation
Support triage preview and connected automation.
Live probe: the public support page answers with its expected content. Page availability does not connect an inbox or execute support automation.
Live public read-only check
Current health not fully verified
Paid priority and managed execution
Provider-backed and side-effecting execution.
No independent public health signal measures paid priority, providers, or managed workflow execution.
Not independently monitored
Current health not fully verified
PostHog
Analytics integration.
No independent public health signal is connected.
Not independently monitored
Current health not fully verified
CI and Deployment
GitHub Actions validation and AWS Amplify publishing.
Live probe: GitHub's own CI badge for this repository's main workflow. It measures the latest reported CI state, not AWS Amplify publishing or continuing service health.
Live public read-only check
Current health not fully verified
Current incident reports
This is a manual register, not an automatic detection service.
No current incident report is recorded in this snapshot. This does not establish that every component is operational.
Historical incident records
Records are preserved. Archiving an old observation does not invent its resolution time or imply that it is a current outage.
archived · major impact
GitHub Actions upstream degradation
Started Aug 6, 2026, 3:22 PM UTC
Historical record retained from August 6. The following messages describe that day's observations, not a current outage. An independently verified closure time was not recorded; no resolution time or uptime is inferred.
GitHub status ↗Aug 6, 2026, 10:18 PM UTC — historical update
GitHub reported significant improvement in workflow success rates while standard and larger runners drained queued work. Webhook triggers and some self-hosted runner behavior remained affected. SolveLang CI/deployment should therefore still be treated as degraded until the upstream incident is fully resolved.
Aug 6, 2026, 8:34 PM UTC — historical update
GitHub reported continued Actions disruption affecting both GitHub-hosted and self-hosted runners, with webhook processing throttled during recovery.
Aug 6, 2026, 3:22 PM UTC — historical update
GitHub began investigating degraded GitHub Actions performance. SolveLang validation jobs may fail to start, queue, or time out while the dependency is degraded.
No invented reliability metrics.
Public availability claims require measured evidence. Billing, credentials, provider activation, and live canaries remain independently controlled; changing this report never enables them.