Last checked
Project management for agile teams.
Experiencing an issue?

¿Jira no funciona?
Status unavailable
The current official status of Jira cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Jira in the last 24 hours. Last official check: .
Source: official status pageShare 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 |
|---|
Status verification pending
The latest official observation is not fresh enough to confirm current service health.
Official provider statusOfficial incident resolved
Issues accessing multiple Atlassian products in some regions — **SUMMARY** On August 27, 2026, between 03:51 and 04:35 UTC, Atlassian customers in the Western Europe and Southeast APAC regions were unable to reach Atlassian Cloud products, including Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search, and Talent. The event was triggered by a defective code change to the routing layer of one of our proxy fleets. This led to HTTP 404 errors being served to all customer traffic through these proxy fleets in Western Europe and Southeast APAC regions. The incident was detected within 1 minute by our automated monitoring systems, and mitigated by rolling back to the previous configuration release, which put the proxy fleet into a known good state. After the proxy fleet recovered, some Jira and Confluence customers (regardless of location) received HTTP 503 errors between 04:33 and 04:53 UTC as server fleets adjusted to the influx of traffic. **IMPACT** The overall impact was split into two discrete periods: - First, on 27 August 2026, between 03:51 and 04:35 UTC on Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search, and Talent. The incident caused service disruption to customer traffic originating from Western Europe and Southeast APAC regions, with HTTP 404 errors returned. There was no impact to customer API traffic, regardless of origin location. - Second, on 27 August 2026, between 04:33 and 04:53 UTC, some Jira and Confluence customers regardless of location received HTTP 503 errors after the HTTP 404 errors were solved: ~32% of requests in ap-southeast-2, ~4% of requests in eu-west-1, ~2.5% of requests in us-west-2 and ap-southeast-1, and <1% of requests in all remaining global regions. **ROOT CAUSE** The event was triggered by a code change to one of our proxy fleets. However, there was a defect in the code deployed which was not detected by manual and automated testing. This led to a misconfiguration of a tenant lookup functionality in the proxy tier, which led to traffic not having a valid network path, resulting in HTTP 404 errors being served to all customer traffic through these proxy fleets in Western Europe and Southeast APAC regions. After the proxy tier impact recovered, a second period of impact was caused to some Jira and Confluence customers. Due to the reduction of traffic served to Jira and Confluence by the proxy fleet, the Jira and Confluence service tiers had automatically scaled in the number of servers serving customer traffic. Once the proxy fleet functionality was restored, the surge of traffic overwhelmed the Jira service tier, which returned an elevated rate of HTTP 503s until it automatically scaled out again. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified because the change was related to a very specific kind of edge case that was not picked up by our automated continuous deployment suites and manual test scripts. We are prioritizing the following improvement actions to help avoid repeating this type of incident: - **Adding further deployment safeguards:** The deployment pipeline for the configuration of the impacted proxy tier was using a legacy system and did not have the appropriate slow regional rollout features configured correctly. We have already added the correct safeguards, and we are moving this to our company standard deployment pipeline that includes all of our safety controls enabled by default. We are also auditing all networking services to validate that they are all on the new standard pipeline deployment service. - **Enhancing service fleet scaling policies:** The auto scaling configuration for our Jira and Confluence service fleets was configured to scale in too aggressively. We are thoroughly reviewing and updating all of the complex Jira and Confluence auto scaling policies to ensure that this doesn’t occur again. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
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 |
|---|---|---|---|---|
| 1h 5m | Yes | Critical | ||
| 4h 26m | Yes | Minor | ||
| 2h 31m | Yes | Minor | ||
| 10h 50m | Yes | Major | ||
| 54m | Yes | Critical | ||
| 5h 51m | Yes | Major | ||
| 3h 53m | Yes | Minor | ||
| 1h 21m | Yes | Critical |
Comparte tus pensamientos sobre Jira
¡Sé el primero en comentar!
Uptimus supervisa Jira mediante su fuente oficial y normaliza incidencias, mantenimiento y componentes en un estado coherente.
Esta página incluye actualmente 11 componentes supervisados, 71 incidencias, 23 mantenimientos y 12 días de historial conocido.
Uptimus es un servicio independiente y no está afiliado con Jira. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.
Recibe alertas cuando Jira 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 71 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Disrupted JIRA availability in US East».
Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 11 componentes de Jira: Viewing content, Create and edit, Authentication and User Management, Search. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
Planned work published by the official provider.
The scheduled maintenance has been completed.
Started 18 mar 2025, 00:00 UTC · Resolved 1 jun 2025, 00:00 UTC
The scheduled maintenance has been completed.
Started 11 may 2024, 00:00 UTC · Resolved 23 may 2024, 16:01 UTC
The scheduled maintenance was completed in 47 minutes and backed up events were processed by 03:00 UTC.
Started 7 abr 2024, 02:00 UTC · Resolved 7 abr 2024, 03:00 UTC
The scheduled maintenance has been completed.
Started 14 mar 2022, 23:25 UTC · Resolved 15 mar 2022, 00:25 UTC
The scheduled maintenance has been completed.
Started 26 sept 2021, 22:00 UTC · Resolved 26 sept 2021, 23:00 UTC
The scheduled maintenance has been completed.
Started 22 ago 2021, 04:00 UTC · Resolved 22 ago 2021, 07:00 UTC
The scheduled maintenance has been completed.
Started 13 jun 2021, 20:00 UTC · Resolved 13 jun 2021, 20:30 UTC
The scheduled maintenance has been completed.
Started 28 feb 2021, 05:00 UTC · Resolved 28 feb 2021, 06:06 UTC
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 Jira | 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 Jira | 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