Previous incidents

Resolved. The cause was an API failure at our authentication provider (Clerk) that prevented some users from signing in between approximately 5:30 PM and 6:08 PM ET. Sign-in has returned to normal and existing sessions were unaffected throughout.

Resolved. Our hosting provider (Railway) experienced a multi-hour outage stemming from a Google Cloud disruption, which took the entire platform offline between approximately 6:31 PM and 9:48 PM ET. All services have been restored. No data was lost.

Resolved. Intermittent timeouts caused elevated errors on the API and writing analysis between approximately 8:00 PM and 10:30 PM ET. Service has recovered.

Resolved. Some users experienced sign-in failures for approximately 29 minutes between 12:27 AM and 12:56 AM ET. Existing sessions were unaffected and service has recovered.