<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.saleseq.ai,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai"/>
  <link rel="self" type="application/atom+xml" href="https://status.saleseq.ai/history.atom"/>
  <title>SalesEQ Status - Incident history</title>
  <updated>2026-07-22T19:43:00.000+00:00</updated>
  <author>
    <name>SalesEQ</name>
  </author>
  
<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhswt04ig0zrui9gvtm4b</id>
  <published>2026-07-22T19:43:00.000+00:00</published>
  <updated>2026-07-22T19:51:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhswt04ig0zrui9gvtm4b"/>
  <title>Errors creating domains and API keys</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours</p>
    <p><strong>Affected Components:</strong> Resend → Email Sending → Single Email, Resend → General API, Resend → Email Events</p>
    <p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>19:51:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have resolved the underlying issue and service has been resumed..</p>
<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>19:43:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified an issue with creating API keys and domains and we are working on a fix now..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfjtop042v0klc4v1oud3k</id>
  <published>2026-07-22T06:27:16.027+00:00</published>
  <updated>2026-07-22T08:19:31.134+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfjtop042v0klc4v1oud3k"/>
  <title>Cloudflare Malicious Upload Detection Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 16 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> Cloudflare → Cloudflare Sites and Services → Firewall</p>
    <p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>08:19:31</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>06:27:16</var> GMT+0</small><br /><strong>Investigating</strong> -
  Cloudflare Malicious Upload Detection Issues

Cloudflare is investigating issues with elevated errors in Malicious Upload Detection service.

We are working to understand the full impact and mitigate this problem. More updates to follow shortly..</p>
<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>06:37:13</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified and a fix is being implemented..</p>
<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>07:09:34</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented and we are monitoring the results..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfilz404mw1blc6bs2lx3j</id>
  <published>2026-07-17T15:02:12.659+00:00</published>
  <updated>2026-07-17T15:02:12.729+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfilz404mw1blc6bs2lx3j"/>
  <title>POST requests not succeeding</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 7 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> Cloudflare → Cloudflare Sites and Services → CDN/Cache</p>
    <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>15:02:12</var> GMT+0</small><br /><strong>Investigating</strong> -
  Cloudflare is aware of and investigating an issue where some customers may be experiencing POST requests not reaching origin servers correctly. We are working to analyse and mitigate this problem. More updates to follow shortly..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>15:06:16</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are continuing to investigate this issue..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>15:50:28</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified and a fix is being implemented..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>16:30:40</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'> 17</var>, <var data-var='time'>16:45:25</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfho0j04t00rpi57m3j16s</id>
  <published>2026-07-17T14:12:58.000+00:00</published>
  <updated>2026-07-17T14:12:58.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfho0j04t00rpi57m3j16s"/>
  <title>Increased invocation failures for Hobby Team functions</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 18 hours and 55 minutes</p>
    <p><strong>Affected Components:</strong> Vercel → Functions</p>
    <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>14:12:58</var> GMT+0</small><br /><strong>Investigating</strong> -
  There are elevated rates of invocation failures for Hobby Team functions in new deployments. Existing deployments are unaffected. We are investigating. Mitigation is possible by rolling back to a previous deployment..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>14:19:52</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the source of errors and are implementing a fix..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>14:27:39</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have deployed a fix and are continuing to monitor. Function invocations for new Hobby Team deployments should no longer fail. If you are still experiencing function invocation errors, redeploy or rollback to a previous deployment..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>15:19:53</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

A subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfjpc304up0rpii387vl45</id>
  <published>2026-07-17T07:31:00.238+00:00</published>
  <updated>2026-07-17T07:31:00.327+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfjpc304up0rpii387vl45"/>
  <title>Network Performance Issues for AWS ap-northeast-1 region</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> Cloudflare → Cloudflare Sites and Services → Network</p>
    <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>07:31:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Cloudflare is investigating issues with Network Performance for customers using AWS ap-northeast-1 region. Customers may see increased latency and HTTP 5xx errors.

