SalesEQ Status - Incident history https://status.saleseq.ai SalesEQ Wed, 22 Jul 2026 19:43:00 +0000 Errors creating domains and API keys Type: Incident Duration: 8 hours Affected Components: Resend → Email Sending → Single Email, Resend → General API, Resend → Email Events Jul 22, 19:51:00 GMT+0 - Resolved - We have resolved the underlying issue and service has been resumed. Jul 22, 19:43:00 GMT+0 - Identified - We have identified an issue with creating API keys and domains and we are working on a fix now. Type: Incident

Duration: 8 hours

Affected Components: , ,

<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> ]]> Wed, 22 Jul 2026 19:43:00 +0000 https://status.saleseq.ai/incident/cmryfhswt04ig0zrui9gvtm4b https://status.saleseq.ai/incident/cmryfhswt04ig0zrui9gvtm4b Cloudflare Malicious Upload Detection Issues Type: Incident Duration: 4 days, 16 hours and 15 minutes Affected Components: Cloudflare → Cloudflare Sites and Services → Firewall Jul 22, 08:19:31 GMT+0 - Resolved - This incident has been resolved. Jul 22, 06:27:16 GMT+0 - Investigating - 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. Jul 22, 06:37:13 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Jul 22, 07:09:34 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Type: Incident

Duration: 4 days, 16 hours and 15 minutes

Affected Components:

<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> ]]> Wed, 22 Jul 2026 06:27:16 +0000 https://status.saleseq.ai/incident/cmryfjtop042v0klc4v1oud3k https://status.saleseq.ai/incident/cmryfjtop042v0klc4v1oud3k POST requests not succeeding Type: Incident Duration: 4 days, 7 hours and 13 minutes Affected Components: Cloudflare → Cloudflare Sites and Services → CDN/Cache Jul 17, 15:02:12 GMT+0 - Investigating - 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. Jul 17, 15:06:16 GMT+0 - Investigating - We are continuing to investigate this issue. Jul 17, 15:50:28 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Jul 17, 16:30:40 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Jul 17, 16:45:25 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 4 days, 7 hours and 13 minutes

Affected Components:

<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> ]]> Fri, 17 Jul 2026 15:02:12 +0000 https://status.saleseq.ai/incident/cmryfilz404mw1blc6bs2lx3j https://status.saleseq.ai/incident/cmryfilz404mw1blc6bs2lx3j Increased invocation failures for Hobby Team functions Type: Incident Duration: 2 days, 18 hours and 55 minutes Affected Components: Vercel → Functions Jul 17, 14:12:58 GMT+0 - Investigating - 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. Jul 17, 14:19:52 GMT+0 - Identified - We have identified the source of errors and are implementing a fix. Jul 17, 14:27:39 GMT+0 - Monitoring - 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. Jul 17, 15:19:53 GMT+0 - Resolved - 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. Type: Incident

Duration: 2 days, 18 hours and 55 minutes

Affected Components:

<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> ]]> Fri, 17 Jul 2026 14:12:58 +0000 https://status.saleseq.ai/incident/cmryfho0j04t00rpi57m3j16s https://status.saleseq.ai/incident/cmryfho0j04t00rpi57m3j16s Network Performance Issues for AWS ap-northeast-1 region Type: Incident Duration: 19 hours and 45 minutes Affected Components: Cloudflare → Cloudflare Sites and Services → Network Jul 17, 07:31:00 GMT+0 - Investigating - 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. Jul 17, 07:36:01 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Jul 17, 07:44:12 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Jul 17, 07:50:45 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 19 hours and 45 minutes

Affected Components:

<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> ]]> Fri, 17 Jul 2026 07:31:00 +0000 https://status.saleseq.ai/incident/cmryfjpc304up0rpii387vl45 https://status.saleseq.ai/incident/cmryfjpc304up0rpii387vl45 Increased HTTP 500 Errors in Querétaro, Mexico Type: Incident Duration: 17 hours and 1 minute Affected Components: Cloudflare → Cloudflare Sites and Services → Network Jul 17, 01:25:53 GMT+0 - Identified - 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. Jul 17, 01:26:35 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Jul 17, 01:42:54 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 17 hours and 1 minute

Affected Components:

<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> ]]> Fri, 17 Jul 2026 01:25:53 +0000 https://status.saleseq.ai/incident/cmryfjpcb04ur0rpi0mryzsme https://status.saleseq.ai/incident/cmryfjpcb04ur0rpi0mryzsme Elevated errors on the dashboard Type: Incident Duration: 1 day and 21 hours Affected Components: Resend → General API, Resend → Email Sending → Single Email, Resend → Email Events Jul 16, 12:30:00 GMT+0 - Resolved - We have resolved the underlying issue and service has been resumed. Jul 16, 11:45:00 GMT+0 - Identified - We have identified increased error rates on the dashboard correlated with an upstream provider incident. We're shipping improvements to contain the errors. Type: Incident

Duration: 1 day and 21 hours

Affected Components: , ,

<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're shipping improvements to contain the errors..</p> ]]> Thu, 16 Jul 2026 11:45:00 +0000 https://status.saleseq.ai/incident/cmryfhswr04if0zru735m0a74 https://status.saleseq.ai/incident/cmryfhswr04if0zru735m0a74 Network Performance issues - Increased HTTP 502 Errors in HKG Type: Incident Duration: 23 days, 13 hours and 37 minutes Affected Components: Cloudflare → Cloudflare Sites and Services → Network Jul 15, 11:00:03 GMT+0 - Monitoring - 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. Jul 15, 20:25:40 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 23 days, 13 hours and 37 minutes

Affected Components:

<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> ]]> Wed, 15 Jul 2026 11:00:03 +0000 https://status.saleseq.ai/incident/cmryfjpc304uo0rpiojkkwvl4 https://status.saleseq.ai/incident/cmryfjpc304uo0rpiojkkwvl4 Increased latency across API endpoints and email sending Type: Incident Duration: 2 days, 5 hours and 27 minutes Affected Components: Resend → General API, Resend → Email Sending → Single Email Jul 10, 13:21:07 GMT+0 - Investigating - We're noticing increased API latency across different endpoints, causing delays in email sending. Jul 10, 13:53:56 GMT+0 - Monitoring - The deployment has been completed, and we're still monitoring. Latency has stabilized since 13:38 UTC. Jul 10, 14:14:35 GMT+0 - Resolved - We have resolved the underlying issue and service has been resumed. Jul 10, 13:31:11 GMT+0 - Identified - We have identified the issue and are deploying a fix now. The team is monitoring. Latency has recovered, but we're keeping this incident open for the next few minutes to monitor downstream services. Type: Incident

Duration: 2 days, 5 hours and 27 minutes

Affected Components: ,

<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'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'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're keeping this incident open for the next few minutes to monitor downstream services..</p> ]]> Fri, 10 Jul 2026 13:21:07 +0000 https://status.saleseq.ai/incident/cmryfhswu04ih0zru8qlyqcnc https://status.saleseq.ai/incident/cmryfhswu04ih0zru8qlyqcnc Network Performance Issues in London Type: Incident Duration: 1 day, 12 hours and 3 minutes Affected Components: Cloudflare → Cloudflare Sites and Services → Network Jul 8, 01:56:02 GMT+0 - Investigating - 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. Jul 8, 02:32:05 GMT+0 - Resolved - This incident has been resolved. Jul 8, 01:56:46 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Type: Incident

Duration: 1 day, 12 hours and 3 minutes

Affected Components:

<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> ]]> Wed, 8 Jul 2026 01:56:02 +0000 https://status.saleseq.ai/incident/cmryfjpcb04uq0rpi9e4qio0u https://status.saleseq.ai/incident/cmryfjpcb04uq0rpi9e4qio0u Email sending delay Type: Incident Duration: 2 days, 15 hours and 17 minutes Affected Components: Resend → Email Sending → Single Email Jul 3, 10:17:49 GMT+0 - Investigating - 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. Jul 3, 11:21:06 GMT+0 - Resolved - We have resolved the underlying issue and services have been recovered. Type: Incident

Duration: 2 days, 15 hours and 17 minutes

Affected Components:

<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> ]]> Fri, 3 Jul 2026 10:17:49 +0000 https://status.saleseq.ai/incident/cmryfhxjf04jc0zruyo09wgbw https://status.saleseq.ai/incident/cmryfhxjf04jc0zruyo09wgbw Degraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1) Type: Incident Duration: 14 hours and 38 minutes Affected Components: Vercel → Functions, Vercel → CDN → IAD1 - Washington DC, USA Jul 2, 16:39:55 GMT+0 - Monitoring - A fix has been implemented and we are observing recovery across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor. Jul 2, 16:33:07 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Jul 2, 16:46:33 GMT+0 - Resolved - This incident has been resolved. Jul 2, 16:31:55 GMT+0 - Investigating - We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available. Type: Incident

Duration: 14 hours and 38 minutes

Affected Components: ,

<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, & 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, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available..</p> ]]> Thu, 2 Jul 2026 16:31:55 +0000 https://status.saleseq.ai/incident/cmryfhji804mk1blcir1n0bib https://status.saleseq.ai/incident/cmryfhji804mk1blcir1n0bib Elevated error rates across our APIs and SMTP services Type: Incident Duration: 1 day Affected Components: Resend → Email Sending → Single Email, Resend → General API, Resend → Email Events Jul 1, 15:43:00 GMT+0 - Monitoring - Services are recovering to normal. Our team is actively monitoring to ensure no further issues are impacting the requests. Jul 1, 16:00:00 GMT+0 - Resolved - Our team has mitigated the issue and this incident is fully resolved. All services are operational. Jul 1, 15:36:00 GMT+0 - Identified - 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. Type: Incident

Duration: 1 day

Affected Components: , ,

<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> ]]> Wed, 1 Jul 2026 15:36:00 +0000 https://status.saleseq.ai/incident/cmryfhswr04id0zruc1zahidw https://status.saleseq.ai/incident/cmryfhswr04id0zruc1zahidw Delayed webhooks Type: Incident Duration: 23 hours and 17 minutes Affected Components: Resend → Email Events Jun 22, 20:34:04 GMT+0 - Investigating - 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. Jun 22, 20:38:00 GMT+0 - Investigating - We have identified that email events are being updated correctly in the dashboard, but webhook sending is delayed. The team is still investigating. Jun 22, 20:48:03 GMT+0 - Identified - We have identified the issue and we are working on a fix now. Jun 22, 20:48:36 GMT+0 - Monitoring - Affected webhooks are now being sent. We expect the affected webhooks to be sent within the next 20 minutes. No webhooks were lost. Jun 22, 20:57:22 GMT+0 - Resolved - We have resolved the underlying issue, and all the affected webhooks have been sent. Type: Incident

Duration: 23 hours and 17 minutes

Affected Components:

<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> ]]> Mon, 22 Jun 2026 20:34:04 +0000 https://status.saleseq.ai/incident/cmryfi7mb04mv0kpif7e16mgi https://status.saleseq.ai/incident/cmryfi7mb04mv0kpif7e16mgi Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions Type: Incident Affected Components: Vercel → Functions Jun 19, 17:54:16 GMT+0 - Resolved - 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. Type: Incident

Affected Components:

<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> ]]> Fri, 19 Jun 2026 17:54:16 +0000 https://status.saleseq.ai/incident/cmryfhpik04t20rpiw6nk9k73 https://status.saleseq.ai/incident/cmryfhpik04t20rpiw6nk9k73 Automations not starting Type: Incident Duration: 1 day and 12 hours Affected Components: Resend → General API, Resend → Email Sending → Single Email, Resend → Email Events Jun 17, 16:19:00 GMT+0 - Investigating - We are currently investigating an issue with automations not starting. Jun 17, 16:55:00 GMT+0 - Resolved - We have resolved the underlying issue and service has been resumed. Type: Incident

Duration: 1 day and 12 hours

Affected Components: , ,

