System status
The current state of Mosco, component by component, plus a record of recent incidents. This page is an illustrative status display, not a live monitoring feed — when our real-time status endpoint ships, it will replace this view automatically.
Some services are degraded
Every part of the platform
API, dashboard, voice and calls, AI agents, billing, and the integrations that connect them.
Public API
OperationalDashboard web app
OperationalUnified Inbox
OperationalSMS / WhatsApp (Twilio)
DegradedElevated latency on Twilio webhook delivery — investigating upstream.
Facebook / Instagram
OperationalVoice AI (Speed Dialer)
OperationalAI Agents runtime
OperationalStripe billing
Operational
What broke, and how we fixed it
Recent incidents with a plain post-mortem for each. We write these so you can see exactly what happened.
Elevated Twilio webhook latency
investigatingStarted recently · ongoing · Minor severity
We're seeing p95 webhook delivery latency above 2s on the Twilio path. No messages are lost, but dispatcher reply time is elevated. Team is working with Twilio support.
Brief outage of Meta Messenger integration
resolvedResolved · about 1.5h to recover · Major severity
Meta rotated credentials on their OAuth endpoint without notice. Restored connection by refreshing tokens for affected tenants. Post-mortem: we now run a background token-validity sweep every 15 minutes.
Dashboard slow initial load
resolvedResolved · rolled back within 30 minutes · Minor severity
A bad migration caused dashboard first-paint to exceed 4s for a subset of accounts. Rolled back within 30 minutes. Root cause: unnecessary JOIN in the workspace-bootstrap query.
Get a heads-up on incidents
Want a note when something changes? Email-based incident updates are on the way. Until then, reach our team directly and we'll keep you posted.