Netlify reported "Increase in errors for drag and drop deploys" on its status page at 2026-11-12 09:00 UTC.

Netlify did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-11-12 09:00 UTC and ended at 2026-11-12 09:00 UTC. It lasted 1 min.

How do I get alerts for Netlify?

Subscribe to the Netlify live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Netlify. outages.live reads it every few minutes and keeps every update.

NetlifyIncident ·

Increase in errors for drag and drop deploys

ResolvedOfficial update

Between 2026-11-12 09:00 UTC and 2026-11-13 17:27 UTC, a high number of drag and drop deploys were failing. The issue is now resolved.

The latest update from Netlify.

State

Resolved

Started

Lasted

1 min

Worst impact

Notice

Timeline

1 update

09:0009:0009:0009:0009:01

NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Netlify

Resolved

Between 2026-11-12 09:00 UTC and 2026-11-13 17:27 UTC, a high number of drag and drop deploys were failing. The issue is now resolved.

Netlify in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

36 min

This incident

100% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

11 h 16 min

median 36 min

90 days agoToday

Other Netlify incidents

All incidents

Netlify·Delayed Support Email Delivery to Microsoft 365 and Outlook Mailboxes

Netlify Helpdesk support email replies to Microsoft 365 and Outlook mailboxes have delivery delays. Netlify reports that a fix is in place and that the state is monitoring. Netlify monitors email delivery and will give an update when delivery is normal.

Degraded

Netlify·Partially Degraded Service

Netlify reported a degraded service that affected GitHub Webhooks. Netlify reports that this incident is resolved. The incident lasted 36 minutes.

Resolved

Netlify·Partially Degraded Service

Netlify reported that GitHub Webhooks had degraded performance. Netlify reports that the issue is resolved. The interruption lasted 18 minutes.

Resolved

Netlify·Partially Degraded Service

Netlify reported a partially degraded service for GitHub Webhooks. Netlify resolved the incident. The outage lasted 3 minutes.

Resolved

Netlify·Partially Degraded Service

Netlify reported degraded service for GitHub Webhooks. Netlify reports that the incident is resolved. The incident lasted 6 minutes.

Resolved

Follow Netlify

Your coding agent knows when Netlify is down, and tells you when a failure is theirs, not yours. You can also get Netlify incidents in a feed reader or in Slack.

Prompt

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 "netlify" and tell me if Netlify 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.

RSS

https://outages.live/feed.xml?providers=netlify

Slack

/feed subscribe https://outages.live/feed.xml?providers=netlify

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane