Incidents reported on status page for Capture https://status.capture.page/ https://d1lppblt9t2x15.cloudfront.net/logos/539f99e1605c32a2df3c0deede2c9bdd.png https://status.capture.page/ en https://status.capture.page/ Mon, 20 Oct 2025 08:19:51 +0000 https://status.capture.page/#65c96fe77ff9ff30407aa6c948b264e0b4f05c8a69c9555bbb36a25c25942cdd capture.page recovered https://status.capture.page/ Mon, 20 Oct 2025 08:09:53 +0000 https://status.capture.page/#65c96fe77ff9ff30407aa6c948b264e0b4f05c8a69c9555bbb36a25c25942cdd capture.page went down https://status.capture.page/incident/744499 Wed, 15 Oct 2025 14:13:00 -0000 https://status.capture.page/incident/744499#cb0d59920627ea002e58d7828daa9039e08f24d3ef21bc25a26ec4deae5b0818 Resolution: Configuration corrected and redeployed; services monitored to confirm stability. Incident fully resolved by Thu, Oct 16, 2025 01:00 AEDT. Systems are operating normally. Additional safeguards added to prevent recurrence (config validation checks and rollout gates). https://status.capture.page/incident/744499 Wed, 15 Oct 2025 08:00:00 -0000 https://status.capture.page/incident/744499#628f9b1e22200c4058a47d48ab358f03488615cb4c9c642863585f5df592b05d What happened: Starting Wed, Oct 15, 2025 19:00 AEDT, a bad server configuration led to intermittent request failures, surfacing as 5xx errors across impacted endpoints. Impact: Sporadic error responses and degraded reliability for some requests; no data loss observed. Root cause: Incorrect server configuration introduced unstable behavior under normal load, triggering upstream error propagation. https://status.capture.page/ Thu, 02 Oct 2025 12:25:46 +0000 https://status.capture.page/#fe79ef528b0adc446d4c7b52ef5a806a41058c906b24906eebf833c6d3146b83 cdn.capture.page (cdn.capture.techulus.in) recovered https://status.capture.page/ Thu, 02 Oct 2025 12:17:50 +0000 https://status.capture.page/#fe79ef528b0adc446d4c7b52ef5a806a41058c906b24906eebf833c6d3146b83 cdn.capture.page (cdn.capture.techulus.in) went down https://status.capture.page/incident/609658 Thu, 26 Jun 2025 15:02:22 -0000 https://status.capture.page/incident/609658#c2f0efbc2edf79e33ee2da07860d912ff383c8e5cbcb5a96b350cb5e201f3d53 cdn.capture.page (cdn.capture.techulus.in) recovered. https://status.capture.page/incident/609658 Thu, 26 Jun 2025 14:53:15 -0000 https://status.capture.page/incident/609658#a27ccb1d70e434197f6f88a251287018d3f779aa13b9bc4ea6c41ff076950b57 cdn.capture.page (cdn.capture.techulus.in) went down. https://status.capture.page/incident/495339 Mon, 13 Jan 2025 19:40:00 -0000 https://status.capture.page/incident/495339#3bced5e1eaf35bbbacf6523499cf049003b4138120bf4c892a55ed992ff2f73b We experienced intermittent request failures and high latency from 14 Jan 2025, 06:33 PM UTC to 07:47 PM UTC due to a proxy failure routing requests to servers. The issue is now resolved, and services are fully operational. We apologize for the disruption and are taking steps to prevent this in the future. https://status.capture.page/incident/423020 Mon, 02 Sep 2024 00:00:00 -0000 https://status.capture.page/incident/423020#2188e0409cd99d56cc7c69159b04bf004f083b4a7205f584f7bc76f085ced470 The downtime reported today was only for our health check endpoint, and the actual API endpoints were unaffected.