Stripe — degraded
2 July 2026 · 15 h 15 min
Service reporting degraded (HTTP 200). Auto-resolved after recovery.
Current status
Web
The askbrigid.com marketing surface — covers every public landing page.
- Operational
Landing page
79 ms · HTTP 200
App
The React app at auth.askbrigid.com — dashboard, outreach, settings, billing.
- Operational
Web app
31 ms · HTTP 200
- Operational
Dashboard
46 ms · HTTP 200
- Operational
Outreach
46 ms · HTTP 200
- Operational
Settings
46 ms · HTTP 200
- Operational
Billing (Stripe-connected)
46 ms · HTTP 200
Auth
Sign-in and sign-up endpoints — gateway into the app.
- Operational
Sign-in
46 ms · HTTP 200
- Operational
Controlled access handoff
48 ms · HTTP 200
API
Server endpoints exposed by the marketing site, including Brigid health.
- Operational
Brigid AI agent
272 ms · HTTP 200
- Operational
Database & API (Supabase)
229 ms · HTTP 200
- Operational
Status API
0 ms · HTTP 200
External
Third-party dependencies surfaced from their public status APIs (Stripe, etc.).
- Operational
Stripe
151 ms · HTTP 200
12 services monitored. Probes run every 30 s. Cached 30 s. A service shows Unknown when our check was turned away by a bot challenge (HTTP 429) or could not be read. That is not an outage, and it is not counted in uptime.
90-day uptime
90 days agoToday
100.00% uptime0 minor incidents0 major incidentsgrey = no data
Recent incidents
Resolved
Brigid AI agent — monitoring false alarm
1 June 2026 · false alarm
The hourly snapshot probe was misconfigured to check localhost instead of production, so this health check could never succeed. No user-facing outage occurred. The monitoring configuration has been fixed.