Augment AI Outage History

Started Oct 29, 2026, 03:17 PM UTC· resolved Oct 29, 2026, 04:12 PM UTC

1. investigating Oct 29, 2026, 03:17 PM UTC

   We are investigating elevated errors with authentication services at one of our US datacenters. Some API requests and Voice Agent sessions routed there may fail with 5xx errors, and some transcription callbacks sent from that datacenter may carry an invalid Dg-Token header.

2. resolved Oct 29, 2026, 04:12 PM UTC

   Between 15:17 and 15:45 UTC on October 29, an issue with authentication services at one of our US datacenters caused some API requests and Voice Agent sessions to fail with 5xx errors, and some transcription callbacks sent from that datacenter to carry an invalid Dg-Token header. A fix was deployed at 15:45 UTC and error rates returned to normal. This incident is resolved. All systems are operational.

Read the full incident report →

Started Oct 23, 2026, 04:07 PM UTC· resolved Oct 23, 2026, 06:55 PM UTC

1. monitoring Oct 23, 2026, 04:32 PM UTC

   We've addressed the issue that caused HubSpot to be unavailable to users in North America since 11:28 AM EDT (UTC -04:00). We're monitoring performance closely to ensure the tools recover properly. The information on this page reflects our understanding of the incident and impact at the time of the update.

2. resolved Oct 23, 2026, 06:55 PM UTC

   Between 11:28 AM EDT (UTC -04:00) and 2:43 PM EDT (UTC -04:00), many customers in North America experienced issues accessing HubSpot.com and various tools. This was caused by underlying network connectivity issues. As of 2:43 PM EDT (UTC -04:00), the networking issue has been addressed and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.

Read the full incident report →

Started Oct 22, 2026, 07:27 PM UTC· resolved Oct 22, 2026, 09:53 PM UTC

1. investigating Oct 22, 2026, 07:27 PM UTC

   We are currently investigating elevated latency and 5xx error rates returned from batch requests to our API platform.

2. resolved Oct 22, 2026, 09:53 PM UTC

   Between 19:27 and 21:53 UTC on October 22, some pre-recorded (batch) requests intermittently had elevated latency, and some timed out. This incident is resolved. All systems are operational.

Read the full incident report →

Started Oct 22, 2026, 04:00 PM UTC· resolved Oct 23, 2026, 11:00 AM UTC

1. investigating Oct 22, 2026, 04:00 PM UTC

   We are currently investigating elevated 5xx errors with authentication services at one of our datacenters.

2. investigating Oct 22, 2026, 05:14 PM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 22, 2026, 05:29 PM UTC

   We have identified the issue & are monitoring the solution.

4. resolved Oct 23, 2026, 11:00 AM UTC

   Between 16:00 and 17:09 UTC on October 22, some API requests returned 5xx errors because of an issue with authentication services at one of our datacenters. This incident is resolved. All systems are operational.

Read the full incident report →

Started Oct 22, 2026, 02:30 PM UTC· resolved Oct 22, 2026, 05:00 PM UTC

1. investigating Oct 22, 2026, 02:30 PM UTC

   Increased 504 errors from batch STT requests

2. resolved Oct 22, 2026, 05:00 PM UTC

   The incident has been resolved.

Read the full incident report →

Started Oct 15, 2026, 05:27 PM UTC· resolved Oct 15, 2026, 05:27 PM UTC

1. resolved Oct 15, 2026, 05:27 PM UTC

   Our team identified and resolved an issue affecting Email Suppressions. Between September 24 and September 29, 2026, customers may have experienced suppression list changes not being reflected, which could have impacted mail send and unsubscribe processing. A very small amount of mail sent during this period may not have been delivered, and some unsubscribe requests may not have been saved as expected. Affected unsubscribe records have been restored, and all impacted services are operating normally. No customer action is required.

Read the full incident report →

Started Oct 15, 2026, 07:56 AM UTC· resolved Oct 15, 2026, 07:58 AM UTC

1. investigating Oct 15, 2026, 07:56 AM UTC

   Decision Site is down at the moment. This incident was automatically created by Instatus monitoring.

