Skip to content

PlaidCloud/plaidcloud-status

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

165 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

PlaidCloud Status

Public status page and incident history for the PlaidCloud platform, powered by Upptime. Uptime checks run on GitHub Actions, incidents are tracked as GitHub Issues, and the page is served from GitHub Pages.

This runs entirely on GitHub, independent of PlaidCloud infrastructure β€” so the status page stays up even when PlaidCloud is down. That isolation is the whole point of a status page.

πŸ”— Live page: https://status.plaidcloud.com

πŸ“ˆ Live status: 🟩 All systems operational

URL Status History Response Time Uptime
Organization and Workspace Management 🟩 Up app.yml
Response time graph 180ms
Response time 186
24-hour response time 213
7-day response time 180
30-day response time 186
1-year response time 186
100.00%All-time uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%
Documentation Website 🟩 Up docs.yml
Response time graph 101ms
Response time 123
24-hour response time 133
7-day response time 101
30-day response time 123
1-year response time 123
100.00%All-time uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%
PlaidCloud Website 🟩 Up website.yml
Response time graph 246ms
Response time 260
24-hour response time 78
7-day response time 246
30-day response time 260
1-year response time 260
100.00%All-time uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%

The table above is generated automatically by Upptime. Don't edit between the status pages markers β€” your changes will be overwritten.

How it works

  • Every ~5 minutes, GitHub Actions probes each site from outside PlaidCloud (so it sees what users see).
  • A failing check auto-opens a GitHub Issue (an incident) and auto-closes it on recovery.
  • Maintainers can also open incidents and maintenance windows manually via the issue templates.
  • The Svelte status page is rebuilt and deployed to GitHub Pages on every change.

Monitored components are defined in .upptimerc.yml.

Managing incidents & maintenance

Full workflow β€” severity levels, the 15-minute first-update rule, component slugs, communication style β€” is in RUNBOOK.md.

Quick version:

  • Incident β€” open a new issue with the Incident template, add the affected component's slug as a label (app, docs, website), post updates as comments, and close the issue to resolve.
  • Scheduled maintenance β€” open a new issue with the Scheduled Maintenance template and fill in the start / end / expectedDown block.

Subscribe

Setup & operations

First-time setup, required secrets, DNS, and GitHub Pages configuration are documented in CLAUDE.md.

Credits & license

Built on Upptime by Anand Chowdhary (MIT β€” see LICENSE). Monitoring data in history/ is under the Open Database License.

About

πŸ“ˆ Uptime monitor and status page for PlaidCloud, powered by @upptime

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors