Incidents reported on status page for MageMetrics https://status.magemetrics.com/ https://d1lppblt9t2x15.cloudfront.net/logos/ae7f94f1f3745cf83553a7cf4c4a56b1.png https://status.magemetrics.com/ en https://status.magemetrics.com/incident/813625 Wed, 28 Jan 2026 14:39:00 -0000 https://status.magemetrics.com/incident/813625#e38f79e76661ecb0ea5041304032b8fa83c617ae4473d96197fedf027bbe09ea On Wednesday, January 28, 2026, we experienced a brief outage during scheduled maintenance by our infrastructure provider Supabase. The maintenance involved updates to their DBMS backup mechanism. Following the maintenance, our database instance did not restart automatically as expected, causing connection failures. Because we were actively monitoring throughout the scheduled maintenance window, we quickly identified the issue and performed a manual restart, restoring full service within minutes. We are working with Supabase support to understand why the automatic restart failed and to prevent similar issues during future maintenance windows. https://status.magemetrics.com/incident/813625 Wed, 28 Jan 2026 14:39:00 -0000 https://status.magemetrics.com/incident/813625#e38f79e76661ecb0ea5041304032b8fa83c617ae4473d96197fedf027bbe09ea On Wednesday, January 28, 2026, we experienced a brief outage during scheduled maintenance by our infrastructure provider Supabase. The maintenance involved updates to their DBMS backup mechanism. Following the maintenance, our database instance did not restart automatically as expected, causing connection failures. Because we were actively monitoring throughout the scheduled maintenance window, we quickly identified the issue and performed a manual restart, restoring full service within minutes. We are working with Supabase support to understand why the automatic restart failed and to prevent similar issues during future maintenance windows. https://status.magemetrics.com/incident/813625 Wed, 28 Jan 2026 14:28:12 -0000 https://status.magemetrics.com/incident/813625#c4765d7f7e274ad7f9e6b8ea3aa5faaf352216acd40c94660e1677f910752dbd Read service went down. https://status.magemetrics.com/incident/813625 Wed, 28 Jan 2026 14:27:41 -0000 https://status.magemetrics.com/incident/813625#d65fd8116fb6e03a9dedec5196b570133c7750d3853cb4854554730910aa04db Write service went down. https://status.magemetrics.com/incident/806289 Sat, 17 Jan 2026 13:54:00 -0000 https://status.magemetrics.com/incident/806289#510e7a21ad5d86b4e5ddd8f79c3b1acbc1f945bf45b07b406c3fc6d55c9af08f On Saturday, January 17, 2026, our API endpoints experienced a brief outage due to PostgreSQL connection failures in our Supabase infrastructure. Upon investigation, we identified a transient connectivity issue with no security or configuration problems detected. The issue appears to have originated from upstream infrastructure providers (Supabase/AWS). We performed a database project restart which successfully restored full service availability within minutes. https://status.magemetrics.com/incident/806289 Sat, 17 Jan 2026 13:54:00 -0000 https://status.magemetrics.com/incident/806289#510e7a21ad5d86b4e5ddd8f79c3b1acbc1f945bf45b07b406c3fc6d55c9af08f On Saturday, January 17, 2026, our API endpoints experienced a brief outage due to PostgreSQL connection failures in our Supabase infrastructure. Upon investigation, we identified a transient connectivity issue with no security or configuration problems detected. The issue appears to have originated from upstream infrastructure providers (Supabase/AWS). We performed a database project restart which successfully restored full service availability within minutes. https://status.magemetrics.com/incident/806289 Sat, 17 Jan 2026 13:41:44 -0000 https://status.magemetrics.com/incident/806289#b0e88519a62b853f80689dfb1830556725dd771bc21bf724b91df69802c5913f Write service went down. https://status.magemetrics.com/incident/806289 Sat, 17 Jan 2026 13:40:54 -0000 https://status.magemetrics.com/incident/806289#088a68fa5a7078e65e9195354e2b8702834b64a1f25bc25971dde6644845d461 Read service went down.