Last checked
Project, product, and portfolio management software for Jira.
Experiencing an issue?
Tempo est-il en panne?
Status unavailable
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
Small green bars: normal status (illustrative). Taller bars: report activity. 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 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 | ||
| 3843h 4mOngoing | Yes | Unknown | ||
| 360h 36m | Yes | Minor |
Partagez vos réflexions sur Tempo
Soyez le premier à commenter!
Uptimus surveille Tempo via sa source officielle et normalise les incidents, maintenances et composants en un état cohérent.
Cette page comprend actuellement 8 composants surveillés, 26 incidents, 0 maintenances et 3 jours d'historique connu.
Uptimus est un service indépendant sans affiliation avec Tempo. Un état normal ne garantit pas que chaque utilisateur, appareil ou région soit épargné.
Recevez une alerte lorsque Tempo ou un composant surveillé signale une panne majeure ou une perturbation critique. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées. L’historique disponible contient 26 incidents indexés, donnant à chaque alerte un contexte au-delà de l’état actuel. Un incident récent indexé était « Elevated API Errors ».
Recevez des alertes sur les performances dégradées, les impacts partiels et les incidents qui ne constituent pas une panne complète. Uptimus suit actuellement 8 composants Tempo: Jira, Tempo for Slack, Financial Manager, Tempo for Jira Cloud Help Center. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.
Les pages publiques de Downdetector s’appuient surtout sur les signalements des utilisateurs. Uptimus les associe aux incidents officiels, maintenances et états des composants lorsque le fournisseur les publie.
| Critères de comparaison | Uptimus | Downdetector |
|---|---|---|
| Signalements communautaires concernant 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: .
| Inclus |
| Inclus |
| Référence adaptative distinguant les cas isolés d’une panne étendue | Inclus | Inclus |
|---|
| Activité des signalements sur 24 heures et vue régionale | Inclus | Inclus |
|---|
| Un espace pour les sites, pages de statut, jeux Steam et apps et jeux Android | Inclus | Produit séparé |
|---|
| Alertes e-mail, push et webhook depuis le même espace | Inclus | Produit séparé |
|---|
| Mises à jour officielles et chronologie du statut de Tempo | Inclus | Piloté par les signalements |
|---|
| État des composants et maintenances affichés séparément | Inclus | Limité sur les pages publiques |
|---|
Rate this service
No reviews yet