Incidents | harshalmore31 Incidents reported on status page for harshalmore31 https://status.harshalmore.dev/ en nss-db recovered https://status.harshalmore.dev/ Mon, 16 Mar 2026 00:31:01 +0000 https://status.harshalmore.dev/#54e0a0227ee0d750b97d47f6a9708eeab032bb81411c3fde652e0a01a8855ecb nss-db recovered nss-db went down https://status.harshalmore.dev/ Mon, 16 Mar 2026 00:30:02 +0000 https://status.harshalmore.dev/#54e0a0227ee0d750b97d47f6a9708eeab032bb81411c3fde652e0a01a8855ecb nss-db went down vidyaverve-db recovered https://status.harshalmore.dev/ Sat, 14 Mar 2026 14:49:02 +0000 https://status.harshalmore.dev/#e73409796aa2353681c68cf51133924bd3b2209973c919f495a2884ed98acd78 vidyaverve-db recovered vidyaverve-db went down https://status.harshalmore.dev/ Sat, 14 Mar 2026 14:48:02 +0000 https://status.harshalmore.dev/#e73409796aa2353681c68cf51133924bd3b2209973c919f495a2884ed98acd78 vidyaverve-db went down vidyaverve-db recovered https://status.harshalmore.dev/ Fri, 13 Mar 2026 19:46:01 +0000 https://status.harshalmore.dev/#51ff0749d0567e70def3c346d20f592c13fa00400d57422a29676d62a6f2c9b1 vidyaverve-db recovered vidyaverve-db went down https://status.harshalmore.dev/ Fri, 13 Mar 2026 19:45:01 +0000 https://status.harshalmore.dev/#51ff0749d0567e70def3c346d20f592c13fa00400d57422a29676d62a6f2c9b1 vidyaverve-db went down nss-db recovered https://status.harshalmore.dev/ Tue, 10 Mar 2026 19:13:01 +0000 https://status.harshalmore.dev/#fb6ce67e76d58b72d07eb7d25ec747c543d8da81c6d0421c0fa03e41b74791d6 nss-db recovered nss-db went down https://status.harshalmore.dev/ Tue, 10 Mar 2026 19:12:00 +0000 https://status.harshalmore.dev/#fb6ce67e76d58b72d07eb7d25ec747c543d8da81c6d0421c0fa03e41b74791d6 nss-db went down vidyaverve-db recovered https://status.harshalmore.dev/ Sun, 08 Mar 2026 23:55:01 +0000 https://status.harshalmore.dev/#76f8911c7601f2ba69e4ed6ece5fcb299b8fe5e3e6a0d2a1f6f08e9d5df5eb27 vidyaverve-db recovered vidyaverve-db went down https://status.harshalmore.dev/ Sun, 08 Mar 2026 23:54:04 +0000 https://status.harshalmore.dev/#76f8911c7601f2ba69e4ed6ece5fcb299b8fe5e3e6a0d2a1f6f08e9d5df5eb27 vidyaverve-db went down nss-db recovered https://status.harshalmore.dev/ Tue, 03 Mar 2026 13:26:01 +0000 https://status.harshalmore.dev/#10ce2bcdf8fa9ea370b2aa7633fb9eb91b32ffaf96587fa91f03f2347f18b803 nss-db recovered nss-db went down https://status.harshalmore.dev/ Tue, 03 Mar 2026 13:25:03 +0000 https://status.harshalmore.dev/#10ce2bcdf8fa9ea370b2aa7633fb9eb91b32ffaf96587fa91f03f2347f18b803 nss-db went down nss-db recovered https://status.harshalmore.dev/ Sat, 28 Feb 2026 20:38:00 +0000 https://status.harshalmore.dev/#5f61558bce6e73590f2fd75bcb9d6c164991292d3a3a5e828b667085de1bb3b7 nss-db recovered nss-db went down https://status.harshalmore.dev/ Sat, 28 Feb 2026 20:37:01 +0000 https://status.harshalmore.dev/#5f61558bce6e73590f2fd75bcb9d6c164991292d3a3a5e828b667085de1bb3b7 nss-db went down Fix the issues https://status.harshalmore.dev/incident/571175 Mon, 19 May 2025 10:05:00 -0000 https://status.harshalmore.dev/incident/571175#e0e398414e004f8f1becd1629fb89a64312b29b4ba45783eed21ed2b9252e048 There were some issue server side, there won't be disruption further Temporary Database Downtime Due to Server Region https://status.harshalmore.dev/incident/563056 Tue, 13 May 2025 21:22:00 -0000 https://status.harshalmore.dev/incident/563056#1d026177960634eed4ba43b956d76880cddfbf556156d60fe20aab6eea9f18f6 Status: Resolved Duration: 19 minutes Start Time: 2:28 AM IST, 14 May 2025 End Time: 2:47 AM IST, 14 May 2025 Impact: Temporary unavailability of database services Summary: At 2:28 AM IST on 14 May 2025, our database services became temporarily unavailable due to an ongoing server region migration from West US to Central EU. The migration was part of a planned infrastructure improvement to enhance latency and availability in target regions. During the transition, database connectivity was interrupted as the service was reinitialized in the new region. This brief downtime triggered internal monitoring alerts and temporarily affected components dependent on the database. The migration completed successfully, and services were restored by 2:47 AM IST, bringing the total downtime to 19 minutes. No manual intervention was required post-deployment, and normal operations resumed automatically. Fixed all the issues https://status.harshalmore.dev/incident/560248 Sun, 11 May 2025 20:49:00 -0000 https://status.harshalmore.dev/incident/560248#253f72546b48d98b8869b8b367b7bd2eca975f71132dbff3d0ac013127fbe1a4 Fixed the Inconsistency in response from the database servers Now operational, no inconsistency further anymore items-supabase Heartbeat Monitor Issue https://status.harshalmore.dev/incident/560224 Sun, 11 May 2025 19:32:00 -0000 https://status.harshalmore.dev/incident/560224#b2593696bea75000d7bc664f876444a74ca5ca1f73fa678d30b9a3579d8e77ba Date: May 12, 2025 Duration: 12:24 AM – 12:39 AM IST What happened: Our scheduled health-check function began returning errors during initial deployment and integration with BetterStack, triggering the heartbeat monitor. Impact: Internal monitoring alerts only—no user-facing downtime. Resolution: Deployment fixes and configuration updates were applied; successful heartbeats resumed, and the incident cleared automatically. Next steps: We’ve tightened our deployment checklist and added validation to prevent recurrence.