<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> ]]> Wed, 17 Jun 2026 16:19:00 +0000 https://status.saleseq.ai/incident/cmryfhswj04ic0zruc1ob4fxx https://status.saleseq.ai/incident/cmryfhswj04ic0zruc1ob4fxx Issues downloading attachments Type: Incident Duration: 3 days, 7 hours and 30 minutes Affected Components: Resend → General API Jun 15, 20:40:47 GMT+0 - Monitoring - The fix for downloading email attachments has been pushed and we are now monitoring the situation. Jun 15, 21:14:40 GMT+0 - Resolved - We have resolved the underlying issue and service has been resumed. Jun 15, 19:55:10 GMT+0 - Investigating - We are currently investigating issues with downloading attachments where existing download URLs would incorrectly return a 403 response. Type: Incident

Duration: 3 days, 7 hours and 30 minutes

Affected Components:

<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> ]]> Mon, 15 Jun 2026 19:55:10 +0000 https://status.saleseq.ai/incident/cmryfhswr04ie0zruq5s813i4 https://status.saleseq.ai/incident/cmryfhswr04ie0zruq5s813i4 Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region Type: Incident Duration: 2 days, 14 hours and 24 minutes Affected Components: Vercel → Functions Jun 8, 18:57:47 GMT+0 - Identified - 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. Jun 8, 19:04:25 GMT+0 - Identified - We'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. Jun 8, 19:36:38 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Jun 8, 19:36:44 GMT+0 - Monitoring - We are continuing to monitor for any further issues. Jun 8, 20:00:11 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days, 14 hours and 24 minutes

Affected Components:

<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'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> ]]> Mon, 8 Jun 2026 18:57:47 +0000 https://status.saleseq.ai/incident/cmryfhpii04t10rpimbh900z7 https://status.saleseq.ai/incident/cmryfhpii04t10rpimbh900z7 API quota reporting incorrect numbers Type: Incident Duration: 1 day, 6 hours and 2 minutes Affected Components: Resend → Email Sending → Single Email Jun 3, 15:45:19 GMT+0 - Identified - We are currently reverting a change that cause quotas to be calculated incorrectly. Jun 3, 16:10:54 GMT+0 - Monitoring - The fix has been pushed and we are now monitoring the situation. Jun 3, 16:15:21 GMT+0 - Resolved - We have resolved the underlying issue and service has been resumed. Type: Incident

Duration: 1 day, 6 hours and 2 minutes

Affected Components:

<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> ]]> Wed, 3 Jun 2026 15:45:19 +0000 https://status.saleseq.ai/incident/cmryfhxiz04jb0zrupdetqn4t https://status.saleseq.ai/incident/cmryfhxiz04jb0zrupdetqn4t Elevated Function Invocation Errors in Stockholm region (ARN1) Type: Incident Duration: 2 days, 11 hours and 34 minutes Affected Components: Vercel → Functions May 28, 16:00:14 GMT+0 - Investigating - We'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. May 28, 16:18:09 GMT+0 - Identified - The issue has been identified and a fix is being implemented. May 28, 16:37:04 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. May 28, 16:59:49 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days, 11 hours and 34 minutes

Affected Components:

<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'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> ]]> Thu, 28 May 2026 16:00:14 +0000 https://status.saleseq.ai/incident/cmryfhpiq04t40rpioz3u64x5 https://status.saleseq.ai/incident/cmryfhpiq04t40rpioz3u64x5 Resend dashboard facing intermittent errors Type: Incident Duration: 7 hours Affected Components: Resend → General API, Resend → Email Sending → Single Email, Resend → Email Events May 26, 15:29:00 GMT+0 - Investigating - We are currently investigating increased latency in Resend dashboard. At this time, you may experience delays and errors while trying to access our dashboard. May 26, 15:36:00 GMT+0 - Resolved - We have resolved the underlying issue and service has been resumed. Type: Incident

Duration: 7 hours

Affected Components: , ,

<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> ]]> Tue, 26 May 2026 15:29:00 +0000 https://status.saleseq.ai/incident/cmryfht3y04ij0zruz7bqrrp9 https://status.saleseq.ai/incident/cmryfht3y04ij0zruz7bqrrp9 Email Events - Scheduled Maintenance Type: Maintenance Duration: 1 hour Affected Components: Resend → Email Events May 20, 15:13:56 GMT+0 - Completed - We've completed our Email Events maintenance, and they are now showing the up-to-date status. May 19, 11:58:27 GMT+0 - Scheduled - 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. May 20, 14:05:31 GMT+0 - Identified - 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. Type: Maintenance

