Incidents reported on status page for harshalmore31 https://status.harshalmore.dev/ en https://status.harshalmore.dev/ Sat, 23 May 2026 04:02:06 +0000 https://status.harshalmore.dev/#9aa6b4c214626da2a33711938665798bdd182f57b778119dbd158eccfcd8b3b7 vidyaverve-db recovered https://status.harshalmore.dev/ Sat, 23 May 2026 04:01:21 +0000 https://status.harshalmore.dev/#9aa6b4c214626da2a33711938665798bdd182f57b778119dbd158eccfcd8b3b7 vidyaverve-db went down https://status.harshalmore.dev/ Fri, 22 May 2026 01:25:06 +0000 https://status.harshalmore.dev/#a04ba8aeb1305aceb4ef0a78fc769d316115bbb25e47e0108a140dd652f8c05c vidyaverve-db recovered https://status.harshalmore.dev/ Fri, 22 May 2026 01:24:05 +0000 https://status.harshalmore.dev/#a04ba8aeb1305aceb4ef0a78fc769d316115bbb25e47e0108a140dd652f8c05c vidyaverve-db went down https://status.harshalmore.dev/ Thu, 21 May 2026 14:20:57 +0000 https://status.harshalmore.dev/#264f5fe14d42714dd66bc93f1996a341d7a3a66070e1d2562f2bb4972c495b35 nss-db recovered https://status.harshalmore.dev/ Thu, 21 May 2026 14:12:54 +0000 https://status.harshalmore.dev/#264f5fe14d42714dd66bc93f1996a341d7a3a66070e1d2562f2bb4972c495b35 nss-db went down https://status.harshalmore.dev/ Thu, 21 May 2026 14:07:57 +0000 https://status.harshalmore.dev/#94e121a9846ce52052aa376caf937491f0c6e75f9ee4a67e040195dd4e9daa81 vidyaverve-db recovered https://status.harshalmore.dev/ Thu, 21 May 2026 14:07:25 +0000 https://status.harshalmore.dev/#bbe73e119e8b95c9d7c22bd6879316dffa3fe2640dad22416e79b3e40bb9faaf nss-db recovered https://status.harshalmore.dev/ Thu, 21 May 2026 14:05:19 +0000 https://status.harshalmore.dev/#bbe73e119e8b95c9d7c22bd6879316dffa3fe2640dad22416e79b3e40bb9faaf nss-db went down https://status.harshalmore.dev/ Thu, 21 May 2026 14:05:18 +0000 https://status.harshalmore.dev/#94e121a9846ce52052aa376caf937491f0c6e75f9ee4a67e040195dd4e9daa81 vidyaverve-db went down https://status.harshalmore.dev/ Thu, 21 May 2026 13:57:36 +0000 https://status.harshalmore.dev/#1ee85325972936caaec965771b9b950e6ebc51aafd8eb1b0a769dbcde9c618a5 vidyaverve-db recovered https://status.harshalmore.dev/ Thu, 21 May 2026 13:55:24 +0000 https://status.harshalmore.dev/#1ee85325972936caaec965771b9b950e6ebc51aafd8eb1b0a769dbcde9c618a5 vidyaverve-db went down https://status.harshalmore.dev/ Thu, 21 May 2026 13:52:51 +0000 https://status.harshalmore.dev/#f22f1a5ddb04bc473201acec404c25d3a035d8a8d71eac33304de60945ce0eff vidyaverve-db recovered https://status.harshalmore.dev/ Thu, 21 May 2026 13:50:35 +0000 https://status.harshalmore.dev/#f22f1a5ddb04bc473201acec404c25d3a035d8a8d71eac33304de60945ce0eff vidyaverve-db went down https://status.harshalmore.dev/ Sat, 16 May 2026 11:28:02 +0000 https://status.harshalmore.dev/#36733dda9b5dfb4aece33d00c5d3d1400254ae13256b8eeac063ee6eef641a73 vidyaverve-db recovered https://status.harshalmore.dev/ Sat, 16 May 2026 11:27:02 +0000 https://status.harshalmore.dev/#36733dda9b5dfb4aece33d00c5d3d1400254ae13256b8eeac063ee6eef641a73 vidyaverve-db went down https://status.harshalmore.dev/ Fri, 15 May 2026 14:10:01 +0000 https://status.harshalmore.dev/#196c88c43aaef3d248e409779bf94e5fb9564fee78cfe78b87748a2ddd81c08e nss-db recovered https://status.harshalmore.dev/ Fri, 15 May 2026 14:09:02 +0000 https://status.harshalmore.dev/#196c88c43aaef3d248e409779bf94e5fb9564fee78cfe78b87748a2ddd81c08e nss-db went down 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 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. 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 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.