Is GitGuardian down?

Last checked 30d ago
Current status
GitGuardian is up

No incidents right now.

Official status page: https://gitguardian.statuspage.io · Polled every 5 minutes · 19 components tracked

GitGuardian is operational right now. Last checked 30d ago; the most recent incident resolved 57d ago.

Real-time GitGuardian status, recent outages, and incident history — pulled directly from GitGuardian's official status page at https://gitguardian.statuspage.io every 5 minutes. Pingoru tracks 19 GitGuardian services and has captured 4 incidents in the last 90 days (99.30% uptime). Get email, Slack, Discord, or webhook alerts the moment GitGuardian reports a new incident — free for 5 monitors, no credit card.

Users who monitor GitGuardian also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 Incapsula SentinelOne Keeper View all 6,000+ providers
GitGuardian uptime 99.30% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 20m
    Started Jun 04, 2026, 07:03 AM UTC · Resolved Jun 04, 2026, 07:23 AM UTC
    DashboardWebhooksSecrets Detection APISecret Detection - Scan Check RunMCP Server (beta)
    Timeline · 2 updates
    • investigating · Jun 04, 2026, 07:03 AM UTC

      We will be performing scheduled database maintenance on Jun 4, 2026 from 9:00 to 9:30 CET on EU platform tenant. During this window, you may experience: No access to the dashboard Delayed secret scanning results— scans will be queued and processed once maintenance is complete Delayed event processing— security events may take longer than usual to appear in your dashboard No data will be lost. All scans and events will be processed automatically after the maintenance window. We apologize for any inconvenience and appreciate your patience.

    • resolved · Jun 04, 2026, 07:23 AM UTC

      Maintenance is done. All services are back to normal operational mode.

    Latest: Maintenance is done. All services are back to normal operational mode.

  2. Resolved
    Started May 31, 2026, 10:00 PM UTC · Resolved May 31, 2026, 10:00 PM UTC
    Timeline · 1 update
    • resolved · Jun 01, 2026, 11:43 AM UTC

      What happened: From June 1 12:00am UTC to June 1 08:45am UTC, one of the component serving the public monitoring experienced some delays and a growing backlog of unprocessed messages. Impact: No data was lost. The only impact for customers could have been a delay between the detection of a secret and the moment the corresponding incident was created in the customer's dashboard. The problem is now fixed, the faulty component was able to re-start and to process the backlog of messages.

    Latest: What happened: From June 1 12:00am UTC to June 1 08:45am UTC, one of the component serving the public monitoring experienced some delays and a growing backlog of unprocessed messag…

  3. Resolved 1h 45m
    Started May 22, 2026, 08:36 AM UTC · Resolved May 22, 2026, 10:21 AM UTC
    DashboardWebhooksSecrets Detection APISecret Detection - Scan Check RunMCP Server (beta)
    Timeline · 3 updates
    • identified · May 22, 2026, 08:36 AM UTC

      We will be performing scheduled database maintenance on May 22, 2026 from 11:00 to 11:15 CET (09:00–09:15 UTC) on EU platform tenant. During this window, you may experience: No access to the dashboard Delayed secret scanning results— scans will be queued and processed once maintenance is complete Delayed event processing— security events may take longer than usual to appear in your dashboard No data will be lost. All scans and events will be processed automatically after the maintenance window. We apologize for any inconvenience and appreciate your patience.

    • identified · May 22, 2026, 10:21 AM UTC

      We are continuing to work on a fix for this issue.

    • resolved · May 22, 2026, 10:21 AM UTC

      Maintenance is over.

    Latest: Maintenance is over.

  4. Resolved 22h 51m
    Started May 21, 2026, 03:41 PM UTC · Resolved May 22, 2026, 02:33 PM UTC
    Secret Detection - Scan Check Run
    Timeline · 2 updates
    • monitoring · May 21, 2026, 03:41 PM UTC

      We are currently investigating an issue where some customers may experience intermittent spikes of slowness when processing check runs. Our team is actively monitoring the situation and working on a fix. We will provide updates as the situation progresses. We apologise for the inconvenience.

    • resolved · May 22, 2026, 02:33 PM UTC

      We deployed a fix today that addressed the check run issues. A brief database load increase was observed post-deployment with no impact on check run results. This incident is now resolved.

    Latest: We deployed a fix today that addressed the check run issues. A brief database load increase was observed post-deployment with no impact on check run results. This incident is now r…

Outage history

Past 90 days · 4 incidents View full outage history →