Webflow incident

[RESOLVED] Reports of form notification emails not being delivered

Critical Resolved View vendor source →

Webflow experienced a critical incident on February 10, 2026 affecting Email Notifications, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Feb 10, 2026, 04:11 PM UTC
Resolved
Feb 11, 2026, 05:05 PM UTC
Duration
1d
Detected by Pingoru
Feb 10, 2026, 04:11 PM UTC

Affected components

Email Notifications

Update timeline

  1. investigating Feb 10, 2026, 04:11 PM UTC

    We’re investigating reports that form notification emails are not being delivered as expected for some customers. Our team is actively investigating and will share another update as soon as we have more information. In the meantime, form submissions can be reviewed via the forms tab in site settings.

  2. identified Feb 10, 2026, 04:30 PM UTC

    We’ve identified that this behaviour is arising due to an issue with an upstream provider. We’re actively working with them to resolve the issue and restore normal notification delivery as soon as possible. Form submissions themselves are not impacted, and can still be reviewed via the forms tab in site settings as expected.

  3. identified Feb 10, 2026, 06:02 PM UTC

    With the support of our upstream provider, the required actions to resolve the issue have been identified and work is ongoing. We will share another update as soon as a new information is available, and sincerely appreciate your patience and understanding as we work to restore this functionality. In the meantime, Form submissions can be accessed via the Forms tab in Site Settings.

  4. identified Feb 10, 2026, 09:22 PM UTC

    Work to restore full functionality to form submission notification emails is ongoing with the support of our upstream provider. In the meantime, form submissions can still be reviewed via the Forms tab in Site Settings. We sincerely appreciate your patience and understanding and will share another update as soon as new information is available.

  5. identified Feb 11, 2026, 01:04 AM UTC

    Work to restore full functionality to form submission notification emails is still ongoing, and we’re continuing to work closely with our upstream provider to resolve the issue and restore normal notification delivery.In the meantime, form submissions can still be reviewed via the Forms tab in Site Settings. We sincerely appreciate your continued patience and will share another update as soon as more information becomes available.

  6. identified Feb 11, 2026, 02:01 AM UTC

    Work to restore full functionality to form submission notification emails is still ongoing. At this time, we do not expect to share another update until tomorrow (Pacific time) unless we receive new information from our upstream provider. In the meantime, all form submissions continue to be successfully processed by Webflow and remain fully accessible via the Forms tab in Site Settings. Only notification emails are impacted. We recognize how disruptive this issue is for customers who rely on this functionality, and we remain engaged with our upstream provider to resolve the issue and restore normal notification delivery as soon as possible.

  7. monitoring Feb 11, 2026, 03:43 PM UTC

    Form notification email functionality is now restored and our upstream provider are now processing these emails as expected. While there is no current customer-facing impact, we are continuing to actively monitor the situation to ensure stability and will share another update as soon as possible.

  8. resolved Feb 11, 2026, 05:05 PM UTC

    This incident has been resolved. Due to an issue with an upstream provider, Form submission notification emails were not processed as expected between 21:30 February 10th - 21:30 February 11th (UTC). Form submissions received during this time processed as expected, and remain available to review via the Forms tab in Site Settings. We sincerely apologize for any inconvenience this issue caused, and appreciate your understanding as we worked with our upstream provider to resolve this issue.