Guru Outage History

Guru is up right now

Guru had 2 outages in the last 2 years totaling 12h 1m of downtime — averaging 0.1 incidents per month.

There were 2 Guru outages since August 28, 2024 totaling 12h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getguru.com

Notice July 24, 2026

Guru Service Disruption

Detected by Pingoru
Jul 24, 2026, 11:30 AM UTC
Resolved
Jul 24, 2026, 11:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Jul 24, 2026, 01:45 PM UTC

    Early morning on July 24th, 2026, our team became aware of a a third-party incident occurred and affecting customers in certain regions. During this time some customers may have experienced timeout and not able to login. The issue was resolved at 4:25 AM PT and Guru continues to monitor a recovery to normal conditions.

Read the full incident report →

Notice June 10, 2025

Degraded performance of Assist + Answers features

Detected by Pingoru
Jun 10, 2025, 01:09 PM UTC
Resolved
Jun 11, 2025, 01:11 AM UTC
Duration
12h 1m
Affected: Web AppExtensionSlack botAPI
Timeline · 5 updates
  1. investigating Jun 10, 2025, 01:09 PM UTC

    OpenAI, the provider we use to support our AI features (Assist + Answers) is currently experiencing issues that are affecting the performance of those features. All other Guru features are operational. We are monitoring the situation and will provide updates here.

  2. identified Jun 10, 2025, 03:17 PM UTC

    OpenAI is implementing a fix for this issue and stated that recovery could take several hours. We'll update here when their services are fully restored.

  3. monitoring Jun 10, 2025, 05:41 PM UTC

    The fix has been applied by OpenAI, and the results are being monitored.

  4. monitoring Jun 10, 2025, 10:51 PM UTC

    OpenAI has confirmed that this issue is resolved and their services are back up for the majority of users. All Guru AI features (Assist + Answers) are operational again.

  5. resolved Jun 11, 2025, 01:11 AM UTC

    This incident has been resolved.

Read the full incident report →