2. resolved Oct 15, 2026, 07:58 AM UTC

   Decision Site is back up. This incident was automatically resolved by Instatus monitoring.

Read the full incident report →

Started Oct 15, 2026, 07:55 AM UTC· resolved Oct 15, 2026, 07:57 AM UTC

1. investigating Oct 15, 2026, 07:55 AM UTC

   Decision Site is down at the moment. This incident was automatically created by Instatus monitoring.

2. resolved Oct 15, 2026, 07:57 AM UTC

   Decision Site (az-prod-usc-01 origin) is back up. This incident was automatically resolved by Instatus monitoring.

Read the full incident report →

Started Oct 14, 2026, 12:37 AM UTC· resolved Oct 14, 2026, 06:46 PM UTC

1. investigating Oct 14, 2026, 12:37 AM UTC

   We are currently investigating the issue..

2. identified Oct 14, 2026, 04:51 PM UTC

   We've identified the issue and are working on a fix..

3. identified Oct 14, 2026, 05:16 PM UTC

   We've found the cause of the failures affecting automatically generated call plans, call outputs, follow-up emails, opportunity win plans, account plans, and briefing documents. Workflows built in the workflow builder aren't affected. A fix has been completed and is being deployed. Once it's live, we'll regenerate the outputs that failed and post another update..

4. monitoring Oct 14, 2026, 05:59 PM UTC

   We implemented a fix and are currently monitoring the result..

5. monitoring Oct 14, 2026, 06:22 PM UTC

   The issue has been resolved, and the backlog of intelligence output generations is being processed..

6. resolved Oct 14, 2026, 06:46 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Oct 08, 2026, 03:08 AM UTC· resolved Oct 08, 2026, 09:35 AM UTC

1. investigating Oct 08, 2026, 03:08 AM UTC

   We are investigating an issue affecting Twilio Verify deliveries to Australia, where an internal block is preventing verification codes from reaching end-users. Customers in this region may experience delivery failures during authentication flows. Our engineering team is actively working to clear the block and restore normal service. We will provide another update in 1 hour or as soon as more details become available..

2. investigating Oct 08, 2026, 04:04 AM UTC

   We are continuing to investigate an issue impacting Twilio Verify deliveries across multiple regions, where an internal block is preventing verification codes from reaching end-users. We are seeing recovery for Australia traffic, and our engineering team is actively working on mitigation for the remaining affected countries to restore full service. We will provide another update in 2 hour or as soon as more information becomes available..

3. identified Oct 08, 2026, 05:17 AM UTC

   We have identified the issue affecting Twilio Verify and Programmable SMS delivery across impacted regions. We are seeing recovery for Twilio Verify traffic, and our engineering team is actively working towards mitigation for Programmable SMS to restore full service. We will provide another update in 1 hour or as soon as more information becomes available..

4. identified Oct 08, 2026, 06:03 AM UTC

   We have identified the issue affecting Twilio Verify and Programmable SMS delivery across impacted regions. We are seeing recovery for Twilio Verify traffic, and our engineering team is actively working towards mitigation for Programmable SMS to restore full service. We will provide another update in 2 hour or as soon as more information becomes available..

5. identified Oct 08, 2026, 08:03 AM UTC

   We have identified the issue affecting Twilio Verify and Programmable SMS delivery across impacted regions. We are seeing recovery for Twilio Verify traffic, and our engineering team is actively working towards mitigation for Programmable SMS to restore full service. We will provide another update in 4 hours or as soon as more information becomes available..

6. monitoring Oct 08, 2026, 08:57 AM UTC

   We are seeing recovery for the intermittent delivery issues with Twilio Verify and Programmable SMS across the impacted regions. Our engineering team will continue to actively monitor the services to ensure a full recovery. We expect to provide another update in 30 minutes or as soon as more information becomes available..

7. resolved Oct 08, 2026, 09:35 AM UTC

   Twilio Verify and Programmable SMS delivery have fully recovered, and all impacted services are back to normal performance. This incident is now resolved. Thank you for your patience!.

Read the full incident report →

Started Oct 01, 2026, 06:45 AM UTC· resolved Oct 01, 2026, 07:00 AM UTC

