Go to file
claude-ceo-assistant 08066d3d67 feat(ci): replace upptime with Gitea-native uptime probe (closes #2)
Combined transition PR — does the full upptime → Gitea-native cron
swap in one place, vs two separate PRs that would land in interleaved
state.

Why upptime had to go
- All 5 upptime workflows call api.github.com for releases lookup,
  issue management, and result commits.
- Post the 2026-05-06 GitHub org suspension, no token in our org
  authenticates against api.github.com — every scheduled run fails
  with HTTP 401 "Bad credentials". Run #70 is the most recent
  example; the failure mode has been continuous since the suspension.

What this PR does
- Moves all 5 upptime workflows from .github/workflows/ to
  .github/workflows-disabled/. Gitea Actions does not scan that
  directory, so they stop scheduling immediately on merge.
- Adds .github/workflows-disabled/README.md explaining the move +
  linking #2 + linking the replacement.
- Adds a single new .github/workflows/uptime-probe.yml that runs the
  new Gitea-native probe (https://git.moleculesai.app/molecule-ai/
  molecule-ai-uptime-probe) on a 5-minute cadence and commits per-site
  JSONL history to history/.

Why a single new workflow vs the upptime decomposition
- Each upptime workflow ran a different command: argument
  (graphs / response-time / static-site / summary / uptime). The
  decomposition existed because each command produced a different
  artifact in upptime's model.
- Our model: probe emits raw probe results only. Status page (Vercel,
  separate PR) reads those JSONL files and renders graphs/summaries
  itself. One concern per tool, one workflow.

History migration: out of scope. Existing history/ JSON files (one
per site) stay untouched; the new probe writes a new
history/<slug>.jsonl alongside. Whether to back-fill or archive the
old format is a separate decision tracked in the issue body.

Status page rebuild: out of scope. Vercel app reading JSONL is
follow-up — first we want to see real probe data flowing for ~24h.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-08 01:14:48 +00:00
.github feat(ci): replace upptime with Gitea-native uptime probe (closes #2) 2026-05-08 01:14:48 +00:00
api 🍱 Update graphs [skip ci] 2026-04-19 01:16:33 +00:00
graphs 🍱 Update graphs [skip ci] 2026-04-19 01:16:33 +00:00
history 🟥 Canvas — legal redirect is down (404 in 6 ms) [skip ci] [upptime] 2026-04-19 23:24:15 +00:00
.gitattributes 📝 Update summary in README [skip ci] [upptime] 2026-04-15 21:23:47 +00:00
.gitignore chore: gitignore credentials for molecule-ai-status 2026-04-16 09:18:42 -07:00
.upptimerc.yml fix(post-suspension): migrate github.com/Molecule-AI refs to git.moleculesai.app (Class G #168) 2026-05-07 13:02:21 -07:00
LICENSE chore: initial Upptime scaffold for status.moleculesai.app 2026-04-15 14:20:45 -07:00
README.md fix(post-suspension): migrate github.com/Molecule-AI refs to git.moleculesai.app (Class G #168) 2026-05-07 13:02:21 -07:00

📈 Live Status: 🟧 Partial outage

This repository contains the open-source uptime monitor and status page for Molecule AI, powered by Upptime.

Uptime CI Response Time CI Graphs CI Static Site CI Summary CI

📊 Overall Uptime

URL Status History Response time Uptime
Customer app 🟩 Up customer-app.yml
Response time graph 278ms
Response time 278
24-hour response time 275
7-day response time 278
30-day response time 278
1-year response time 278
100.00%Uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%
Docs site 🟩 Up docs-site.yml
Response time graph 247ms
Response time 247
24-hour response time 258
7-day response time 247
30-day response time 247
1-year response time 247
98.21%Uptime 98.21%
24-hour uptime 100.00%
7-day uptime 98.21%
30-day uptime 98.21%
1-year uptime 98.21%
Control plane API 🟩 Up control-plane-api.yml
Response time graph 168ms
Response time 168
24-hour response time 418
7-day response time 168
30-day response time 168
1-year response time 168
24.13%Uptime 24.13%
24-hour uptime 0.01%
7-day uptime 24.13%
30-day uptime 24.13%
1-year uptime 24.13%
Control plane — Legal pages 🟩 Up control-plane-legal-pages.yml
Response time graph 75ms
Response time 75
24-hour response time 197
7-day response time 75
30-day response time 75
1-year response time 75
24.13%Uptime 24.13%
24-hour uptime 0.00%
7-day uptime 24.13%
30-day uptime 24.13%
1-year uptime 24.13%
Landing page 🟩 Up landing-page.yml
Response time graph 229ms
Response time 229
24-hour response time 263
7-day response time 229
30-day response time 229
1-year response time 229
100.00%Uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%
Canvas — pricing route 🟥 Down canvas-pricing-route.yml
Response time graph 34ms
Response time 34
24-hour response time 21
7-day response time 34
30-day response time 34
1-year response time 34
0.00%Uptime 0.00%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 0.00%
1-year uptime 0.00%
Canvas — legal redirect 🟥 Down canvas-legal-redirect.yml
Response time graph 28ms
Response time 28
24-hour response time 18
7-day response time 28
30-day response time 28
1-year response time 28
0.00%Uptime 0.00%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 0.00%
1-year uptime 0.00%

License