SalesEQ - Notice history

Cloudflare → Cloudflare Sites and Services → Network experiencing degraded performance

Ask AI - Operational

100% - uptime
May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Website - Operational

100% - uptime
May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Cloudflare → Cloudflare Sites and Services → Network - Degraded performance

Notice history

Jul 2026

Errors creating domains and API keys
  • Resolved
    UTC
    Resolved

    We have resolved the underlying issue and service has been resumed.

  • Identified
    UTC
    Identified

    We have identified an issue with creating API keys and domains and we are working on a fix now.

Cloudflare Malicious Upload Detection Issues
  • Resolved
    UTC
    Resolved

    This incident has been resolved.

  • Monitoring
    UTC
    Monitoring

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

  • Identified
    UTC
    Identified

    The issue has been identified and a fix is being implemented.

  • Investigating
    UTC
    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.

POST requests not succeeding
  • Resolved
    UTC
    Resolved

    This incident has been resolved.

  • Monitoring
    UTC
    Monitoring

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

  • Identified
    UTC
    Identified

    The issue has been identified and a fix is being implemented.

  • Update
    UTC
    Update

    We are continuing to investigate this issue.

  • Investigating
    UTC
    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.

Increased invocation failures for Hobby Team functions
  • Resolved
    UTC
    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.

  • Monitoring
    UTC
    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.

  • Identified
    UTC
    Identified

    We have identified the source of errors and are implementing a fix.

  • Investigating
    UTC
    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.

Network Performance Issues for AWS ap-northeast-1 region
  • Resolved
    UTC
    Resolved

    This incident has been resolved.

  • Monitoring
    UTC
    Monitoring

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

  • Identified
    UTC
    Identified

    The issue has been identified and a fix is being implemented.

  • Investigating
    UTC
    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.

Jun 2026

Delayed webhooks
  • Resolved
    UTC
    Resolved

    We have resolved the underlying issue, and all the affected webhooks have been sent.

  • Monitoring
    UTC
    Monitoring

    Affected webhooks are now being sent. We expect the affected webhooks to be sent within the next 20 minutes.

    No webhooks were lost.

  • Identified
    UTC
    Identified

    We have identified the issue and we are working on a fix now.

  • Update
    UTC
    Update

    We have identified that email events are being updated correctly in the dashboard, but webhook sending is delayed. The team is still investigating.

  • Investigating
    UTC
    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.

Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions
  • Resolved
    UTC
    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 ERRSTREAMPREMATURE_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.

Automations not starting
  • Resolved
    UTC
    Resolved

    We have resolved the underlying issue and service has been resumed.

  • Investigating
    UTC
    Investigating

    We are currently investigating an issue with automations not starting.

Issues downloading attachments
  • Resolved
    UTC
    Resolved

    We have resolved the underlying issue and service has been resumed.

  • Monitoring
    UTC
    Monitoring

    The fix for downloading email attachments has been pushed and we are now monitoring the situation.

  • Investigating
    UTC
    Investigating

    We are currently investigating issues with downloading attachments where existing download URLs would incorrectly return a 403 response.

Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region
  • Resolved
    UTC
    Resolved

    This incident has been resolved.

  • Update
    UTC
    Update

    We are continuing to monitor for any further issues.

  • Monitoring
    UTC
    Monitoring

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

  • Update
    UTC
    Update

    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.

  • Identified
    UTC
    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.

May 2026

Elevated Function Invocation Errors in Stockholm region (ARN1)
  • Resolved
    UTC
    Resolved

    This incident has been resolved.

  • Monitoring
    UTC
    Monitoring

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

  • Identified
    UTC
    Identified

    The issue has been identified and a fix is being implemented.

  • Investigating
    UTC
    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.

Resend dashboard facing intermittent errors
  • Resolved
    UTC
    Resolved

    We have resolved the underlying issue and service has been resumed.

  • Investigating
    UTC
    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.

Email Events - Scheduled Maintenance
  • Completed
    May 20, 2026 at 3:13 PMUTC
    Completed
    May 20, 2026 at 3:13 PMUTC

    We've completed our Email Events maintenance, and they are now showing the up-to-date status.

  • In progress
    May 20, 2026 at 2:05 PMUTC
    In progress
    May 20, 2026 at 2:05 PMUTC

    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.

  • Scheduled
    May 19, 2026 at 11:58 AMUTC
    Scheduled
    May 19, 2026 at 11:58 AMUTC

    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.

Elevated errors across multiple services in IAD1 (Washington, D.C., USA)
  • Resolved
    UTC
    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.

  • Monitoring
    UTC
    Monitoring

    We implemented a fix and are monitoring the results. Backlogs for Workflows and Queues will be processed within the next few hours.

  • Update
    UTC
    Update

    New workflow runs and queue messages are being processed now. Processing the backlog of existing workflow runs and queued messages is still being investigated.

  • Update
    UTC
    Update

    We are continuing to work on a fix for this issue.

  • Update
    UTC
    Update

    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.

  • Update
    UTC
    Update

    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.

  • Identified
    UTC
    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.

Inbound emails with incorrect "To" field when forwarded
  • Resolved
    UTC
    Resolved

    We have resolved the underlying issue by reverting the unintended breaking change and service has been resumed.

  • Identified
    UTC
    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.

May 2026 to Jul 2026

Next