1. investigating Oct 01, 2026, 06:45 AM UTC

   nextstep-sweep-az-prod-usc-01 did not report its scheduled check-in on time. This incident was automatically created by Instatus monitoring..

2. resolved Oct 01, 2026, 07:00 AM UTC

   nextstep-sweep-az-prod-usc-01 has resumed reporting on schedule. This incident was automatically resolved by Instatus monitoring..

Read the full incident report →

Started Sep 30, 2026, 07:29 PM UTC· resolved Sep 30, 2026, 07:39 PM UTC

1. investigating Sep 30, 2026, 07:29 PM UTC

   We are investigating elevated error rates on API requests to US endpoints. Some requests and connections are failing with HTTP 500 errors or timing out..

2. resolved Sep 30, 2026, 07:39 PM UTC

   Between 19:29 and 19:39 UTC, some API requests failed with HTTP 500 errors or timed out. This happened in two short bursts of about 1-2 minutes each, during a planned update to our authentication service. Services have recovered automatically and this issue is resolved..

Read the full incident report →

Started Sep 30, 2026, 05:05 PM UTC· resolved Sep 30, 2026, 08:35 PM UTC

1. identified Sep 30, 2026, 05:05 PM UTC

   We have identified that users are experiencing elevated latency for the impacted services. We are working on implementing a mitigation..

2. identified Sep 30, 2026, 05:13 PM UTC

   We have identified that users are experiencing elevated latency for the impacted services. We are working on implementing a mitigation..

3. identified Sep 30, 2026, 05:51 PM UTC

   We have implemented an initial mitigation and are seeing improvements in API latency. We are continuing to investigate the scope of the issue and apply additional mitigations as needed. Some requests to the Responses and Chat Completions APIs may still experience elevated latency or timeouts..

4. monitoring Sep 30, 2026, 06:21 PM UTC

   We have applied the mitigation and are monitoring the recovery..

5. resolved Sep 30, 2026, 08:35 PM UTC

   All impacted services have now fully recovered..

Read the full incident report →

Started Sep 30, 2026, 03:16 PM UTC· resolved Sep 30, 2026, 04:31 PM UTC

1. investigating Sep 30, 2026, 03:16 PM UTC

   We are experiencing delivery failures from Verify to China. Our engineers are working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available..

2. investigating Sep 30, 2026, 04:15 PM UTC

   We continue to experience delivery failures from Verify to China. Our engineers are working to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available..

3. resolved Sep 30, 2026, 04:31 PM UTC

   We have completed our investigation and determined that this event did not result in any customer impact. All systems are operating normally..

Read the full incident report →

Started Sep 29, 2026, 05:52 PM UTC· resolved Oct 06, 2026, 08:26 AM UTC

1. investigating Sep 29, 2026, 05:52 PM UTC

   We’re investigating elevated errors affecting ChatGPT, Codex, and the API. Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more..

2. investigating Sep 29, 2026, 06:24 PM UTC

   We’re investigating elevated errors affecting ChatGPT, Codex, and the API including the Agents API. Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more..

3. investigating Sep 29, 2026, 07:08 PM UTC

   We’re still investigating elevated errors affecting ChatGPT, Codex, and the API including the Agents API. Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more..

4. monitoring Sep 29, 2026, 07:39 PM UTC

   We have applied the mitigation and are monitoring the recovery..

5. monitoring Sep 29, 2026, 09:09 PM UTC

   We have applied the mitigation and are monitoring the recovery..

6. monitoring Sep 29, 2026, 10:03 PM UTC

   We have applied the mitigation and are monitoring the recovery..

7. monitoring Sep 29, 2026, 10:47 PM UTC

   We have applied the mitigation and are monitoring the recovery..

8. resolved Sep 29, 2026, 11:14 PM UTC

   The issue causing elevated errors across ChatGPT, Codex, and the API has been resolved, and all affected services have recovered. Thank you for your patience while we worked to restore service. The detailed Root Cause Analysis (RCA) will be published in the next 5 business days..

9. resolved Oct 06, 2026, 08:26 AM UTC

   All impacted services have now fully recovered..

