Last checked
Git security scanning and secrets detection for code security.
Experiencing an issue?

¿Gitguardian no funciona?
Degraded performance
Share your experience to help others stay informed.
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Loading reports… · Last 24 hours
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Official status checked
Gitguardian is experiencing issues
Official provider statusOfficial incident active
Delayed check runs — Status: 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. Affected components Secret Detection - Scan Check Run (Operational)
Official provider statusOfficial maintenance active
Maintenance: Database migration — Status: Complete Maintenance has completed Affected components Secrets Detection API (Under maintenance) Dashboard (Under maintenance) MCP Server (beta) (Under maintenance) Secret Detection - Scan Check Run (Under maintenance)
Official provider statusOfficial maintenance active
Scheduled Database Maintenance — Status: Resolved Maintenance is done. All services are back to normal operational mode. Affected components Webhooks (Operational) Secrets Detection API (Operational) Secret Detection - Scan Check Run (Operational) Dashboard (Operational) MCP Server (beta) (Operational)
Official provider status0 outage reports in the last 24 hours.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 641h 4mOngoing | Yes | Unknown | ||
| 0m | Yes | Major | ||
| 0m | Yes | Unknown | ||
| 0m | Yes | Unknown | ||
| 0m | Yes | Minor | ||
| 0m | Yes | Unknown | ||
| 0m | Yes | Major | ||
| 0m | Yes | Unknown |
Planned work published by the official provider.
Status: Complete Maintenance has completed Affected components Secrets Detection API (Under maintenance) Dashboard (Under maintenance) MCP Server (beta) (Under maintenance) Secret Detection - Scan Check Run (Under maintenance)
Started 28 jul 2026, 08:00 UTC · Ongoing
Status: Resolved Maintenance is done. All services are back to normal operational mode. Affected components Webhooks (Operational) Secrets Detection API (Operational) Secret Detection - Scan Check Run (Operational) Dashboard (Operational) MCP Server (beta) (Operational)
Started 4 jun 2026, 07:23 UTC · Ongoing
Status: Resolved Maintenance is over. Affected components Secret Detection - Scan Check Run (Operational) Dashboard (Operational) MCP Server (beta) (Operational) Webhooks (Operational) Secrets Detection API (Operational)
Comparte tus pensamientos sobre Gitguardian
¡Sé el primero en comentar!
Uptimus supervisa Gitguardian mediante su fuente oficial y normaliza incidencias, mantenimiento y componentes en un estado coherente.
Esta página incluye actualmente 18 componentes supervisados, 30 incidencias, 3 mantenimientos y 6 días de historial conocido.
Uptimus es un servicio independiente y no está afiliado con Gitguardian. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.
Recibe alertas cuando Gitguardian o uno de sus componentes supervisados informa de una interrupción grave o crítica. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas. El historial disponible contiene 30 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Delayed check runs».
Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 18 componentes de Gitguardian: Dashboard, Dashboard, Dashboard, Data Collectors. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
Las páginas públicas de Downdetector se centran en los reportes de usuarios. Uptimus combina esa actividad con incidentes oficiales, mantenimientos y salud de componentes cuando el proveedor los publica.
| Criterios de comparación | Uptimus | Downdetector |
|---|---|---|
| Reportes de la comunidad sobre Gitguardian |
The current official status of Gitguardian cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Gitguardian in the last 24 hours. Last official check: .
Started 22 may 2026, 10:21 UTC · Ongoing
| Incluido |
| Incluido |
| Línea base adaptativa que separa casos aislados de una interrupción amplia | Incluido | Incluido |
|---|
| Actividad de reportes de 24 horas y vista regional de interrupciones | Incluido | Incluido |
|---|
| Un espacio para sitios web, proveedores de estado, juegos de Steam y aplicaciones y juegos Android | Incluido | Producto separado |
|---|
| Alertas por correo, push y webhook desde el mismo espacio | Incluido | Producto separado |
|---|
| Actualizaciones oficiales de incidentes y cronología de Gitguardian | Incluido | Basado en reportes |
|---|
| Salud de componentes y mantenimientos mostrados por separado | Incluido | Limitado en páginas públicas |
|---|
Rate this service
No reviews yet