Capgo

Service availability and performance

Jan 26, 2026

6 months ago

Database at 100% CPU

Resolved · January 26 at 5:14 PM (UTC) (in 7 hours)

Our DDOS portection may have put your app in cache with 429 status (default when our DB cannot answer) If this is not resolved for you, or you need urgent release, please upload a version again this should clear cache. If you are still stuck please reach out we can fix manually

Resolved · January 26 at 1:46 PM (UTC) (3 hours earlier)

The issue is fully resolved

Monitoring · January 26 at 1:46 PM (UTC) (0 seconds earlier)

We are now back to 10% CPU as expected and are monitoring

Identified · January 26 at 1:43 PM (UTC) (3 minutes earlier)

We identified an issue on our plugin endpoint. An app that do not pay capgo anymore had a spike of Usage and still have ur plugin installed. The spike of usage did spamed our DB to send emails to the customer to notify him about the issue. We Implemented a change to ensure we cache the query and prevent overload.

Investigating · January 26 at 10:30 AM (UTC) (3 hours earlier)

Since this morning our CPU skyrocketed to 100% usage it seems correlated to Supabase issue reported here https://status.supabase.com We are monitoring and looking for solutions with Supabase teams. Updates already in our replicate will work without issue but new upload or switch channel are impacted