<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.augment.co,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.augment.co"/>
  <link rel="self" type="application/atom+xml" href="https://status.augment.co/history.atom"/>
  <title>Augment Status - Incident history</title>
  <updated>2026-09-04T12:59:09.000+00:00</updated>
  <author>
    <name>Augment</name>
  </author>
  
<entry>
  <id>tag:status.augment.co,2005:Incident/cmtmvyu2c2cif0rnpfk1u8jke</id>
  <published>2026-09-04T12:59:09.000+00:00</published>
  <updated>2026-09-04T17:53:40.986+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmtmvyu2c2cif0rnpfk1u8jke"/>
  <title>Multiple delivery failures when sending emails to Microsoft or MS based recipients</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 days and 21 hours</p>
    <p><strong>Affected Components:</strong> SendGrid (email delivery)</p>
    <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>17:53:40</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are continuing to seeing a recovery in our services for customer sending to Microsoft and MS 365 supported recipients, and we&#039;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&#039;ll provide more updates in 3 hours or as soon as they become available.</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>18:56:09</var> GMT+0</small><br /><strong>Resolved</strong> -
  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..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>11:40:07</var> GMT+0</small><br /><strong>Investigating</strong> -
  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..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>13:21:35</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are seeing a recovery in our services for customer sending to Microsoft and MS 365 supported recipients, and we&#039;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&#039;ll provide more updates in 2 hours or as soon as they become available.</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>12:59:09</var> GMT+0</small><br /><strong>Identified</strong> -
  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 &quot;IPs throttled by recipient server&quot; is a preemptive deferral in response to the &quot;Server too busy&quot; 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 delist@microsoft.com.

We will provide another update in 2 hours or as soon as more information becomes available..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>15:21:30</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are continuing to seeing a recovery in our services for customer sending to Microsoft and MS 365 supported recipients, and we&#039;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&#039;ll provide more updates in 2 hours or as soon as they become available.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9di16302x41bqv04pa0eyc</id>
  <published>2026-08-04T14:30:34.000+00:00</published>
  <updated>2026-08-04T14:30:34.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9di16302x41bqv04pa0eyc"/>
  <title>[Deepgram API] Elevated Batch and Streaming STT Error Rates</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 days, 3 hours and 47 minutes</p>
    <p><strong>Affected Components:</strong> Deepgram (transcription)</p>
    <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>14:30:34</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an issue where batch and streaming STT requests have degraded performance..</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>15:21:42</var> GMT+0</small><br /><strong>Monitoring</strong> -
  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..</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>18:10:21</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Maintenance/cmt9djp4q030o0sqv746fjuvv</id>
  <published>2026-07-29T16:00:00.000+00:00</published>
  <updated>2026-07-29T16:00:07.681+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/maintenance/cmt9djp4q030o0sqv746fjuvv"/>
  <title>SendGrid Status Page Migration to Twilio Status Page — July 29, 2026</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    
    <p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>16:00:07</var> GMT+0</small><br /><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>12:10:20</var> GMT+0</small><br /><strong>Scheduled</strong> -
  On July 29, 2026 at 9:00 AM PT (originally planned for July 22), SendGrid incident and maintenance notifications will move to the Twilio Status Page: https://status.twilio.com.

Your existing SendGrid Status Page subscription will be migrated. Depending on how you currently receive notifications, you may need to confirm your subscription to continue receiving updates.

What to expect:

EMAIL SUBSCRIBERS: You should have received a confirmation email from status-help@statuspage.twilio.com on July 13 or 14. You must confirm your subscription via the email to continue receiving updates.

SMS SUBSCRIBERS: You should have received a confirmation email from status-help@statuspage.twilio.com on July 13 or 14. You must confirm your subscription via the message to continue receiving updates.

WEBHOOK SUBSCRIBERS: No action is required. Your webhook subscription will be migrated automatically and will continue to receive notifications without interruption.

Post migration, you will continue to receive notifications for the SendGrid services you are currently subscribed to, delivered from the Twilio Status Page.
 
