https://approjects-vendor-status-watch.static.hf.space/v/gemfury.htmlIncidents from Gemfury's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/vw223zl5r73mgemfury:2026-08-09T06:38:22.473-07:00Sun, 09 Aug 2026 13:38:22 +0000Errors have returned to normal levels. Fix confirmed. Resolving.https://stspg.io/jtntfl4gfhyfgemfury:2026-05-20T06:20:22.000-07:00Wed, 20 May 2026 13:20:22 +0000Configuration & scaling improvements seem to be absorbing the traffic spikes more comfortably now. Resolving.https://stspg.io/h7kcrh3l5dp5gemfury:2026-03-25T00:44:39.424-07:00Wed, 25 Mar 2026 07:44:39 +0000Jobs processing normally, and outstanding work has been completed. Resolving.https://stspg.io/yz7bqxctkr2tgemfury:2026-03-24T09:34:53.654-07:00Tue, 24 Mar 2026 16:34:53 +0000Production-specific misconfiguration caused our async workers to enter a crash-restart loop. We've fixed the issue, and we will be looking into how to catch these issues earlier in the release process. Resolving.https://stspg.io/w807zc1hmylsgemfury:2026-03-16T08:41:58.570-07:00Mon, 16 Mar 2026 15:41:58 +0000Resolving the incident to continue the investigation and fix offline.https://stspg.io/p92k9q68j7v2gemfury:2026-02-21T20:59:17.981-08:00Sun, 22 Feb 2026 04:59:17 +0000Operations returned to normal. We will address the performance issue through our development cycle.https://stspg.io/dw0mc2sbg7dggemfury:2026-02-09T03:21:42.872-08:00Mon, 09 Feb 2026 11:21:42 +0000We've tracked the issue down to a frequent DB update and applied a fix to reduce it. Resolving the incident while we will keep monitoring the fix.https://stspg.io/d9ysxqqlzq1dgemfury:2025-10-20T08:59:53.000-07:00Mon, 20 Oct 2025 15:59:53 +0000**Summary** First, we want to thank everyone for your patience as we worked through this incident. After restoring platform availability, we noticed that some services \(e.g. uploads\) did not immediately recover. This postmortem explains what happened, what we found, and what we’re doing to prevent similar issues in the future. **What Happened** The platform experienced a temporary availability outage that affected several services. While core systems came back online as expected, a subset of services continued to experience availability issues after the upstream outage. **Root Cause** The affected services were still using stale DNS cache entries from during the outage, preventing them from reaching other internal components. While DNS caching is technically correct, our monitorihttps://stspg.io/jtbfzvx230s3gemfury:2025-10-20T03:15:37.253-07:00Mon, 20 Oct 2025 10:15:37 +0000Upstream issue has been resolved. We are back to normal. Resolving.https://stspg.io/7r2167vrv7drgemfury:2025-09-18T08:37:01.308-07:00Thu, 18 Sep 2025 15:37:01 +0000It appears a misplaced space in a configuration update of caused the configured library to throw exceptions for some of the requests. We've fixed the configuration and will be patching the library to ensure this is handled more gracefully. Resolving.