Last checked
Clio status
Legal practice management software for law firms and legal professionals.
Experiencing an issue?
¿Clio no funciona?
Degraded performance
Source: official status page
Having issues with Clio?
Share your experience to help others stay informed.
Clio service health graph
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Clio activity
Loading reports… · Last 24 hours
Download
- No problems detected
- Possible problems
- Problems detected
- Early warning
- Official incident
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.
View chart data
| Start | End | Reports | Status |
|---|
Latest activity
Last 24 hoursOfficial status checked
Clio is experiencing issues
Official provider statusOfficial incident active
API Key may potentially have been leaked — At 6:53 AM, we received an email notification from Stripe saying our API key may be compromised, and that an API request was made with our live mode Stripe API key by a secret scanner. Related API key identifier: req_7wlTi6PhftQAFm Currently investigating this in Cycode
Official provider status
Clio outage reports
0 outage reports in the last 24 hours.
Mapa de fallas de Clio
Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.Mapa de fallas de Clio
Loading report locations…
Clio status history
Official status observations, not measured service uptime.
Last 60 daysDaily history
Loading history…
- Operativo
- Problemas
- Falla
- Mantenimiento
- Sin datos
Clio components
| Component name | Status |
|---|
No components are available for this provider.
Clio incident history
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 |
|---|---|---|---|---|
| 1666h 46mOngoing | Yes | Unknown | ||
| 1h 26m | Yes | Minor | ||
| 129h 40m | Yes | Minor | ||
| 4h 35m | Yes | Minor | ||
| 80h 58m | Yes | Minor | ||
| 1h 48m | Yes | Minor | ||
| 32m | Yes | Minor | ||
| 39m | Yes | Minor |
Discusión de la comunidad
Comparte tus pensamientos sobre Clio
Sin comentarios aún
¡Sé el primero en comentar!
Acerca del monitoreo de Clio en Uptimus
Uptimus monitorea Clio mediante su fuente oficial y normaliza incidentes, mantenimiento y componentes en un estado consistente.
Esta página incluye actualmente 0 componentes monitoreados, 18 incidentes, 0 mantenimientos y 2 días de historial conocido.
Uptimus es un servicio independiente y no está afiliado con Clio. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.
Cómo monitorea Uptimus Clio
Recibe alertas cuando Clio 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 18 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «API Key may potentially have been leaked».
Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
