Service status
Live monitoring of all customer-facing services. Data refreshes every 60 seconds from our external monitor.
Components
Detailed history: stats.uptimerobot.com/BME80NvbTk (multi-region checks, 5-minute interval, on-call email at first failure).
Service-level commitments
These commitments are written into our standard Data Privacy Agreement (§7A) for every customer engagement. Pre-pilot phase: best-effort outside business hours; full 24/7 coverage triggers at 10 paid customers or 1 district-scale deployment.
| Metric | Commitment | Definition |
|---|---|---|
| Uptime | 99.5% / month | Measured by external monitor on 5-min intervals |
| Recovery Time Objective | 4 hours | Acknowledged outage to restored service |
| Recovery Point Objective | 1 minute | Firestore Point-in-Time Recovery is enabled with a seven (7) day window and one-minute restore granularity. Daily Firebase-managed snapshots provide a second recovery lane with a fourteen (14) day retention window. Database delete-protection is enabled. Project-isolated out-of-band export to a separately-owned destination is the next backup-isolation upgrade and is committed before the first signed pilot agreement. |
| Acknowledgment | 60 minutes (business) / 4 hours (overnight) | Alert to operator response |
Incident severity
- SEV-0 — total outage. All comms, all-hands until resolved.
- SEV-1— major degradation, >50% users affected. Same response.
- SEV-2 — partial degradation, subset of features. 24-hour resolution target.
- SEV-3 — minor issue with workaround. Tracked in normal release cadence.
Reporting an issue
If you're a teacher, school or district contact, or parent and you're experiencing a service issue:
- Check this page first. If we're tracking the issue, it'll be listed at the top.
- Email support@potatoclass.com with a short description, a screenshot if possible, and your time zone. We respond within 60 minutes during business hours.
- For SEV-0 / SEV-1 issues affecting an active pilot, your school or district IT contact should also have a direct line — see your DPA §7A.
For security issues
If you've found a security vulnerability, do not report it via email. Use the responsible-disclosure form at growingstandard.com/security — that path runs through a dedicated security workflow with safe-harbor commitments, separate from operational incidents.
Last reviewed: 2026-04-26. Live data via UptimeRobot read-only API, proxied through Cloudflare Worker, refreshed every 60 seconds.