Incidents reported on status page for Techulus https://status.changes.page/ https://d1lppblt9t2x15.cloudfront.net/logos/bfd06d174c9e620962328ae5a0895fbf.png https://status.changes.page/ en https://status.changes.page/ Mon, 24 Nov 2025 10:01:01 +0000 https://status.changes.page/#f98cc08bf0c89f823dd855cdc1571d8ee2e29a1cf4ddd0040ac29e85b8f20212 hey.changes.page recovered https://status.changes.page/incident/773060 Mon, 24 Nov 2025 10:01:00 -0000 https://status.changes.page/incident/773060#09c4fd4b67ddccae1de24240121b53848cc2d4cbbc0e962b5b46d736bfccc37c Issue has been resolved, it was a temporary connection issue to our database provider. https://status.changes.page/incident/773060 Mon, 24 Nov 2025 10:01:00 -0000 https://status.changes.page/incident/773060#09c4fd4b67ddccae1de24240121b53848cc2d4cbbc0e962b5b46d736bfccc37c Issue has been resolved, it was a temporary connection issue to our database provider. https://status.changes.page/incident/773060 Mon, 24 Nov 2025 09:52:00 -0000 https://status.changes.page/incident/773060#438c19e8f7080f7851ea35e04b201f18fa86959b489a90acdff1f2433318b787 Intermittent errors are seen across dashboard and pages. Issue is currently under active investigation. https://status.changes.page/incident/773060 Mon, 24 Nov 2025 09:52:00 -0000 https://status.changes.page/incident/773060#438c19e8f7080f7851ea35e04b201f18fa86959b489a90acdff1f2433318b787 Intermittent errors are seen across dashboard and pages. Issue is currently under active investigation. https://status.changes.page/ Mon, 24 Nov 2025 09:45:55 +0000 https://status.changes.page/#f98cc08bf0c89f823dd855cdc1571d8ee2e29a1cf4ddd0040ac29e85b8f20212 hey.changes.page went down https://status.changes.page/incident/747245 Mon, 20 Oct 2025 18:48:00 -0000 https://status.changes.page/incident/747245#4107b47b54fc3f62b2cd987b9e7fe3c698b185ceeef27cd1ae3db26aa5a6741b Resolved: We are no longer observing issues with our infrastructure provider. https://status.changes.page/incident/747245 Mon, 20 Oct 2025 18:48:00 -0000 https://status.changes.page/incident/747245#4107b47b54fc3f62b2cd987b9e7fe3c698b185ceeef27cd1ae3db26aa5a6741b Resolved: We are no longer observing issues with our infrastructure provider. https://status.changes.page/incident/747245 Mon, 20 Oct 2025 10:50:00 -0000 https://status.changes.page/incident/747245#4981f8ea36ddcf1ecca5e36e0328e4fc1062bb0148a712403bede9062ccec5d4 We are currently seeing elevated error rates from our cloud provider’s API. Our engineering team is actively coordinating with these partners to mitigate impact and restore full functionality. Further updates will be provided as more information becomes available. https://status.changes.page/incident/747245 Mon, 20 Oct 2025 10:50:00 -0000 https://status.changes.page/incident/747245#4981f8ea36ddcf1ecca5e36e0328e4fc1062bb0148a712403bede9062ccec5d4 We are currently seeing elevated error rates from our cloud provider’s API. Our engineering team is actively coordinating with these partners to mitigate impact and restore full functionality. Further updates will be provided as more information becomes available. https://status.changes.page/incident/714067 Thu, 28 Aug 2025 10:58:00 -0000 https://status.changes.page/incident/714067#f5273a6ec6c62897f845bc2310f4c2026721176b186b80e3fe548fc93f692b13 Intermittent errors were caused by our database provider Supabase, it has now been resolved. Supabase incident: https://status.supabase.com/incidents/gvp38qdj3bm6 https://status.changes.page/incident/714067 Thu, 28 Aug 2025 10:58:00 -0000 https://status.changes.page/incident/714067#f5273a6ec6c62897f845bc2310f4c2026721176b186b80e3fe548fc93f692b13 Intermittent errors were caused by our database provider Supabase, it has now been resolved. Supabase incident: https://status.supabase.com/incidents/gvp38qdj3bm6 https://status.changes.page/incident/714067 Thu, 28 Aug 2025 09:54:00 -0000 https://status.changes.page/incident/714067#3c8ee26d2e99c081925882c1df7702fb494c2b738c5116f7054022d2f843d7f8 We are currently investigating intermittent errors affecting the change log page. Our team is actively working to identify the root cause and implement a fix. We'll provide updates as more information becomes available. Thank you for your patience. https://status.changes.page/incident/714067 Thu, 28 Aug 2025 09:54:00 -0000 https://status.changes.page/incident/714067#3c8ee26d2e99c081925882c1df7702fb494c2b738c5116f7054022d2f843d7f8 We are currently investigating intermittent errors affecting the change log page. Our team is actively working to identify the root cause and implement a fix. We'll provide updates as more information becomes available. Thank you for your patience. https://status.changes.page/incident/602159 Thu, 12 Jun 2025 20:00:00 -0000 https://status.changes.page/incident/602159#28ba83106636a7ff7a3331d217f29cb4c1915eabc2598545c21977509abe651d We believe connectivity issues are the result of a broad outage with our upstream provider. We are currently monitoring the situation, and they are posting updates to their own status page here: https://www.cloudflarestatus.com/incidents/25r9t0vz99rp https://status.changes.page/incident/219822 Tue, 13 Jun 2023 22:45:00 -0000 https://status.changes.page/incident/219822#fe6dac242c3ebf92e34492947d0d54cb8c51cf8d6f74abeda9e9c26d159a455c We regret to inform you that our service is currently facing service degradation across all pages. This unfortunate situation is a result of a significant outage affecting the AWS Lambda service, which is our provider for serverless compute. To get detailed updates regarding this incident, we recommend checking the AWS status page at https://health.aws.amazon.com/health/status. We apologize for any inconvenience caused and appreciate your patience during this time. https://status.changes.page/incident/219822 Tue, 13 Jun 2023 22:45:00 -0000 https://status.changes.page/incident/219822#fe6dac242c3ebf92e34492947d0d54cb8c51cf8d6f74abeda9e9c26d159a455c We regret to inform you that our service is currently facing service degradation across all pages. This unfortunate situation is a result of a significant outage affecting the AWS Lambda service, which is our provider for serverless compute. To get detailed updates regarding this incident, we recommend checking the AWS status page at https://health.aws.amazon.com/health/status. We apologize for any inconvenience caused and appreciate your patience during this time.