[MONITORING] Reports of issues accessing the Dashboard for some customers
Some Webflow customers could not access the Dashboard. Webflow reports that this incident is resolved. The issue lasted from about 01:05 to 01:33 UTC.
State
Resolved
Started
Lasted
1 h 12 min
Worst impact
Major outage
Timeline
3 updatesInvestigating
12 min 16%
Monitoring
1 h 84%
Updates
Times in UTCAs posted by Webflow
There were issues accessing the Dashboard affecting some customers between approximately 01:05 and 01:33 UTC. We're no longer seeing customer impact related to this issue. This incident is now resolved. Thank you for your patience while we worked through this.
We're no longer seeing active customer impact related to issues accessing the Dashboard affecting some customers. Our team is continuing to monitor the situation closely and will share another update shortly.
We're investigating reports of issues accessing the Dashboard affecting some customers. Our team is actively investigating and will share another update as soon as we have more information.
Affected components
1Webflow in the last 90 days
Full historyIncidents in 90 days
8
Days with an incident
10
Median duration
2 h 51 min
This incident
58% shorter than the median
Other Webflow incidents
All incidentsWebflow·[RESOLVED] Increased publishing times for some customers
Following continued monitoring, we’ve confirmed that the issue affecting publishing times has been resolved and there is no current customer impact. We appreciate your patience while our team worked to resolve this issue.
Webflow·[RESOLVED] Reports of form submission notification emails not being delivered for some customers
This incident is now resolved. Form submission notification emails were impacted between 00:46 UTC on September 21 and 15:33 UTC on September 22. New form submissions are now triggering notification emails as expected. During this time, form submissions continued to be received and saved as expected, and webhook delivery was unaffected. Notification emails that were not delivered during the affected timeframe will not be delivered retroactively. Affected customers can review submissions from this timeframe via: - the Forms tab in Site settings - the data_forms MCP tool - the Form Submissions API endpoints We appreciate your patience while we worked with our upstream provider to resolve this issue.
Webflow·[RESOLVED] Reports of issues authorizing MCP for sites within Client Workspaces
This incident has been resolved. Thank you for your patience while we worked on this issue.
Webflow·[RESOLVED] Reports of 500 intermittent errors affecting some hosted sites
Between approximately 08:29 - 9:40am UTC, some hosted sites experienced intermittent 500 errors over the following short periods: 08:29–08:35 UTC 08:42–08:52 UTC 08:58–09:04 UTC 09:32–09:40 UTC This predominantly impacted sites that were recently published. We’re no longer seeing customer impact related to this issue, and the incident is now resolved. We sincerely appreciate your patience while our team worked through this issue.
Webflow·[RESOLVED] Reports of issues impacting multiple Webflow services
Following continued monitoring, we’ve confirmed that the issue affecting multiple Webflow services has been resolved. This incident is now closed. We appreciate your patience while we worked with our upstream provider to resolve this issue.
Follow Webflow
Your coding agent knows when Webflow is down, and tells you when a failure is theirs, not yours. You can also get Webflow incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "webflow" and tell me if Webflow has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=webflow/feed subscribe https://outages.live/feed.xml?providers=webflowFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane