Tempo Outage History

Tempo is up right now

There were 3 Tempo outages since February 26, 2026 totaling 579h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tempo.io

Minor March 18, 2026

Data Processing Delays - Reporting Tools Affected

Detected by Pingoru
Mar 18, 2026, 02:24 PM UTC
Resolved
Mar 18, 2026, 02:24 PM UTC
Duration
—
Affected: Timesheets
Timeline · 3 updates
  1. investigating Mar 03, 2026, 01:48 PM UTC

    Status: Investigating We are currently experiencing delays in calendar event synchronization for users with Microsoft Outlook (O365) and Google Calendar integrations. Events may not appear in Tempo Timesheets as expected. Our engineering team is actively investigating the issue. We will provide further updates as we learn more. We apologize for the inconvenience. Affected components Timesheets (Degraded performance)

  2. investigating Mar 13, 2026, 08:50 PM UTC

    Status: Investigating We have temporarily remedied the degraded performance by scaling up the system. We continue to investigate the root cause. Affected components Timesheets (Degraded performance)

  3. resolved Mar 18, 2026, 02:24 PM UTC

    Status: Resolved We have identified and addressed the root cause of the delays. The issue is now resolved. Affected components Timesheets (Operational)

Read the full incident report →

Minor February 26, 2026

Elevated API Errors

Detected by Pingoru
Feb 26, 2026, 05:46 PM UTC
Resolved
Feb 26, 2026, 05:46 PM UTC
Duration
—
Affected: Capacity PlannerTimesheetsFinancial Manager
Timeline · 5 updates
  1. investigating Feb 26, 2026, 03:41 PM UTC

    Status: Investigating We're experiencing a high number of API errors in the EU cluster. We are actively investigating the cause. Affected components Financial Manager (Degraded performance) Capacity Planner (Degraded performance) Timesheets (Degraded performance)

  2. monitoring Feb 26, 2026, 03:54 PM UTC

    Status: Monitoring The issue is self-recovering. We are monitoring the issue. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

  3. monitoring Feb 26, 2026, 04:11 PM UTC

    Status: Monitoring Partial outages are still being observed in the cluster. Affected components Capacity Planner (Degraded performance) Timesheets (Degraded performance) Financial Manager (Degraded performance)

  4. monitoring Feb 26, 2026, 05:13 PM UTC

    Status: Monitoring The inbound requests have been processed stably. We continue to monitor the cluster. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

  5. resolved Feb 26, 2026, 05:46 PM UTC

    Status: Resolved The incident was resolved. Root cause analysis for a permanent solution is in progress. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

Read the full incident report →

Looking to track Tempo downtime and outages?

Pingoru polls Tempo's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Tempo reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Tempo alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Tempo for free

5 free monitors · No credit card required