We are working to analyze and mitigate this problem. More updates to follow shortly..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>07:36:01</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified and a fix is being implemented..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>07:44:12</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'> 17</var>, <var data-var='time'>07:50:45</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfjpcb04ur0rpi0mryzsme</id>
  <published>2026-07-17T01:25:53.480+00:00</published>
  <updated>2026-07-17T01:25:53.546+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfjpcb04ur0rpi0mryzsme"/>
  <title>Increased HTTP 500 Errors in Querétaro, Mexico</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 17 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> Cloudflare → Cloudflare Sites and Services → Network</p>
    <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>01:25:53</var> GMT+0</small><br /><strong>Identified</strong> -
  Cloudflare is investigating an increased level of HTTP 500 errors in Querétaro, Mexico. 

We are working to analyse and mitigate this problem.  More updates to follow shortly..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>01:26:35</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'> 17</var>, <var data-var='time'>01:42:54</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhswr04if0zru735m0a74</id>
  <published>2026-07-16T11:45:00.000+00:00</published>
  <updated>2026-07-16T12:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhswr04if0zru735m0a74"/>
  <title>Elevated errors on the dashboard</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 21 hours</p>
    <p><strong>Affected Components:</strong> Resend → General API, Resend → Email Sending → Single Email, Resend → Email Events</p>
    <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have resolved the underlying issue and service has been resumed..</p>
<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>11:45:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified increased error rates on the dashboard correlated with an upstream provider incident. We&#039;re shipping improvements to contain the errors..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfjpc304uo0rpiojkkwvl4</id>
  <published>2026-07-15T11:00:03.000+00:00</published>
  <updated>2026-07-15T11:00:03.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfjpc304uo0rpiojkkwvl4"/>
  <title>Network Performance issues - Increased HTTP 502 Errors in HKG</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 days, 13 hours and 37 minutes</p>
    <p><strong>Affected Components:</strong> Cloudflare → Cloudflare Sites and Services → Network</p>
    <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>11:00:03</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Cloudflare is investigating an increased level of HTTP 502 errors originating from the Hong Kong datacenter. We are working to analyse and mitigate this problem. More updates to follow shortly..</p>
<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>20:25:40</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhswu04ih0zru8qlyqcnc</id>
  <published>2026-07-10T13:21:07.622+00:00</published>
  <updated>2026-07-10T13:21:07.622+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhswu04ih0zru8qlyqcnc"/>
  <title>Increased latency across API endpoints and email sending</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 5 hours and 27 minutes</p>
    <p><strong>Affected Components:</strong> Resend → General API, Resend → Email Sending → Single Email</p>
    <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>13:21:07</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;re noticing increased API latency across different endpoints, causing delays in email sending..</p>
<p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>13:53:56</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The deployment has been completed, and we&#039;re still monitoring. Latency has stabilized since 13:38 UTC..</p>
<p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>14:14:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have resolved the underlying issue and service has been resumed..</p>
<p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>13:31:11</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and are deploying a fix now. The team is monitoring. Latency has recovered, but we&#039;re keeping this incident open for the next few minutes to monitor downstream services..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfjpcb04uq0rpi9e4qio0u</id>
  <published>2026-07-08T01:56:02.055+00:00</published>
  <updated>2026-07-08T01:56:02.192+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfjpcb04uq0rpi9e4qio0u"/>
  <title>Network Performance Issues in London</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 12 hours and 3 minutes</p>
    <p><strong>Affected Components:</strong> Cloudflare → Cloudflare Sites and Services → Network</p>
    <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>01:56:02</var> GMT+0</small><br /><strong>Investigating</strong> -
  Cloudflare is investigating issues with Network Performance in London. Some customers may experience increased latency or timeouts for the uksouth Azure region.

We are working to analyze and mitigate this problem. More updates to follow shortly..</p>
<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>02:32:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>01:56:46</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented and we are monitoring the results..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhxjf04jc0zruyo09wgbw</id>
  <published>2026-07-03T10:17:49.500+00:00</published>
  <updated>2026-07-03T10:17:49.500+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhxjf04jc0zruyo09wgbw"/>
  <title>Email sending delay</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 15 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> Resend → Email Sending → Single Email</p>
    <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>10:17:49</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating increased latency in email sending. At this time, you may experience delays when sending emails via our SMTP service and API..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>11:21:06</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have resolved the underlying issue and services have been recovered..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhji804mk1blcir1n0bib</id>
  <published>2026-07-02T16:31:55.748+00:00</published>
  <updated>2026-07-02T16:39:55.625+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhji804mk1blcir1n0bib"/>
  <title>Degraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 hours and 38 minutes</p>
    <p><strong>Affected Components:</strong> Vercel → Functions, Vercel → CDN → IAD1 - Washington DC, USA</p>
    <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>16:39:55</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented and we are observing recovery across CDN, Dashboard, &amp; Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>16:33:07</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified and a fix is being implemented..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>16:46:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>16:31:55</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating an issue causing degraded performance across CDN, Dashboard, &amp; Functions in Washington, Cleveland (iad1, cle1). We&#039;ll provide additional updates as they become available..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhswr04id0zruc1zahidw</id>
  <published>2026-07-01T15:36:00.000+00:00</published>
  <updated>2026-07-01T15:43:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhswr04id0zruc1zahidw"/>
  <title>Elevated error rates across our APIs and SMTP services</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day</p>
    <p><strong>Affected Components:</strong> Resend → Email Sending → Single Email, Resend → General API, Resend → Email Events</p>
    <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>15:43:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Services are recovering to normal. Our team is actively monitoring to ensure no further issues are impacting the requests..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our team has mitigated the issue and this incident is fully resolved. All services are operational..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>15:36:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Our team has identified an issue causing elevated error rates across our APIs and SMTP services. The impact is currently affecting email sending requests, which may result in increased 500 errors for some customers.

We are actively working on mitigation and will provide further updates as we make progress..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfi7mb04mv0kpif7e16mgi</id>
  <published>2026-06-22T20:34:04.761+00:00</published>
  <updated>2026-06-22T20:34:04.761+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfi7mb04mv0kpif7e16mgi"/>
  <title>Delayed webhooks</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> Resend → Email Events</p>
    <p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>20:34:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating increased latency in email events. Emails are being sent normally without any delays, but their respective statuses are taking longer to appear in the dashboard or via webhooks.

Email sending is not affected..</p>
<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>20:38:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified that email events are being updated correctly in the dashboard, but webhook sending is delayed. The team is still investigating..</p>
<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>20:48:03</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and we are working on a fix now..</p>
<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>20:48:36</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Affected webhooks are now being sent. We expect the affected webhooks to be sent within the next 20 minutes.

No webhooks were lost..</p>
<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>20:57:22</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have resolved the underlying issue, and all the affected webhooks have been sent..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhpik04t20rpiw6nk9k73</id>
  <published>2026-06-19T17:54:16.000+00:00</published>
  <updated>2026-06-19T17:54:16.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhpik04t20rpiw6nk9k73"/>
  <title>Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Vercel → Functions</p>
    <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>17:54:16</var> GMT+0</small><br /><strong>Resolved</strong> -
  Between Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE.

As part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989

We have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the Node.js upgrade once the upstream issue is fixed..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhswj04ic0zruc1ob4fxx</id>
  <published>2026-06-17T16:19:00.000+00:00</published>
  <updated>2026-06-17T16:19:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhswj04ic0zruc1ob4fxx"/>
  <title>Automations not starting</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 12 hours</p>
    <p><strong>Affected Components:</strong> Resend → General API, Resend → Email Sending → Single Email, Resend → Email Events</p>
    <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>16:19:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an issue with automations not starting..</p>
<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>16:55:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have resolved the underlying issue and service has been resumed..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhswr04ie0zruq5s813i4</id>
  <published>2026-06-15T19:55:10.277+00:00</published>
  <updated>2026-06-15T20:40:47.349+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhswr04ie0zruq5s813i4"/>
  <title>Issues downloading attachments</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 7 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> Resend → General API</p>
    <p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>20:40:47</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The fix for downloading email attachments has been pushed and we are now monitoring the situation..</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>21:14:40</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have resolved the underlying issue and service has been resumed..</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>19:55:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating issues with downloading attachments where existing download URLs would incorrectly return a 403 response..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhpii04t10rpimbh900z7</id>
  <published>2026-06-08T18:57:47.000+00:00</published>
  <updated>2026-06-08T18:57:47.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhpii04t10rpimbh900z7"/>
  <title>Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 14 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> Vercel → Functions</p>
    <p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>18:57:47</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified and a fix is being implemented.

A small number of requests may have seen elevated error rates in function invocations during this period..</p>
<p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>19:04:25</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;re continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region.

If your project uses only the dub1 function region, you can switch to the nearest region, lhr1, and redeploy to mitigate the issue..</p>
<p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>19:36:38</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented and we are monitoring the results..</p>
<p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>19:36:44</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are continuing to monitor for any further issues..</p>
<p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>20:00:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhxiz04jb0zrupdetqn4t</id>
  <published>2026-06-03T15:45:19.032+00:00</published>
  <updated>2026-06-03T15:45:19.032+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhxiz04jb0zrupdetqn4t"/>
  <title>API quota reporting incorrect numbers</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 6 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> Resend → Email Sending → Single Email</p>
    <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>15:45:19</var> GMT+0</small><br /><strong>Identified</strong> -
  We are currently reverting a change that cause quotas to be calculated incorrectly..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>16:10:54</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The fix has been pushed and we are now monitoring the situation..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>16:15:21</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have resolved the underlying issue and service has been resumed..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhpiq04t40rpioz3u64x5</id>
  <published>2026-05-28T16:00:14.658+00:00</published>
  <updated>2026-05-28T16:00:14.804+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhpiq04t40rpioz3u64x5"/>
  <title>Elevated Function Invocation Errors in Stockholm region (ARN1)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 11 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> Vercel → Functions</p>
    <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>16:00:14</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;ve identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue..</p>
<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>16:18:09</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified and a fix is being implemented..</p>
<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>16:37:04</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented and we are monitoring the results..</p>
<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>16:59:49</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfht3y04ij0zruz7bqrrp9</id>
  <published>2026-05-26T15:29:00.000+00:00</published>
  <updated>2026-05-26T15:29:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfht3y04ij0zruz7bqrrp9"/>
  <title>Resend dashboard facing intermittent errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours</p>
    <p><strong>Affected Components:</strong> Resend → General API, Resend → Email Sending → Single Email, Resend → Email Events</p>
    <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>15:29:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating increased latency in Resend dashboard. At this time, you may experience delays and errors while trying to access our dashboard..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>15:36:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have resolved the underlying issue and service has been resumed..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Maintenance/cmryfi7nj04mx0kpi41p1zgeu</id>
  <published>2026-05-20T14:00:00.000+00:00</published>
  <updated>2026-05-20T15:13:56.672+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/maintenance/cmryfi7nj04mx0kpi41p1zgeu"/>
  <title>Email Events - Scheduled Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> Resend → Email Events</p>
    <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>15:13:56</var> GMT+0</small><br /><strong>Completed</strong> -
  We&#039;ve completed our Email Events maintenance, and they are now showing the up-to-date status..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>11:58:27</var> GMT+0</small><br /><strong>Scheduled</strong> -
  During the scheduled maintenance window, emails will continue to be sent. Their status will show as queued on the Dashboard and in the API. Email events will also experience delays on the Dashboard. There will be no impact on any other parts of the platform or dashboard except for the emails page..</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>14:05:31</var> GMT+0</small><br /><strong>Identified</strong> -
  We are starting our planned maintenance of Email Events. During this maintenance, emails may appear as Queued while they are actually being sent. After the maintenance, the Email Events will be updated..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhpil04t30rpiyov4rxj2</id>
  <published>2026-05-08T01:18:59.114+00:00</published>
  <updated>2026-05-08T01:18:59.254+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhpil04t30rpiyov4rxj2"/>
  <title>Elevated errors across multiple services in IAD1 (Washington, D.C., USA)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 days, 8 hours and 42 minutes</p>
    <p><strong>Affected Components:</strong> Vercel → Functions</p>
    <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>01:18:59</var> GMT+0</small><br /><strong>Identified</strong> -
  Some Vercel functions that run in the IAD1 region are experiencing elevated invocation failures. We are investigating the issue and will share more information as it becomes available..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>01:47:09</var> GMT+0</small><br /><strong>Identified</strong> -
  Traffic to the IAD1 region has been re-routed to nearby regions. Functions configured in IAD1 will be invoked in a different region if failover regions are configured, but if no other regions are configured, the function will still be invoked in IAD1..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>02:13:23</var> GMT+0</small><br /><strong>Identified</strong> -
  New messages to Vercel Workflows and Vercel Queues are being queued, but message processing is paused. Queued messages will be processed when service is restored..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>02:18:42</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this issue..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>02:33:12</var> GMT+0</small><br /><strong>Identified</strong> -
  New workflow runs and queue messages are being processed now. Processing the backlog of existing workflow runs and queued messages is still being investigated..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>04:54:34</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are monitoring the results. Backlogs for Workflows and Queues will be processed within the next few hours..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>06:39:41</var> GMT+0</small><br /><strong>Resolved</strong> -
  We&#039;ve deployed mitigations and all services are operating normally. Traffic may continue to reroute to nearby regions for the next few hours, but we will restore traffic gradually after verifying system availability in the IAD1 region..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhsxg04ii0zrub18akg2g</id>
  <published>2026-05-07T14:54:00.000+00:00</published>
  <updated>2026-05-08T17:47:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhsxg04ii0zrub18akg2g"/>
  <title>Inbound emails with incorrect &quot;To&quot; field when forwarded</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 days and 5 hours</p>
    <p><strong>Affected Components:</strong> Resend → General API, Resend → Email Sending → Single Email, Resend → Email Events</p>
    <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>17:47:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have resolved the underlying issue by reverting the unintended breaking change and service has been resumed..</p>
<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>14:54:00</var> GMT+0</small><br /><strong>Identified</strong> -
  A recent change to how Resend processes inbound emails affected customers who receive emails via server-side forwarding rules, where a mail server automatically redirects an email to a different address without rewriting its headers.

When an email is forwarded this way to a Resend inbound address, the to field in the inbound webhook payload began reflecting the original &quot;To&quot; header (e.g. support@yourcompany.com) rather than the address that actually received the delivery (e.g. your Resend inbound address).

Direct emails and client-side forwards were not affected..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfhpiq04t50rpi8vxvtfva</id>
  <published>2026-05-01T11:30:44.380+00:00</published>
  <updated>2026-05-01T11:30:44.444+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfhpiq04t50rpi8vxvtfva"/>
  <title>Elevated Functions Invocation Errors in ICN1 (Seoul, South Korea) Region</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Vercel → Functions</p>
    <p><small>May <var data-var='date'> 1</var>, <var data-var='time'>11:30:44</var> GMT+0</small><br /><strong>Resolved</strong> -
  Between May 1, 11:01 am – May 1, 11:09 am UTC, users may have seen increased function invocation errors for traffic originated near the ICN1 Vercel CDN region. Requests to static assets/cached content were unaffected this time. We have reverted the change that caused the issue to mitigate this..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.saleseq.ai,2005:Incident/cmryfi7mg04mw0kpi5xd1tfdi</id>
  <published>2026-04-28T19:17:04.359+00:00</published>
  <updated>2026-04-28T19:17:04.359+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.saleseq.ai/incident/cmryfi7mg04mw0kpi5xd1tfdi"/>
  <title>Email Events Displaying Queued</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 20 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> Resend → Email Events</p>
    <p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>19:17:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating a delay in updating of email events. Emails are being sent/delivered, though the events may display as Queued..</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>19:17:48</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;ve identified the cause of the delay in email events. Event statuses are beginning to catch up. Emails continue to be sent and delivered as normal. Only the displayed status was affected..</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>19:29:26</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We&#039;ve deployed a fix for the delayed events. Webhook deliveries and email event statuses have caught up and are updating in real time. We&#039;re monitoring to confirm the fix holds..</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>20:01:18</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident is resolved. Webhook deliveries and metrics page updates have been stable since our fix was deployed. Sending and receiving were unaffected throughout. Thanks for your patience..</p>

        ]]>
  </content>
</entry>

</feed>