Netlify incident: Degraded performance with Create API

Affected components

• Netlify Create API

1. resolvedMay 19, 2026, 14:52 UTC

   The incident with performance degradation for create.netlify.com has be resolved.

2. monitoringMay 19, 2026, 14:37 UTC

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

3. identifiedMay 19, 2026, 14:31 UTC

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

4. investigatingMay 19, 2026, 14:26 UTC

   We’re seeing degraded performance with create.netlify.com. Some customers are seeing issues with latency or 500 errors while accessing the create.netlify.com.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Netlify's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Anthropic: Elevated errors on Claude Opus 4.7Major · May 19, 2026, 14:03 UTC
• LaunchDarkly: Event Ingestion DelaysMajor · May 19, 2026, 14:49 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Twilio: Subset of AU Sender ID Registration Submissions Directly Transitioning to REJECTEDMinor · May 15, 2026, 20:51 UTC
• Snyk: Service Degradation on US-01 (app.snyk.io)Minor · May 18, 2026, 12:12 UTC
• ClickHouse Cloud: GCP us-east1 capacity constraints impacting cluster operationsMinor · May 18, 2026, 12:31 UTC
• Twilio: Delay in Getting Twilio/flows Templates Approved on WhatsappMinor · May 18, 2026, 18:42 UTC
• Snyk: Supply Chain Compromise on  @antv being investigated for more than 300 packages in npm ecosystemMinor · May 19, 2026, 05:29 UTC

How often does Netlify have incidents?

Netlify reported 16 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 57 min. See Netlify's uptime and incident history