Last checked
Firebase status
Google's mobile web app development platform.
Experiencing an issue?
¿Firebase no funciona?
Degraded performance
The current official status of Firebase cannot be verified. The latest stored provider observation indicated degraded performance. 0 reports were recorded for Firebase in the last 24 hours. Last official check: .
Source: official status pageHaving issues with Firebase?
Share your experience to help others stay informed.
Firebase 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.
Firebase 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
Firebase is experiencing issues
Official provider statusOfficial incident active
Visible reduction in data within Performance Monitoring dashboards and BigQuery exports. — We are investigating a system issue. To protect platform stability, we have limited the volume of collected data. Expect a visible reduction in data within Performance Monitoring dashboards and BigQuery exports.
Official provider status
Firebase outage reports
0 outage reports in the last 24 hours.
Mapa de Interrupciones
Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.Mapa de Interrupciones
Loading report locations…
Firebase status history
Official status observations, not measured service uptime.
Last 60 daysDaily history
Loading history…
- Operativo
- Problemas
- Interrupción
- Mantenimiento
- Sin datos
Firebase components
Firebase 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 |
|---|---|---|---|---|
| 13h 32m | Yes | Minor | ||
| 13h 20m | Yes | Minor | ||
| 69h 51m | Yes | Minor | ||
| 24h 42m | Yes | Major | ||
| 61h 4m | Yes | Minor | ||
| 47h | Yes | Minor | ||
| 1656h 7mOngoing | Yes | Minor | ||
| 2h 30m | Yes | Major |
Discusión de la Comunidad
Comparte tus pensamientos sobre Firebase
Aún no hay comentarios
¡Sé el primero en comentar!
Acerca de la supervisión de Firebase en Uptimus
Uptimus supervisa Firebase mediante su fuente oficial y normaliza incidencias, mantenimiento y componentes en un estado coherente.
Esta página incluye actualmente 26 componentes supervisados, 61 incidencias, 0 mantenimientos y 18 días de historial conocido.
Uptimus es un servicio independiente y no está afiliado con Firebase. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.
Cómo supervisa Uptimus Firebase
Recibe alertas cuando Firebase 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 61 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Testing Service is currently experiencing an availability issue. This disruption is broadly affecting testing traffic.».
Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 26 componentes de Firebase: A/B Testing (Beta), AI Logic, App Check, App Distribution. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