Read the full incident report →

Started Sep 28, 2026, 05:40 PM UTC· resolved Sep 28, 2026, 05:53 PM UTC

1. investigating Sep 28, 2026, 05:40 PM UTC

   We are investigating elevated latency and 429 errors affecting some pre-recorded (batch) STT requests..

2. resolved Sep 28, 2026, 05:53 PM UTC

   An issue affecting some of our pre-recorded transcription servers slowed request processing. As requests took longer to complete, some customers saw elevated latency or received 429 errors. We identified and mitigated the issue, service has returned to normal..

Read the full incident report →

Started Sep 25, 2026, 11:51 PM UTC· resolved Sep 26, 2026, 01:16 AM UTC

1. investigating Sep 25, 2026, 11:51 PM UTC

   Our monitoring systems have detected a potential issue with the Twilio Verify 'Try it out' feature for trial accounts. Our engineers have been alerted and are investigating. We will provide an update when we have more details..

2. investigating Sep 26, 2026, 12:00 AM UTC

   We are investigating intermittent "Trial units expired" errors when creating verifications using the Twilio Verify 'Try it out' feature in trial accounts. We expect to provide another update in 1 hour or as soon as more information becomes available..

3. monitoring Sep 26, 2026, 12:46 AM UTC

   Twilio Verify 'Try it out' feature in trial accounts is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available..

4. monitoring Sep 26, 2026, 01:15 AM UTC

   This incident has been resolved. The Twilio Verify 'Try it out' feature for trial accounts is operating normally..

5. resolved Sep 26, 2026, 01:16 AM UTC

   This incident has been resolved. The Twilio Verify 'Try it out' feature for trial accounts is operating normally..

Read the full incident report →

Started Sep 21, 2026, 03:09 PM UTC· resolved Sep 21, 2026, 03:09 PM UTC

1. resolved Sep 21, 2026, 03:09 PM UTC

   Starting on 09/21/26 14:27 UTC Twilio customers experienced API errors affecting multiple services. Affected Components: Phone Numbers Account Management Authy > Verify Programmable Messaging > SMS Programmable Messaging > Messaging Services Programmable Messaging > MMS Programmable Messaging > Conversations Programmable Video > Group Rooms Serverless > Studio Serverless > Sync Flex > TaskRouter. The issue was resolved on 09/21/26 14:28 UTC.

Read the full incident report →

Started Sep 17, 2026, 08:20 PM UTC· resolved Sep 17, 2026, 09:50 PM UTC

1. identified Sep 17, 2026, 08:20 PM UTC

   We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation..

2. monitoring Sep 17, 2026, 09:20 PM UTC

   We have applied the mitigation and are monitoring the recovery..

3. resolved Sep 17, 2026, 09:50 PM UTC

   All impacted services have now fully recovered..

Read the full incident report →

Started Sep 11, 2026, 09:08 AM UTC· resolved Sep 11, 2026, 11:21 AM UTC

1. identified Sep 11, 2026, 09:08 AM UTC

   We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation..

2. monitoring Sep 11, 2026, 10:09 AM UTC

   We have brought additional capacity online and are seeing improvements for some GPT-5.6 Sol API traffic. We continue to mitigate elevated errors affecting Chat Completions and Responses and are monitoring recovery.

3. resolved Sep 11, 2026, 11:21 AM UTC

   All impacted services have now fully recovered..

Read the full incident report →

Started Sep 04, 2026, 11:40 AM UTC· resolved Sep 04, 2026, 06:56 PM UTC

