Amigo AI Outage History

Amigo AI is up right now

Amigo AI had 10 outages in the last 2 years totaling 22h 42m of downtime — averaging 0.4 incidents per month.

There were 10 Amigo AI outages since August 5, 2025 totaling 22h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.amigo.ai

Minor April 2, 2026

AI Providers are not responding to requests

Detected by Pingoru
Apr 02, 2026, 10:19 PM UTC
Resolved
Apr 02, 2026, 10:19 PM UTC
Duration
Timeline · 4 updates
  1. investigating Apr 02, 2026, 09:59 PM UTC

    Status: Investigating We’re aware of an issue that may be impacting our users and are investigating. Currently, no requests to our ai providers are going through.

  2. resolved Apr 02, 2026, 10:00 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are operating normally. Thank you for bearing with us.

  3. identified Apr 02, 2026, 10:06 PM UTC

    Status: Identified We’ve identified the cause of the issue and are actively working on a resolution. More updates will follow as progress is made.

  4. resolved Apr 02, 2026, 10:19 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are operating normally. Thank you for bearing with us.

Read the full incident report →

Minor March 10, 2026

Create Conversation and Interact endpoint requests are failing

Detected by Pingoru
Mar 10, 2026, 08:10 PM UTC
Resolved
Mar 10, 2026, 08:10 PM UTC
Duration
Affected: Conversations
Timeline · 4 updates
  1. investigating Mar 10, 2026, 05:17 PM UTC

    Status: Investigating We’re aware of an issue that may be impacting some customers when creating conversations and interacting with a conversation. We are currently investigating. We’ll provide an update as soon as we know more. Affected components Conversation (WebSockets) (Partial outage) Conversations (Partial outage)

  2. identified Mar 10, 2026, 05:39 PM UTC

    Status: Identified We are migrating affected customers to another LLM provider to remediate the issue. Affected components Conversations (Partial outage) Conversation (WebSockets) (Partial outage)

  3. monitoring Mar 10, 2026, 07:31 PM UTC

    Status: Monitoring Error rates have returned to nominal. We have also completed migration of all affected customer services to another LLM provider. We will continue monitoring for errors and provide an update in the next 30m. Affected components Conversations (Partial outage) Conversation (WebSockets) (Partial outage)

  4. resolved Mar 10, 2026, 08:10 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are operating normally. Thank you for bearing with us. Affected components Conversations (Operational) Conversation (WebSockets) (Operational)

Read the full incident report →

Minor January 28, 2026

LLM Output Degeneration

Detected by Pingoru
Jan 28, 2026, 07:13 PM UTC
Resolved
Jan 28, 2026, 07:13 PM UTC
Duration
Affected: AgentsServicesConversations
Timeline · 4 updates
  1. investigating Jan 22, 2026, 01:27 PM UTC

    Status: Investigating We’re aware of an issue that may be impacting some users and are currently investigating. We’ll provide an update as soon as we know more. Affected components Services (Full outage) Agents (Full outage) Conversations (Full outage) Conversation (WebSockets) (Full outage)

  2. monitoring Jan 22, 2026, 04:53 PM UTC

    Status: Monitoring Problem: LLM outputs are occasionally returned as garbled text. Impact: Garbled LLM outputs are affecting organizations in the us-east-1 region, occurring in about 0.1% of messages. Causes: A hardware issue in us-east-1 combined with an ASCII to unicode prompt change that shifted tokenization boundaries. Steps to resolve: We are deploying a fix and expect to confirm its effectiveness within about 30m. Affected components Services (Degraded performance) Agents (Degraded performance) Conversations (Degraded performance) Conversation (WebSockets) (Degraded performance)

  3. monitoring Jan 24, 2026, 03:53 AM UTC

    Status: Monitoring The mitigations that we deployed over the past day have resulted in significant reductions in the incidence of the garbled output across affected us-east-1 orgs. We have additionally rerouted the relevant traffic to another cloud provider region that we expect to completely resolve the issue whilst we work with our vendor to identify the root cause and resolution path. Affected components Conversation (WebSockets) (Degraded performance) Services (Degraded performance) Agents (Degraded performance) Conversations (Degraded performance)

  4. resolved Jan 28, 2026, 07:13 PM UTC

    Status: Resolved Migrations of the relevant prompts to GPT 5.1 have resolved the issue. We have observed no further instances of the issue over a 24h+ period. Thank you for your patience. Affected components Conversations (Operational) Conversation (WebSockets) (Operational) Services (Operational) Agents (Operational)

Read the full incident report →

Minor January 27, 2026

Conversation availability for the Europe region is degraded

Detected by Pingoru
Jan 27, 2026, 06:01 PM UTC
Resolved
Jan 27, 2026, 06:01 PM UTC
Duration
Affected: Conversations
Timeline · 3 updates
  1. investigating Jan 27, 2026, 03:55 PM UTC

    Status: Investigating We’re aware of an issue that may be impacting some users and are currently investigating. We’ll provide an update as soon as we know more.

  2. monitoring Jan 27, 2026, 05:00 PM UTC

    Status: Monitoring We have cut over to other regions and are observing significantly reduced error rates and latency is returning to normal. We will continue to monitor for the next hour and provide an update. Affected components Conversations (Degraded performance)

  3. resolved Jan 27, 2026, 06:01 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are operating normally. Thank you for bearing with us. Affected components Conversations (Operational)

Read the full incident report →