Thank you for your continued trust in Twilio and SendGrid..</p>
<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>15:00:22</var> GMT+0</small><br /><strong>Scheduled</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9dkyj802s710qvlqsk5w96</id>
  <published>2026-07-29T00:55:27.831+00:00</published>
  <updated>2026-07-29T00:55:27.831+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9dkyj802s710qvlqsk5w96"/>
  <title>Elevated error rates with the invalid_prompt error code</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 12 hours and 51 minutes</p>
    <p><strong>Affected Components:</strong> OpenAI (AI fallback)</p>
    <p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>00:55:27</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating the issue for the listed services..</p>
<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>01:39:33</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>02:20:19</var> GMT+0</small><br /><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9di16602x51bqv4vt1sdt5</id>
  <published>2026-07-28T14:00:48.000+00:00</published>
  <updated>2026-07-28T14:00:48.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9di16602x51bqv4vt1sdt5"/>
  <title>[Deepgram API] Elevated Batch Error Rates: 400 error code responses</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 26 days, 19 hours and 47 minutes</p>
    <p><strong>Affected Components:</strong> Deepgram (transcription)</p>
    <p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>14:00:48</var> GMT+0</small><br /><strong>Investigating</strong> -
  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..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>15:57:17</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are continuing to investigate this issue..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>15:57:50</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented and we are monitoring the results..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>15:58:34</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are continuing to monitor for any further issues..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>16:03:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  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..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>16:34:10</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented and traffic has returned to normal. We are monitoring the results..</p>
<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>13:08:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9dkyjk02s910qvk6orf5wa</id>
  <published>2026-07-27T18:06:39.536+00:00</published>
  <updated>2026-07-27T15:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9dkyjk02s910qvk6orf5wa"/>
  <title>We’re seeing elevated latency, timeouts, and interrupted streaming across gpt 5.1 mini model and gpt 4.1 mini</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 12 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> OpenAI (AI fallback)</p>
    <p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating the issue for the listed services..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9dkyjo02sb10qv0n6q4bug</id>
  <published>2026-07-25T11:35:24.966+00:00</published>
  <updated>2026-07-25T11:35:24.966+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9dkyjo02sb10qv0n6q4bug"/>
  <title>Elevated error rates</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours and 37 minutes</p>
    <p><strong>Affected Components:</strong> OpenAI (AI fallback)</p>
    <p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>11:35:24</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation..</p>
<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>11:46:39</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>11:57:02</var> GMT+0</small><br /><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9dkyjl02sa10qvqpjpvgxi</id>
  <published>2026-07-25T09:17:49.024+00:00</published>
  <updated>2026-07-25T09:17:49.024+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9dkyjl02sa10qvqpjpvgxi"/>
  <title>Elevated error rates</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 14 hours and 47 minutes</p>
    <p><strong>Affected Components:</strong> OpenAI (AI fallback)</p>
    <p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>09:17:49</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating the issue for the listed services..</p>