Duration: 1 hour

Affected Components:

<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'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> ]]> Wed, 20 May 2026 14:00:00 +0000 https://status.saleseq.ai/maintenance/cmryfi7nj04mx0kpi41p1zgeu https://status.saleseq.ai/maintenance/cmryfi7nj04mx0kpi41p1zgeu Elevated errors across multiple services in IAD1 (Washington, D.C., USA) Type: Incident Duration: 13 days, 8 hours and 42 minutes Affected Components: Vercel → Functions May 8, 01:18:59 GMT+0 - Identified - 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. May 8, 01:47:09 GMT+0 - Identified - 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. May 8, 02:13:23 GMT+0 - Identified - 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. May 8, 02:18:42 GMT+0 - Identified - We are continuing to work on a fix for this issue. May 8, 02:33:12 GMT+0 - Identified - New workflow runs and queue messages are being processed now. Processing the backlog of existing workflow runs and queued messages is still being investigated. May 8, 04:54:34 GMT+0 - Monitoring - We implemented a fix and are monitoring the results. Backlogs for Workflows and Queues will be processed within the next few hours. May 8, 06:39:41 GMT+0 - Resolved - We'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. Type: Incident

Duration: 13 days, 8 hours and 42 minutes

Affected Components:

<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'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> ]]> Fri, 8 May 2026 01:18:59 +0000 https://status.saleseq.ai/incident/cmryfhpil04t30rpiyov4rxj2 https://status.saleseq.ai/incident/cmryfhpil04t30rpiyov4rxj2 Inbound emails with incorrect "To" field when forwarded Type: Incident Duration: 8 days and 5 hours Affected Components: Resend → General API, Resend → Email Sending → Single Email, Resend → Email Events May 8, 17:47:00 GMT+0 - Resolved - We have resolved the underlying issue by reverting the unintended breaking change and service has been resumed. May 7, 14:54:00 GMT+0 - Identified - 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 "To" 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. Type: Incident

Duration: 8 days and 5 hours

Affected Components: , ,

<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 "To" 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> ]]> Thu, 7 May 2026 14:54:00 +0000 https://status.saleseq.ai/incident/cmryfhsxg04ii0zrub18akg2g https://status.saleseq.ai/incident/cmryfhsxg04ii0zrub18akg2g Elevated Functions Invocation Errors in ICN1 (Seoul, South Korea) Region Type: Incident Affected Components: Vercel → Functions May 1, 11:30:44 GMT+0 - Resolved - 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. Type: Incident

Affected Components:

<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> ]]> Fri, 1 May 2026 11:30:44 +0000 https://status.saleseq.ai/incident/cmryfhpiq04t50rpi8vxvtfva https://status.saleseq.ai/incident/cmryfhpiq04t50rpi8vxvtfva Email Events Displaying Queued Type: Incident Duration: 1 day, 20 hours and 13 minutes Affected Components: Resend → Email Events Apr 28, 19:17:04 GMT+0 - Investigating - We are currently investigating a delay in updating of email events. Emails are being sent/delivered, though the events may display as Queued. Apr 28, 19:17:48 GMT+0 - Identified - We'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. Apr 28, 19:29:26 GMT+0 - Monitoring - We've deployed a fix for the delayed events. Webhook deliveries and email event statuses have caught up and are updating in real time. We're monitoring to confirm the fix holds. Apr 28, 20:01:18 GMT+0 - Resolved - 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. Type: Incident

Duration: 1 day, 20 hours and 13 minutes

Affected Components:

<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'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've deployed a fix for the delayed events. Webhook deliveries and email event statuses have caught up and are updating in real time. We'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> ]]> Tue, 28 Apr 2026 19:17:04 +0000 https://status.saleseq.ai/incident/cmryfi7mg04mw0kpi5xd1tfdi https://status.saleseq.ai/incident/cmryfi7mg04mw0kpi5xd1tfdi