Amigo AI Outage History

Amigo AI is up right now

Pingoru has recorded 13 incidents for Amigo AI: 12 in the last 12 months and 1 in the last 90 days.

Source: status.amigo.ai

13incidents recorded
12last 12 months
1last 90 days
5 daystypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Amigo AI in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202620 of 720 (0%)
May 202600 of 744 (0%)
June 20262336 of 720 (47%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202611 of 546 (0%)

Incidents, newest first

Minor October 21, 2026 Scribe staging note-fetching delays 28m

Started Oct 21, 2026, 12:58 PM UTC· resolved Oct 21, 2026, 01:26 PM UTC

  1. investigating Oct 21, 2026, 12:58 PM UTC

    We are investigating reports of errors when starting Scribe recordings. Affected users may be unable to start a recording and may see a 503 error. Our team is investigating the scope and cause. We will provide an update as more information becomes available.

  2. investigating Oct 21, 2026, 01:04 PM UTC

    Our current investigation points to a slow Scribe endpoint in the staging environment. Production impact has not been confirmed. We are continuing to investigate the reported recording errors and will update this page when the scope and recovery are verified.

  3. resolved Oct 21, 2026, 01:26 PM UTC

    The Scribe note-fetching issue in the US staging environment was confirmed resolved at 09:20 EDT on 21 October 2026. The investigation identified a slow upstream carry-forward endpoint. Production was confirmed unaffected by this incident.

  4. resolved Oct 21, 2026, 01:29 PM UTC

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

Read the full incident report →

Minor June 11, 2026 Conversations Failing due to Upstream LLM Provider Intermittent Outages 24d 21h Conversations

Started Jun 11, 2026, 09:19 PM UTC· resolved Jul 06, 2026, 07:14 PM UTC

  1. investigating Jun 11, 2026, 09:19 PM UTC

    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. identified Jun 11, 2026, 10:31 PM UTC

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

  3. resolved Jul 06, 2026, 07:14 PM UTC

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

Read the full incident report →

Minor April 2, 2026 AI Providers are not responding to requests 19m

Started Apr 02, 2026, 09:59 PM UTC· resolved Apr 02, 2026, 10:19 PM UTC

  1. investigating Apr 02, 2026, 09:59 PM UTC

    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

    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

    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

    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 2h 52m Conversations

Started Mar 10, 2026, 05:17 PM UTC· resolved Mar 10, 2026, 08:10 PM UTC

  1. investigating Mar 10, 2026, 05:17 PM UTC

    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.

  2. investigating Mar 10, 2026, 05:17 PM UTC

    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.

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

    We are migrating affected customers to another LLM provider to remediate the issue.

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

    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.

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

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

Read the full incident report →

Minor January 27, 2026 Conversation availability for the Europe region is degraded 2h 6m Conversations

Started Jan 27, 2026, 03:55 PM UTC· resolved Jan 27, 2026, 06:01 PM UTC

  1. investigating Jan 27, 2026, 03:55 PM UTC

    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

    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.

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

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

Read the full incident report →

Minor January 22, 2026 LLM Output Degeneration 6d 5h Agents, Services, Conversations

Started Jan 22, 2026, 01:27 PM UTC· resolved Jan 28, 2026, 07:13 PM UTC

  1. investigating Jan 22, 2026, 01:27 PM UTC

    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 22, 2026, 04:53 PM UTC

    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.

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

    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.

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

    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.

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

    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.

Read the full incident report →

Critical November 15, 2025 Starting and interacting with text and voice conversations failing 13m

Started Nov 15, 2025, 09:48 PM UTC· resolved Nov 15, 2025, 10:01 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical October 20, 2025 Full API Product Outage Due to Cloud Provider Outage (US) 13h 4m

Started Oct 20, 2025, 01:16 PM UTC· resolved Oct 21, 2025, 02:21 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →