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/incident/900160 Wed, 20 May 2026 02:13:00 -0000 https://status.capture.page/incident/900160#5467a4e26c2dbdb4e1c1d99029caf78fd91ee0527e426a0bbfcd38a3242706d7 The intermittent errors affecting the Capture API have been resolved. The issue was caused by a major outage with our infrastructure provider, Railway. Railway has since restored service, and the Capture API is operating normally again. We’ll continue monitoring closely to ensure everything remains stable. https://status.capture.page/ Wed, 20 May 2026 01:48:38 +0000 https://status.capture.page/#60b3950ee1f48e983c42a5c49a9b5f48f5a66adcba29d3aea0141888c8f29b43 cdn.capture.page (cdn.capture.techulus.in) recovered https://status.capture.page/incident/900160 Tue, 19 May 2026 23:01:00 -0000 https://status.capture.page/incident/900160#20912eb33859c569999bbbee778a7a85d79a1fb753a2fbc632ee56248f93c29d We are currently seeing intermittent errors affecting the Capture API due to a major outage with our infrastructure provider, Railway. Our team is monitoring Railway’s status updates closely and will continue to track the issue until service is fully restored. Railway status: https://status.railway.com https://status.capture.page/ Tue, 19 May 2026 22:48:49 +0000 https://status.capture.page/#60b3950ee1f48e983c42a5c49a9b5f48f5a66adcba29d3aea0141888c8f29b43 cdn.capture.page (cdn.capture.techulus.in) went down https://status.capture.page/incident/884619 Thu, 30 Apr 2026 21:01:00 -0000 https://status.capture.page/incident/884619#01d155b0312a76b422c4b77340c5c5b954cfd8c2c0ac90bdaa7be9e9010b42c8 Our API services deployed on Railway experienced an outage after an invalid configuration caused all Railway services to hit a hard platform limit. As a result, Railway stopped the services and removed the active deployments, leaving the API unavailable. We corrected the build configuration and restored the affected services. The API is now operating normally. We apologise for the disruption. https://status.capture.page/ Thu, 30 Apr 2026 20:57:24 +0000 https://status.capture.page/#26ab3e9007e96c466e2906e1336e897ad7c9d67d575ca4f4246dd185a123a48c cdn.capture.page (cdn.capture.techulus.in) recovered https://status.capture.page/ Thu, 30 Apr 2026 18:33:36 +0000 https://status.capture.page/#26ab3e9007e96c466e2906e1336e897ad7c9d67d575ca4f4246dd185a123a48c cdn.capture.page (cdn.capture.techulus.in) went down https://status.capture.page/ Wed, 18 Feb 2026 08:27:40 +0000 https://status.capture.page/#7c9e19a563a97d7f135f3dfbbd62b1464e468e1cd16ff5fa2a1e8d6158d6c639 cdn.capture.page (cdn.capture.techulus.in) recovered https://status.capture.page/ Wed, 18 Feb 2026 08:22:17 +0000 https://status.capture.page/#7c9e19a563a97d7f135f3dfbbd62b1464e468e1cd16ff5fa2a1e8d6158d6c639 cdn.capture.page (cdn.capture.techulus.in) 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/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.