Tempo logo

Is Tempo Down?

SaaSLive status, outages, and incident history

No. Tempo is up right now.

Every monitored Tempo system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · 60s while moving

Know the moment Tempo breaks

Tempo is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Tempo status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Tempo Component Status

The main Tempo systems on this page. All 8 are operational right now.

8operational
Adaptive Planner
Operational
Capacity Planner
Operational
Financial Manager
Operational

5 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Jira, Tempo for Jira Cloud Help Center, Tempo for Slack, Time Tracker, Timesheets.

See all of them free

Component statuses may change independently during partial outages.

Recent Tempo Outages & Incidents

Incident history from the official Tempo status page, including resolution updates.

Slow response times and elevated errorsResolved Sep 15, 2026 · 42h 30mResolved

The incident has been resolved. During the incident we had to block Jira Issue webhook processing, but any updates in Jira since September 16th at 8:30pm have been processed normally. --- [2026-09-16T20:28:31Z] (monitoring) We are currently monitoring to make sure the system is back to full health. Customers can expect some delay in processing Jira issue updates. --- [2026-09-16T11:36:21Z] (investigating) We are continuing to investigate latencies that are causing problems loading the web app. This ties into the incident from yesterday. There is some delay in processing events from Jira as well as a result of this. --- [2026-09-15T19:47:41Z] (monitoring) We've applied some fixes that have stabilised things, but we are still dealing with some delays in processing events from Jira. --- [2026-09-15T16:22:34Z] (investigating) We're experiencing an elevated level of request errors and slow response times. We are currently looking into the issue.

Tempo App UnavailabilityResolved Aug 27, 2026 · 103h 23mResolved

This incident has been resolved. The affected Tempo apps have been restored and are operating normally for impacted customers. A fix has been deployed to prevent recurrence. If you're still experiencing issues, please contact Tempo Support. --- [2026-08-28T00:31:25Z] (monitoring) A solution has been deployed. Access is being restored to affected customers. We are currently monitoring the rollout. --- [2026-08-27T11:10:14Z] (identified) The incident affected a subset of our customers running connect on forge, and legacy connect apps. We have identified the problem and are looking into a solution to restore access as soon as possible --- [2026-08-27T08:36:57Z] (investigating) We are currently experiencing an issue where Tempo is failing to load for a subset of customers in our US instance. Our development team is actively investigating the cause.

Degraded performanceResolved Aug 25, 2026 · 6h 43mResolved

This incident has been resolved. --- [2026-08-25T13:11:32Z] (monitoring) The issue was self-healed. However, we haven't identified the root cause yet. We are investigating and continue to monitor the issue. --- [2026-08-25T08:57:40Z] (investigating) Status: We are currently investigating issues. Impact: Some users may experience degraded performance.

Tempo Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Tempo incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 8 days with incidentsSep 25

Live Tempo Outage Reports

Problems reported by engineers using Tempo. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Tempo problems reported yet.

Something wrong with Tempo on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Tempo

Tempo publishes a public status page at status.tempo.io covering 8 components, including Jira, Tempo for Slack and Financial Manager. PulsAPI tracks Tempo outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Tempo uptime at 89.15%. Response times, incident history, and SLA tracking for Tempo are available on the PulsAPI dashboard.

Tempo Status FAQ

Is Tempo down right now?

The verdict at the top of this page comes from the latest poll of the official Tempo status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Tempo is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Tempo recovers.

How do I check Tempo uptime history?

PulsAPI tracks Tempo uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 89.15%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Tempo changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Tempo outages?

PulsAPI reads the official Tempo status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Tempo components?

Yes. PulsAPI monitors 8 individual Tempo components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Tempo goes down?

Yes. Create a free account and subscribe to Tempo: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Tempo to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Tempo problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Tempo?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Tempo plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Tempo with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services