New Multi-region uptime checks and custom-domain status pages

GitGuardian Outage History

Daily provider-status observations and published incident history for GitGuardian.

Operational

GitGuardian is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow GitGuardian for future changes.

96.5% of 57 verified observed days had no reported provider issue

90-Day Trend

Jul 23Oct 20

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 30 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

9 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

August 2026
Delayed check runs
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We've identified renewed performance degradation affecting check run and realtime processing, with some customers experiencing delays of up to approximately 30 minutes. We've identified contributing factors related to database load and have deployed mitigations to reduce impact. We're continuing to investigate further improvements and will share updates as we have more information.
Delayed check runs
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Service has returned to normal levels and we're no longer seeing degradation. Our engineering team has applied mitigations and continues to investigate the underlying cause to prevent recurrence. We're closely monitoring the situation and will update this page as needed.
investigating
We are continuing to investigate delays affecting check runs and GitHub Actions checks for customers. The root cause hasn't been confirmed yet, but we've applied mitigations to reduce load on our systems. We're closely monitoring the situation and will share another update as soon as we have more information.
investigating
We are aware of delays affecting check runs and GitHub Actions checks for some customers. Our team is actively working on it. We'll post another update as soon as we have more information.
July 2026
Degraded public ingestion due to GitHub API outage
major Source not attested
Last archived state: resolved
View archived record details
monitoring
GitHub has begun restoring their API, and our public ingestion pipeline is recovering. Real-time event ingestion and commit retrieval are resuming. We are continuing to monitor the situation to confirm full recovery and ensure the pipeline is processing normally. We will provide a final update once the incident is fully resolved.
identified
We are currently experiencing degraded performance in our public ingestion pipeline. This is caused by an ongoing outage of the GitHub API, which GitHub has acknowledged on their own status page. Our team is actively monitoring the situation. Because the root cause is on GitHub's side, resolution depends on GitHub restoring their API. Our pipeline is designed to resume automatically once GitHub recovers, and we will provide further updates as the situation develops.
Check runs slowness
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We are currently investigating an issue where some customers may experience intermittent spikes of slowness when processing check runs.Our team deployed a fix and is actively monitoring the situation. We will provide updates as the situation progresses.We apologise for the inconvenience.
June 2026
Scheduled Database Maintenance
minor Source not attested
Last archived state: resolved
View archived record details
investigating
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 ...
May 2026
Scheduled Database Maintenance – Temporary Service Disruption
minor Source not attested
Last archived state: resolved
View archived record details
identified
We will be performing scheduled database maintenance on May 22, 2026 from 12:00 to 12:15 CET (10:00–10: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 maintenanc...
Slowness on Check Runs
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
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.
March 2026
Delay in public scanning
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We identified delay in real-time scanning of public commits since 7:30 AM (UTC). We deployed a fix and the delay is decreasing. At most, the delay was of 1 hour and 45 minutes. No data has been lost.
MCP Server is not working
critical Source not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.