Risotto Outage History

Risotto is up right now

Risotto had 9 outages in the last 2 years totaling 23h 0m of downtime — averaging 0.4 incidents per month.

There were 9 Risotto outages since November 18, 2025 totaling 23h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://risotto.statuspage.io

Minor July 28, 2026

Risotto Agent and Assistant Experiencing Failures

Detected by Pingoru
Jul 28, 2026, 03:19 PM UTC
Resolved
Jul 28, 2026, 03:43 PM UTC
Duration
24m
Affected: Agent
Timeline · 4 updates
  1. investigating Jul 28, 2026, 03:19 PM UTC

    We are investigating an issue affecting both the Agent and the Assistant. We will keep you updated of our progress.

  2. investigating Jul 28, 2026, 03:30 PM UTC

    We implemented a fix that should restore both the Agent and the Assistant to Operational. We are monitoring.

  3. monitoring Jul 28, 2026, 03:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 28, 2026, 03:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 26, 2026

Risotto Dashboard is not loading

Detected by Pingoru
May 26, 2026, 09:55 PM UTC
Resolved
May 26, 2026, 10:52 PM UTC
Duration
56m
Affected: Dashboard
Timeline · 3 updates
  1. monitoring May 26, 2026, 09:55 PM UTC

    We're aware that users are unable to access the dashboard and are actively investigating. This is affecting both new logins and active sessions. Next update in 45 minutes.

  2. monitoring May 26, 2026, 10:05 PM UTC

    Services are restored. Our team is continuing to monitor the event.

  3. resolved May 26, 2026, 10:52 PM UTC

    The dashboard access problem has been resolved. All services are operational, and no customer action is required.

Read the full incident report →

Minor May 14, 2026

Slack incident affecting Risotto

Detected by Pingoru
May 14, 2026, 02:56 PM UTC
Resolved
May 14, 2026, 03:54 PM UTC
Duration
57m
Affected: Agent
Timeline · 3 updates
  1. investigating May 14, 2026, 02:56 PM UTC

    The ongoing incident at slack https://slack-status.com/2026-05/fe557ca05fdb64fa is affecting Risotto as the Agent is not receiving all messages.

  2. investigating May 14, 2026, 03:53 PM UTC

    We are continuing to investigate this issue.

  3. resolved May 14, 2026, 03:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 8, 2026

Email ticketing delays in upstream mail providers

Detected by Pingoru
Apr 08, 2026, 10:09 PM UTC
Resolved
Apr 09, 2026, 04:49 AM UTC
Duration
6h 39m
Affected: Agent
Timeline · 2 updates
  1. monitoring Apr 08, 2026, 10:09 PM UTC

    We are investigating reports of delays in email forwarding for Google Workspace users. We've identified a potential issue between Google and our email provider, though no outage is publicly reported. Other email providers may also be affected. If you use one or more Email Request Sources with Risotto, we recommend checking email delivery logs in the system used for forwarding (such as Google Workspace) to confirm the status of any messages received but not successfully forwarded.

  2. resolved Apr 09, 2026, 04:49 AM UTC

    We believe the upstream issue was resolved.

Read the full incident report →

Minor February 19, 2026

Customers are unable to log into the Risotto Dashboard

Detected by Pingoru
Feb 19, 2026, 04:42 PM UTC
Resolved
Feb 19, 2026, 05:58 PM UTC
Duration
1h 16m
Affected: Dashboard
Timeline · 3 updates
  1. identified Feb 19, 2026, 04:42 PM UTC

    We have identified an issue with our auth provider that is resulting in increased latency while attempting to log in to the Risotto Dashboard. We're working to restore access quickly. Next update in 30 minutes.

  2. monitoring Feb 19, 2026, 05:10 PM UTC

    We are seeing some recovery and dashboard users are able to log in. We will continue to monitor and provide another update in 30 min.

  3. resolved Feb 19, 2026, 05:58 PM UTC

    The incident has been resolved and users should be able to log into the Risotto dashboard.

Read the full incident report →

Major January 21, 2026

Multiple services down

Detected by Pingoru
Jan 21, 2026, 09:42 PM UTC
Resolved
Jan 21, 2026, 10:57 PM UTC
Duration
1h 15m
Affected: DashboardAgent
Timeline · 4 updates
  1. investigating Jan 21, 2026, 09:42 PM UTC

    We are investigating an issue affecting both the Dashboard and the Agent. We will keep you updated of our progress.

  2. identified Jan 21, 2026, 09:46 PM UTC

    The issue was identified and we are working on a fix.

  3. monitoring Jan 21, 2026, 09:50 PM UTC

    We implemented a fix that should restore both the Dashboard and the Agent to Operational. We are monitoring.

  4. resolved Jan 21, 2026, 10:57 PM UTC

    All services are operational. The issue has been resolved and a long-term fix is in place. No customer action is required.

Read the full incident report →

Critical January 15, 2026

Agent is escalating immediately without providing any support

Detected by Pingoru
Jan 15, 2026, 05:07 PM UTC
Resolved
Jan 15, 2026, 05:15 PM UTC
Duration
8m
Affected: Agent
Timeline · 2 updates
  1. investigating Jan 15, 2026, 05:07 PM UTC

    We are currently investigating an issue reaching our LLM provider to support Agent functionality. Ticket management and Dashboard operations should continue to work, however automated responses are down.

  2. resolved Jan 15, 2026, 05:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 13, 2026

Risotto creating duplicate tickets for Slack requests

Detected by Pingoru
Jan 13, 2026, 07:43 PM UTC
Resolved
Jan 13, 2026, 09:01 PM UTC
Duration
1h 17m
Affected: Agent
Timeline · 4 updates
  1. identified Jan 13, 2026, 07:43 PM UTC

    An issue with how we process Slack messages has been identified and a fix is being implemented.

  2. identified Jan 13, 2026, 07:44 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Jan 13, 2026, 08:04 PM UTC

    We have deployed a fix for the issue and are actively monitoring the system to ensure everything is operating normally.

  4. resolved Jan 13, 2026, 09:01 PM UTC

    This incident has been resolved.

Read the full incident report →