Gemfury incident

Investigating elevated repo errors

Resolved after 2 hours 35 minutes, affecting Repo endpoints, on May 20, 2026.

resolved May 20, 2026, 03:55 PM UTC

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

Started
May 20, 2026, 01:20 PM UTC
Resolved
May 20, 2026, 03:55 PM UTC
Duration
2h 35m
Detected by Pingoru
May 20, 2026, 01:20 PM UTC

Affected components

Repo endpoints

Update timeline

  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.

Your product runs on more than Gemfury

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →