GitGuardian incident

Unavailable public monitoring features

Minor Resolved View vendor source →
Started
Feb 11, 2026, 11:45 PM UTC
Resolved
Feb 11, 2026, 11:40 PM UTC
Duration
Detected by Pingoru
Feb 11, 2026, 11:45 PM UTC

Affected components

Dashboard

Update timeline

  1. identified Feb 11, 2026, 09:22 PM UTC

    Following an incident on our cloud provider, our explore feature is not available in public monitoring. We monitor the situation and take measures to reduce the impact.

  2. identified Feb 11, 2026, 09:56 PM UTC

    We are waiting for updates from our cloud provider on their status page: https://bare-metal-servers.status-ovhcloud.com/incidents/l18zzyfpnxq2

  3. monitoring Feb 11, 2026, 10:36 PM UTC

    Cloud provider incident is resolved. Our services are restarting and will then catch up with the real-time. Explore feature is available again but with a delay of 2 hours which should resolve in a few hours.

  4. resolved Feb 12, 2026, 07:47 AM UTC

    The incident has been fully mitigated. Root cause: hardware failure in our cloud provider's networking infrastructure. All services have been restored to normal operation.

Looking to track GitGuardian downtime and outages?

Pingoru polls GitGuardian's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when GitGuardian reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track GitGuardian alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring GitGuardian for free

5 free monitors · No credit card required