Gemfury Outage History

Gemfury is up right now

Pingoru has recorded 45 incidents for Gemfury: 7 in the last 12 months and 1 in the last 90 days.

Source: status.fury.co

45incidents recorded
7last 12 months
1last 90 days
2 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Gemfury in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202613 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202612 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 527 (0%)

Incidents, newest first

Major August 9, 2026 Elevated error rates for badge service 2h 8m Badge

Started Aug 09, 2026, 01:38 PM UTC· resolved Aug 09, 2026, 03:46 PM UTC

  1. investigating Aug 09, 2026, 01:38 PM UTC

    We are currently investigating this issue.

  2. identified Aug 09, 2026, 01:50 PM UTC

    Bots/crawlers are overwhelming the service. Adjusting throttling.

  3. monitoring Aug 09, 2026, 02:53 PM UTC

    Throttling adjustments are in place. Errors subsiding. Monitoring.

  4. resolved Aug 09, 2026, 03:46 PM UTC

    Errors have returned to normal levels. Fix confirmed. Resolving.

Read the full incident report →

Minor May 20, 2026 Investigating elevated repo errors 2h 35m Repo endpoints

Started May 20, 2026, 01:20 PM UTC· resolved May 20, 2026, 03:55 PM UTC

  1. investigating May 20, 2026, 01:20 PM UTC

    We're seeing unusual traffic to our repositories that are causing elevated errors and timeouts. We've investigating possible ways to miteigate this.

  2. monitoring May 20, 2026, 01:35 PM UTC

    The number of open connections to each server was reaching our configured limit. We have raised the limit. Monitoring.

  3. resolved May 20, 2026, 03:55 PM UTC

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

Read the full incident report →

Minor March 25, 2026 Elevated errors for uploads and asynchronous work 46m Uploads

Started Mar 25, 2026, 07:44 AM UTC· resolved Mar 25, 2026, 08:31 AM UTC

  1. investigating Mar 25, 2026, 07:44 AM UTC

    We are again seeing errors & delays for uploads. Investigating.

  2. monitoring Mar 25, 2026, 08:03 AM UTC

    Looks like some of the misconfiguration issues persisted from yesterday. A few of the queues were not processed, which prevented account updates from propagating to repositories. We have made a fix, and are now processing the backlog.

  3. resolved Mar 25, 2026, 08:31 AM UTC

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

Read the full incident report →

Minor March 24, 2026 Job processing delays & errors 2h 5m Uploads

Started Mar 24, 2026, 04:34 PM UTC· resolved Mar 24, 2026, 06:40 PM UTC

  1. investigating Mar 24, 2026, 04:34 PM UTC

    We are investigating delays in processing of uploads and other asynchronous work.

  2. resolved Mar 24, 2026, 06:40 PM UTC

    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.

Read the full incident report →

Minor March 16, 2026 Elevated errors 1h 41m Dashboard, Git server, API, Repo endpoints

Started Mar 16, 2026, 03:41 PM UTC· resolved Mar 16, 2026, 05:23 PM UTC

  1. investigating Mar 16, 2026, 03:41 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 16, 2026, 04:53 PM UTC

    We had a temporary 10x traffic increase on one of our backend services, which lead to elevated timeouts and errors. Error rates have now returned to normal while we continue to look for the root cause of that traffic spike.

  3. resolved Mar 16, 2026, 05:23 PM UTC

    Resolving the incident to continue the investigation and fix offline.

Read the full incident report →

Minor February 9, 2026 Elevated errors & timeouts 4h 59m Dashboard, API, Repo endpoints, Uploads and 1 more

Started Feb 09, 2026, 11:21 AM UTC· resolved Feb 09, 2026, 04:21 PM UTC

  1. investigating Feb 09, 2026, 11:21 AM UTC

    We are investigating elevated error and timeout rates.

  2. monitoring Feb 09, 2026, 11:30 AM UTC

    Unusual traffic spike seems to have temporarily overwhelmed one of our API endpoints. That spike has subsided, error/timeout rates are back to normal. We are monitoring while we continue to investigate.

  3. resolved Feb 09, 2026, 04:21 PM UTC

    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.