<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>10:02:52</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>11:08:36</var> GMT+0</small><br /><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9djp2t030i0sqv32ckuk26</id>
  <published>2026-07-24T12:06:36.807+00:00</published>
  <updated>2026-07-24T12:06:36.869+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9djp2t030i0sqv32ckuk26"/>
  <title>AWS us-west-2 DNS Health Checks Fired</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 days and 13 hours</p>
    
    <p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>12:06:36</var> GMT+0</small><br /><strong>Investigating</strong> -
  Starting around 4:09 am PST on Jul/24, our engineers began investigating an issue related to low success rates in the us-west-2 region. Customer shouldn&#039;t experience impact. This does not impact mail send. We will provide another update in an hour or as soon as more information becomes available..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>12:09:07</var> GMT+0</small><br /><strong>Monitoring</strong> -
  At 4:21 PST our engineers have isolated the degraded region and removed it from load balancing and are now mitigated and observing. We will provide another update in an hour or as soon as more information becomes available..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>19:31:37</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our engineers have monitored the fix and confirmed the issue has been resolved. All services are now operating normally at this time..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9djp37030m0sqvqka34zoa</id>
  <published>2026-07-24T01:40:20.655+00:00</published>
  <updated>2026-07-24T01:40:20.745+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9djp37030m0sqvqka34zoa"/>
  <title>Some shared IP customers getting &quot;no IPs are available for this account&quot; when sending emails</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 3 hours and 25 minutes</p>
    
    <p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>01:40:20</var> GMT+0</small><br /><strong>Investigating</strong> -
  Our engineers began investigating an issue with customers getting &quot;no IPs are available for this account&quot; when sending emails. Users may experience delays in email delivery.We will provide another update in 1 hour or as soon as more information becomes available..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>02:06:24</var> GMT+0</small><br /><strong>Identified</strong> -
  Our engineers have identified the issue and are working toward a fix. We will provide another update in an hour or as soon as more information becomes available..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>02:22:38</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our engineers have identified the problem and implemented a fix and are monitoring system performance. We will provide another update in an hour or as soon as more information becomes available..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>03:33:41</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our engineers are continuing to monitor the fix. Please note that email requests are now being delivered as expected for customers using shared IPs.We will provide another update in 4 hours or as soon as more information becomes available..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>04:07:46</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our engineers have monitored the fix and confirmed the issue with shared Ips has been resolved. All services are now operating normally at this time..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9dkyj502s610qvu3c0ejzj</id>
  <published>2026-07-23T15:36:02.973+00:00</published>
  <updated>2026-07-23T15:36:02.973+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9dkyj502s610qvu3c0ejzj"/>
  <title>Elevated Error Rates</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 days, 21 hours and 19 minutes</p>
    <p><strong>Affected Components:</strong> OpenAI (AI fallback)</p>
    <p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>15:36:02</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating the issue for the listed services..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>15:56:57</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>16:08:37</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>16:48:54</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation with the downstream infrastructure provider..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>17:36:32</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on implementing a mitigation..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>17:58:26</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on implementing a mitigation..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>18:50:34</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>19:37:21</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating the issue for the listed services..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>20:22:48</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>09:56:47</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating the issue for the listed services..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>10:06:05</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating the issue for the listed services..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>11:34:20</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>19:33:22</var> GMT+0</small><br /><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9djp2z030l0sqvd97nhbrq</id>
  <published>2026-06-24T18:05:02.771+00:00</published>
  <updated>2026-06-24T18:05:02.938+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9djp2z030l0sqvd97nhbrq"/>
  <title>EU Regionalized Email Links Down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 1 hour and 24 minutes</p>
    
    <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>18:05:02</var> GMT+0</small><br /><strong>Investigating</strong> -
  Starting around 9:40 AM PST on June 24th 2026, our engineers began investigating an issue with Click Tracked links from EU Regionalized configured senders not working. Users may experience recipients seeing a &#039;Your connection is not private&#039; when clicking links sent from EU regionalized configured accounts. This does not impact mail send. This does not impact accounts configured for Global sending. We will provide another update in 1 hour or as soon as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>18:10:51</var> GMT+0</small><br /><strong>Identified</strong> -
  Our engineers have identified the issue and are working toward a fix. We will provide another update in 1 hour or as soon as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>18:15:54</var> GMT+0</small><br /><strong>Identified</strong> -
  Our engineers have implemented a fix and are monitoring system performance. We will provide another update in 30 minutes or as soon as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>18:19:44</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our engineers have implemented a fix and are monitoring system performance. We will provide another update in 30 minutes or as soon as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>18:54:27</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our engineers have monitored the fix and confirmed the issue with Click Tracked links from EU Regionalized Senders has been resolved. All services are now operating normally at this time..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9dkyj302s510qvh6p5xqfk</id>
  <published>2026-06-24T05:59:33.348+00:00</published>
  <updated>2026-06-24T05:59:33.348+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9dkyj302s510qvh6p5xqfk"/>
  <title>gpt-4o-mini high error rate</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> OpenAI (AI fallback)</p>
    <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>05:59:33</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>06:07:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9di16802x61bqvh711b2ve</id>
  <published>2026-06-17T13:35:10.000+00:00</published>
  <updated>2026-06-17T13:35:10.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9di16802x61bqvh711b2ve"/>
  <title>400 errors with PreRecorded STT (&quot;REMOTE_CONTENT_ERROR&quot; / &quot;failed to return valid data&quot;) when passing a URL</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 days, 12 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> Deepgram (transcription)</p>
    <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>13:35:10</var> GMT+0</small><br /><strong>Identified</strong> -
  Between the hours of 13:35 UTC - 19:47 UTC we noticed an increase in 400 errors returned on PreRecorded STT requests where the payload was a URL. They were transient errors, retrying the request was the recommended course of action and would typically result in a successful transcription..</p>
