System Status
Live monitoringUptime Overview
Past 90 daysRecent Incidents
Resolved & activeUsers experienced intermittent 502 errors when making API calls. The issue was caused by an upstream load balancer misconfiguration. The engineering team rolled back the change and all endpoints are now responding normally.
June 28, 2025 — 03:14 UTCTransactional emails were experiencing delayed delivery (5–15 minutes). The SMTP queue was backed up due to a DNS TTL expiration on our mail relay. DNS has been corrected and the queue has fully drained.
June 14, 2025 — 11:02 UTCThe customer portal was returning 503 errors for users attempting to access billing pages. A database connection pool exhaustion was identified and resolved by restarting the connection manager.
May 29, 2025 — 08:47 UTCSearch results were returning stale data due to an indexing lag. The Elasticsearch cluster was re-indexed and search results are now up to date.
May 12, 2025 — 16:30 UTCLatest Incident Timeline
Resolved
All API endpoints are back to normal. Monitoring confirms stable response times.
04:42 UTCUpdate
Load balancer configuration has been rolled back. Endpoint response times are recovering.
04:18 UTCIdentified
Root cause identified: upstream load balancer route misconfiguration from the last deployment.
03:45 UTCInvestigating
We've detected intermittent 502 errors on the API. Our team is actively investigating.
03:14 UTCScheduled Maintenance
Database Cluster Upgrade
PostgreSQL version upgrade from 15.x to 16.x. Brief connection resets expected.
02:00 – 04:00 UTCCDN Cache Refresh
Full CDN cache purge and SSL certificate renewal across all edge nodes.
01:00 – 02:00 UTCSecurity Patch Rollout
Application server security patches. Zero-downtime rolling deployment planned.
03:00 – 05:00 UTCStay Updated
Subscribe to get notified about incidents and scheduled maintenance via email, SMS, or RSS.