Last checked
Project, product, and portfolio management software for Jira.
Experiencing an issue?
¿Tempo 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
Tempo is experiencing issues
Official provider statusOfficial incident active
Forge Migration Update — The migration of Timesheets, Capacity Planner, and Financial Manager to [Forge](https://www.tempo.io/product-news/tempo-moves-to-forge) is underway, but the **automatic rollout did not start on March 31, 2026 as planned.** The automatic migration to Forge is tentatively scheduled to begin on June 15, 2026. You have the option to do either of the following: • **Perform a manual update** Review the expected changes (see links below) and assess any impacts to your workflows. If the impact is manageable, we recommend updating manually to control the timing of your instance’s migration. • **Wait for automatic update** The automatic rollout will occur gradually, so we are unable to confirm the exact date your instance will be updated. It will not be possible to schedule, delay, or opt out once started. After your instance is updated, you will receive an in-app notification confirming the change. You can also verify if your instance has migrated to Forge by **[checking the app versions](https://tempo-io.atlassian.net/wiki/spaces/DRAFTTIMESHEETS/pages/5679415354/Timesheets+Migration+to+Forge+FAQs#How-to-Check-Your-Current-Version).** **Breaking changes** Most of the migration is seamless, but a few things will change that may affect you, particularly around JQL filters: • JQL filter syntax – `issueInternal`, Account, Tempo Team, and custom field IDs • Tempo Panels in Jira issue view • Keyboard shortcuts • OAuth app URLs Please review the relevant documentation to prepare for changes that might affect you: • [Expected Changes in Timesheets on Forge](https://help.tempo.io/timesheets/latest/expected-changes-in-timesheets-on-forge) • [Expected Changes in Capacity Planner on Forge](https://help.tempo.io/planner/latest/expected-changes-in-capacity-planner-on-forge) • [Expected Changes in Financial Manager on Forge](https://help.tempo.io/financialmanager/latest/expected-changes-in-financial-manager-on-forge)
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 |
|---|---|---|---|---|
| 7h 50m | Yes | Critical | ||
| 2h 48m | Yes | Unknown | ||
| 2h 52m | Yes | Major | ||
| 7h 3m | Yes | Unknown | ||
| 19h 17m | Yes | Major | ||
| 7h 54m | Yes | Major | ||
| 3796h 35mOngoing | Yes | Unknown | ||
| 360h 36m | Yes | Minor |
Comparte tus pensamientos sobre Tempo
¡Sé el primero en comentar!
Uptimus monitorea Tempo mediante su fuente oficial y normaliza incidentes, mantenimiento y componentes en un estado consistente.
Esta página incluye actualmente 8 componentes monitoreados, 26 incidentes, 0 mantenimientos y 3 días de historial conocido.
Uptimus es un servicio independiente y no está afiliado con Tempo. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.
Recibe alertas cuando Tempo 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 26 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Elevated API Errors».
Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 8 componentes de Tempo: Jira, Tempo for Slack, Financial Manager, Tempo for Jira Cloud Help Center. 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 enfocan en 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 Tempo |
The current official status of Tempo cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Tempo in the last 24 hours. Last official check: .
| Incluido |
| Incluido |
| Línea base adaptativa que distingue casos aislados de una falla amplia | Incluido | Incluido |
|---|
| Actividad de reportes de 24 horas y vista regional de fallas | Incluido | Incluido |
|---|
| Un espacio para sitios web, proveedores de estado, juegos de Steam y apps 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 Tempo | 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