<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>19:47:56</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue was resolved at 19:47 UTC..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9djp2t030j0sqv6vhiqydf</id>
  <published>2026-06-14T16:45:32.287+00:00</published>
  <updated>2026-06-14T16:45:32.410+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9djp2t030j0sqv6vhiqydf"/>
  <title>Email Sending Delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 14 hours and 5 minutes</p>
    
    <p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>16:45:32</var> GMT+0</small><br /><strong>Investigating</strong> -
  Starting around 12:00 AM PDT on June 14, 2026, our engineers began investigating an issue with our core API and platform services. Users may experience high latency, timeouts, and 5xx errors with sending email through the API and the UI. We will provide another update in 30 minutes or as soon as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>17:20:58</var> GMT+0</small><br /><strong>Investigating</strong> -
  Engineers are still investigating issues causing email sending delays. We will provide a status update in 30 minutes or as soon as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>17:34:05</var> GMT+0</small><br /><strong>Identified</strong> -
  Our engineers have identified the issue and are working toward a fix. Mitigation efforts are underway to resolve the intermittent errors and delays. We will provide another update in 30 minutes or as soon as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>18:11:07</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our engineers have implemented a fix and are monitoring system performance. We will continue to observe the platform for the next hour to ensure full stability, and will mark this incident as resolved if no further issues are seen. We will provide another update in 1 hour or as soon as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>19:23:38</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our engineers have monitored the fix and confirmed the issue with high latency and 5xx errors has been resolved. All services are now operating normally at this time..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9dkyj102s410qv56mymsp7</id>
  <published>2026-06-11T22:22:14.786+00:00</published>
  <updated>2026-06-11T22:22:14.786+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9dkyj102s410qv56mymsp7"/>
  <title>Elevated 431 Errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 1 hour and 42 minutes</p>
    <p><strong>Affected Components:</strong> OpenAI (AI fallback)</p>
    <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>22:22:14</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified that some users are experiencing elevated 431 errors for the impacted services.

We are working on implementing a mitigation..</p>
<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>22:59:24</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are continuing to investigate the issue regarding elevated 431 errors and are working on the mitigation..</p>
<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>23:25:36</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>00:47:57</var> GMT+0</small><br /><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9dkyja02s810qvwexqlmeu</id>
  <published>2026-05-28T05:27:00.000+00:00</published>
  <updated>2026-05-28T05:27:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9dkyja02s810qvwexqlmeu"/>
  <title>Subscription checkout failing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> OpenAI (AI fallback)</p>
    <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>05:27:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Resolved - Some users were unable to complete subscriptions on web and mobile. Affected users may have experienced the Subscribe button becoming unresponsive or encountered the error message submit_error_source:email during checkout..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9djp2n030h0sqvi561et0c</id>
  <published>2026-05-08T02:04:48.000+00:00</published>
  <updated>2026-05-08T02:04:48.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9djp2n030h0sqvi561et0c"/>
  <title>Mail Delay</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 days, 4 hours and 15 minutes</p>
    
    
        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9djp2z030k0sqvquyttv9c</id>
  <published>2026-04-15T16:00:17.886+00:00</published>
  <updated>2026-04-15T16:00:17.886+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9djp2z030k0sqvquyttv9c"/>
  <title>EU located subusers unable to send emails</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 19 hours and 45 minutes</p>
    
    
        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.augment.co,2005:Incident/cmt9djp3b030n0sqv4ozh2sy2</id>
  <published>2026-03-03T01:05:32.795+00:00</published>
  <updated>2026-03-03T01:05:32.795+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.augment.co/incident/cmt9djp3b030n0sqv4ozh2sy2"/>
  <title>Mail delivery delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    
        ]]>
  </content>
</entry>

</feed>