GitGuardian Services Outage History

31 incidents recorded over the last 365 days, 29 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live GitGuardian Services status100.00% uptime history

Every Recorded GitGuardian Services Incident

GitGuardian Services incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 12, 2026Major upgrade of a component for US platformWe will be upgrading a backend component on the US platform. No downtime is expected, the platform will continue to work normally during the maintenance window.2h 30mScheduled
Nov 10, 2026Major upgrade of a component for EU platformWe will be upgrading a backend component on the EU platform. No downtime is expected, the platform will continue to work normally during the maintenance window.2h 30mScheduled
Oct 16, 2026Transient Email sending errorsResolution has been validated.2h 55mResolved
Oct 7, 2026Delays in check-runs and real-time handlingSystem is back to normal operations.14h 27mResolved
Aug 18, 2026Delayed check runsResolved. Following database query optimizations and reduced load from noisy background jobs, no further performance degradation has been observed. Metrics have been stable since deployment of the fixes.23 minResolved
Aug 11, 2026Delayed check runsThis incident is now resolved. Following fixes deployed by our team, we have not observed further performance degradation, and metrics have been stable since.68h 7mResolved
Jul 16, 2026Degraded public ingestion due to GitHub API outageGitHub has restored their API, and our public ingestion pipeline has fully recovered. Real-time event ingestion and commit retrieval are operating normally again. This incident was caused by an upstream GitHub API…57 minResolved
Jul 16, 2026 Check runs slownessThe fix has successfully been deployed and the situation should be back to normal. Sorry for the inconvenience.1h 4mResolved
Jun 9, 2026Data collector issue on Public MonitoringDue to a deployment incident, Public Monitoring's Data collector was not operational this morning between 8:00 AM UTC and 8:12 AM UTC.-2631324 minResolved
Jun 9, 2026Public Monitoring - Auth0 is unavailableThis incident has been resolved by Auth0 at 23:53 UTC yesterday. More infos here https://status.auth0.com/incidents/zvjzyc7912g5?u=v0zzz6jxvbv7-2700393 minResolved
Jun 9, 2026Internal Monitoring - Dashboard issueThis incident has been resolved.-2759012 minResolved
Jun 9, 2026Ongoing incident due to hosting issue since 7:20 UTC approximativelyOVH has resolved the routing issue. No data was lost, secret detection worked as usual. Only the "Explore" feature was unavailable.-2448291 minResolved
Jun 9, 2026Internal Repositories Monitoring - API Latency due to database maintenanceDear customers, At 14:30 UTC, GitGuardian Internal Monitoring's API suffered from increased latency. The API response time was fully back to normal at 15:00 UTC and the service remained available all the time. We…-2459454 minResolved
Jun 9, 2026GitGuardian Internal Monitoring application stuck in Maintenance mode at 14:29 UTCMaintenance mode was removed and dashboard & workers were restored at 14:56 UTC. No incoming events were lost. A bug in the maintenance script maintained a lock on the release process. We had to manually remove the…-2571864 minResolved
Jun 9, 2026Drop of commit coverage on Public Monitoring at 7:28 UTCThis incident has been resolved. All the GitHub commits, except those that may have been deleted by their authors, have been recovered. Incident's impact has been lowered to "Major".-2621049 minResolved
Jun 9, 2026GitGuardian Internal Monitoring upgrade in progress is taking longer than expectedThe release process is finished.-2396382 minResolved
Jun 9, 2026Services down due to AWS issuesOur services were unavailable from 16h09 to 17h43 CET. The situation is now resolved.-2356961 minResolved
Jun 9, 2026GitGuardian Internal Monitoring is not accessibleThis incident has been resolved.-2357444 minResolved
Jun 9, 2026Public GitHub monitoring is not working because GitHub API is downGitHub API is fully functional. Public GitHub data collection is up again.-2382671 minResolved
Jun 9, 2026Incident during Scheduled MaintenanceThis incident has been resolved.-2309968 minResolved
Jun 9, 2026GPM: Issues with the Search featureCommits and patches are now indexed in real-time again.-2335797 minResolved
Jun 9, 2026Errors on some of our API EndpointsThe incident has been resolved.-2167188 minResolved
Jun 9, 2026Important Delay in processing eventThis incident has been resolved.-1914954 minResolved
Jun 9, 2026Data Processing DelaysFrom Friday 9th Sept 6:30pm UTC to Monday 12th Sept 7:30 UTC, data collectors services were partially down due to an internal error. Github events have been correctly gathered into GitGuardian platform but processing…-1971174 minResolved
Jun 9, 2026Delay in events/check runs evaluationThis incident has been resolved.-1984304 minResolved
Jun 9, 2026GitGuardian Internal Monitoring - Database OutageThe incident has been resolved at 9h10 CEST.-2098230 minResolved
Jun 9, 2026GitGuardian Internal Monitoring - DNS outageFollowing a DNS misconfiguration, GitGuardian Internal Monitoring platform was unavailable for about 20 minutes. Impact: No realtime scan (webhook): - GitHub events from recent GHE instances and Github.com were…-1850574 minResolved
Jun 9, 2026Email notifications sent for already existing incidentsThis incident has been resolved.-1904964 minResolved
Jun 9, 2026Network issues on Internal Repositories Monitoring SAASWe have identified a Network issue on Internal Repositories Monitoring that impacted Hook, Dashboard and API.-1822974 minResolved
Jun 9, 2026GIM: Network issue following a network component upgradeFollowing a upgrade operation of a network component, GIM endpoints have been unavailable most of the time during this incident between 09:48 and 10:24 UTC. Fix has been deployed, situation is still under monitoring.-1722516 minResolved
Jun 9, 2026Application Malfunction due to new deploymentDuring deployment of GIM new version, The app was malfunctioning for a few minutes. The events that failed to evaluate during the incidents have been processed again.-1755324 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next GitGuardian Services incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This GitGuardian Services Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before GitGuardian Services acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single GitGuardian Services outage in this window ran 2d 20h, against a mean recovery of 11h 37m. If you depend on GitGuardian Services in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.