Gemfury Status

Configuration & scaling improvements seem to be absorbing the traffic spikes more comfortably now. Resolving.

Jobs processing normally, and outstanding work has been completed. Resolving.

Production-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.

Resolving the incident to continue the investigation and fix offline.

Operations returned to normal. We will address the performance issue through our development cycle.

We'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.

**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 monitoring should have detected the failures, and prompted corrective action. However, our existing checks were only performing shallow availability tests and did not verify internal reachability, leading to a false positive. **Resolution** Once identified, clearing the DNS caches restored full connectivity and service availability. To prevent recurrence, we’ve extended our monitoring to include internal reachability probes, ensuring that similar issues are surfaced automatically in the future. **Closing** We understand how disruptive downtime can be, and we’re committed to learning from each incident to make our platform more resilient. Thank you again for your patience and continued trust.

Upstream issue has been resolved. We are back to normal. Resolving.

It 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.

Upstream incident has been resolved, and no problems otherwise. Resolving.

Successfully completed maintenance. Resolving.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

Maintenance completed.

The scheduled maintenance has been completed.

Everything looks good. Thank you for your patience everyone - we're working hard to return Gemfury to the level of stability that you've come to trust from us.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.