1. investigating Sep 04, 2026, 11:40 AM UTC

   Starting around 3:30 PST on September the 4th, our engineers began investigating an issue with all emails being delivered to Microsoft. Users may experience different 5XX errors such as: Email was deferred due to the following reason(s): [IPs were throttled by recipient server: Mail send is affected only when sending to Microsoft supported services We will provide another update in an hour or as soon as more information becomes available..

2. identified Sep 04, 2026, 12:59 PM UTC

   Our engineers have identified the cause of the incident to be a change in the delivery policies with Microsoft as it has been acknowledged on their status post here: https://x.com/MSFT365Status. We encourage the customers to reach out to them directly for more information and updates including the affected IP and the exact message received. Errors such as "IPs throttled by recipient server" is a preemptive deferral in response to the "Server too busy" error, so we suggest that all errors should be read as literal and reach out Microsoft if you need more details on this: https://olcsupport.office.com/, and for Office 365 Anti-Spam IP delisting portal here: https://sender.office.com/ and their address for delisting is [email protected]. We will provide another update in 2 hours or as soon as more information becomes available..

3. monitoring Sep 04, 2026, 01:21 PM UTC

   We are seeing a recovery in our services for customer sending to Microsoft and MS 365 supported recipients, and we'll continue to monitor. Microsoft has acknowledged this issue here: https://x.com/MSFT365Status and we kindly ask our customers to reach out to them for more updates We'll provide more updates in 2 hours or as soon as they become available.

4. monitoring Sep 04, 2026, 03:21 PM UTC

   We are continuing to seeing a recovery in our services for customer sending to Microsoft and MS 365 supported recipients, and we'll continue to monitor. Microsoft has acknowledged this issue here: https://x.com/MSFT365Status and we kindly ask our customers to reach out to them for more updates We'll provide more updates in 2 hours or as soon as they become available.

5. monitoring Sep 04, 2026, 05:53 PM UTC

   We are continuing to seeing a recovery in our services for customer sending to Microsoft and MS 365 supported recipients, and we'll continue to monitor. Microsoft has acknowledged this issue here: https://x.com/MSFT365Status and we kindly ask our customers to reach out to them for more updates We'll provide more updates in 3 hours or as soon as they become available.

6. resolved Sep 04, 2026, 06:56 PM UTC

   Our engineers have monitored the issue and confirmed the issue with email deliveries to Microsoft has recovered to normal levels. All services are now operating normally at this time..

Read the full incident report →

Started Aug 04, 2026, 02:30 PM UTC· resolved Aug 04, 2026, 06:10 PM UTC

1. investigating Aug 04, 2026, 02:30 PM UTC

   We are currently investigating an issue where batch and streaming STT requests have degraded performance..

2. monitoring Aug 04, 2026, 03:21 PM UTC

   An ISP network failure resulted in poor performance along one network path, resulting in degraded performance that primarily affected STT traffic. All network traffic is now routed through a high quality network path and services have recovered. We are actively monitoring..

3. resolved Aug 04, 2026, 06:10 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Jul 29, 2026, 12:55 AM UTC· resolved Jul 29, 2026, 02:20 AM UTC

1. investigating Jul 29, 2026, 12:55 AM UTC

   We are investigating the issue for the listed services..

2. monitoring Jul 29, 2026, 01:39 AM UTC

   We have applied the mitigation and are monitoring the recovery..

3. resolved Jul 29, 2026, 02:20 AM UTC

   All impacted services have now fully recovered..

Read the full incident report →

Started Jul 28, 2026, 02:00 PM UTC· resolved Jul 29, 2026, 01:08 PM UTC

1. investigating Jul 28, 2026, 02:00 PM UTC

   We are currently investigating an issue where some batch requests are returning 400 errors due to remote content download errors. Retrying the request one or more times often succeeds..

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

   We are continuing to investigate this issue..

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

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

4. monitoring Jul 28, 2026, 03:58 PM UTC

   We are continuing to monitor for any further issues..

5. investigating Jul 28, 2026, 04:03 PM UTC

   We are continuing to investigate an issue. STT batch requests may have returned 5xx errors, and some STT websockets may have experienced high latency, starting at 16:03 UTC..

6. monitoring Jul 28, 2026, 04:34 PM UTC

   A fix has been implemented and traffic has returned to normal. We are monitoring the results..

7. resolved Jul 29, 2026, 01:08 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Jul 27, 2026, 03:30 PM UTC· resolved Jul 27, 2026, 05:30 PM UTC

1. investigating Jul 27, 2026, 03:30 PM UTC

   We are investigating the issue for the listed services..

2. resolved Jul 27, 2026, 05:30 PM UTC

   All impacted services have now fully recovered..

Read the full incident report →