Last checked
Project, product, and portfolio management software for Jira.
Experiencing an issue?
Er Tempo nede?
Degraded performance
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: .
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 |
|---|
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 | ||
| 3812h 53mOngoing | Yes | Unknown | ||
| 360h 36m | Yes | Minor |
Del dine tanker om Tempo
Vær den første til at kommentere!
Uptimus overvåger Tempo via den officielle statuskilde og normaliserer hændelser, vedligeholdelse og komponenter til én ensartet status.
Siden indeholder nu 8 komponenter, 26 hændelser, 0 vedligeholdelser og 3 dages kendt historik.
Uptimus er en uafhængig tjeneste og er ikke tilknyttet Tempo. En sund status garanterer ikke, at alle brugere, enheder eller områder er upåvirkede.
Få besked, når Tempo eller en overvåget komponent melder et større eller kritisk nedbrud. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer. Den tilgængelige historik indeholder 26 hændelser og giver mere kontekst end den aktuelle status. En nylig registreret hændelse var “Elevated API Errors”.
Få besked om nedsat ydelse, delvis påvirkning og mindre hændelser uden et fuldt nedbrud. Uptimus følger nu 8 Tempo-komponenter: Jira, Tempo for Slack, Financial Manager, Tempo for Jira Cloud Help Center. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.
Downdetectors offentlige sider er primært baseret på brugerrapporter. Uptimus kombinerer dem med officielle hændelser, vedligeholdelse og komponentstatus, når udbyderen offentliggør dataene.
| Jämförelsekriterier | Uptimus | Downdetector |
|---|---|---|
| Rapporter fra fællesskabet om Tempo |
| Inkluderet |
| Adaptiv basislinje, der skelner enkelte rapporter fra større nedbrud | Inkluderet | Inkluderet |
|---|
| Rapportaktivitet over 24 timer og regionalt nedbrudskort | Inkluderet | Inkluderet |
|---|
| Ét arbejdsområde til websites, statusudbydere, Steam-spil og Android-apps og -spil | Inkluderet | Separat produkt |
|---|
| E-mail-, push- og webhookalarmer fra samme arbejdsområde | Inkluderet | Separat produkt |
|---|
| Officielle hændelsesopdateringer og statushistorik for Tempo | Inkluderet | Rapportbaseret |
|---|
| Komponentstatus og vedligeholdelse vises separat | Inkluderet | Begrænset på offentlige sider |
|---|
Rate this service
No reviews yet