System Status

Last updated September 1, 2026

All systems operational

Components

Web app
keepingup.com — dashboard, sign-in, onboarding, AI Advisor, settings · Provider: Vercel status ↗
Operational
Mobile app
iOS app (TestFlight beta) — feature parity with web for read views · Provider: Expo status ↗
Operational
Bank sync
Transaction, balance, and identity data from your connected accounts · Provider: Plaid status ↗
Operational
Authentication
Sign-in, sign-up, and session management · Provider: Clerk status ↗
Operational
Payments
Pro subscription billing · Provider: Stripe status ↗
Operational
AI Advisor
Personalized recommendations and chat (Pro feature) · Provider: Anthropic status ↗
Operational
Database
Customer data store; benchmark cohort cache · Provider: Neon status ↗
Operational
Email delivery
Transactional email — sign-in codes, alerts, support replies · Provider: Resend status ↗
Operational

Recent incidents

No incidents to report. Once we have any, we'll post a summary here with timeline, impact, root cause, and the fix — and we'll email affected users directly per our Privacy Policy breach-notification commitments.

How we operate

Keeping Up runs on Vercel with a global CDN, single-region Postgres (Neon), and a small set of specialized third-party providers for authentication, bank connections, payments, and AI. We use the provider best-in-class for each function rather than building everything in-house — when one of them has an incident, you can see it directly above and check their status page for ETA.

For confirmed material incidents, we notify affected users by email within 72 hours per our Privacy Policy.

Seeing something off?

If you're experiencing an issue not reflected above, please email support@keepingup.com. Jon (our founder) reads every message and replies within 24 hours.