Read the full incident report →

Minor October 20, 2025 AWS outage effects 12h 40m Git server, API, Repo endpoints

Started Oct 20, 2025, 03:59 PM UTC· resolved Oct 21, 2025, 04:39 AM UTC

  1. identified Oct 20, 2025, 03:59 PM UTC

    We are reopening the incident due new availability issues related to AWS outage.

  2. monitoring Oct 20, 2025, 06:04 PM UTC

    We are continuing to monitor the upstream issue.

  3. resolved Oct 21, 2025, 04:39 AM UTC

    Upstream issue resolved. If you’re still having availability issues, don’t hesitate to contact us directly.

  4. postmortem Oct 24, 2025, 03:56 AM UTC

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

Read the full incident report →

Minor September 18, 2025 Elevated error rates 1h 51m Dashboard, Repo endpoints, Custom domains

Started Sep 18, 2025, 03:37 PM UTC· resolved Sep 18, 2025, 05:28 PM UTC

  1. investigating Sep 18, 2025, 03:37 PM UTC

    We are seeing elevated error rates. Investigating.

  2. monitoring Sep 18, 2025, 04:13 PM UTC

    We've found that the issue was triggered by a recent configuration update. We've rolled back the changes, and the error rates have returned to normal levels. Checking further into the changes that caused the failure.

  3. resolved Sep 18, 2025, 05:28 PM UTC

    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.

Read the full incident report →

Minor June 12, 2025 Timeouts for proxied npm registry 1h 40m Repo endpoints

Started Jun 12, 2025, 07:20 PM UTC· resolved Jun 12, 2025, 09:01 PM UTC

  1. identified Jun 12, 2025, 07:20 PM UTC

    We are seeing increased timeouts for proxied requests to the public npm registry. We are tracking the upstream issue with npmjs.org.

  2. resolved Jun 12, 2025, 09:01 PM UTC

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

Read the full incident report →

Minor June 10, 2025 Platform issues causing upload failures 14h 22m Uploads

Started Jun 10, 2025, 12:51 PM UTC· resolved Jun 11, 2025, 03:14 AM UTC

  1. investigating Jun 10, 2025, 03:51 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 10, 2025, 03:53 PM UTC

    Our asynchronous workers are not running due to platform issues, and thus cannot process uploads. We are waiting for updates from our platform provider.

  3. monitoring Jun 10, 2025, 05:27 PM UTC

    We were able to start some of the workers. Starting to work through the async task backlog.

  4. monitoring Jun 10, 2025, 07:20 PM UTC

    Although some platform instability persists, we have processed most of the asynchronous task backlog (uploads, emails, etc.). Most functionality has been restored. We will continue monitoring the status of the platform until resolution. If you're still experiencing delays or issues with your account, please contact [email protected] with full details.

  5. monitoring Jun 10, 2025, 07:20 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Jun 11, 2025, 03:14 AM UTC

    We are resolving this as we are no longer seeing customer-facing errors. We'll continue to monitor both our and the platform's status to address any issues that may arise.

Read the full incident report →

Minor November 20, 2024 Elevated errors after deployment 1h 36m Dashboard, API, Repo endpoints

Started Nov 20, 2024, 06:48 AM UTC· resolved Nov 20, 2024, 08:24 AM UTC

  1. monitoring Nov 20, 2024, 06:48 AM UTC

    We've deployed an update that caused elevated errors due to a caching error that didn't surface during testing. We've rolled back the update, implemented a fix, and rolled out the fixed update. Monitoring.

  2. resolved Nov 20, 2024, 08:24 AM UTC

    The fix was effective. Service fully restored.

Read the full incident report →