Netlify Outage Check
Is Netlify Down Right Now?
✅ Netlify is up and working normally. Checked: 5:10 PM (GMT+8).
Auto-refreshing live data in 60s
| Component | Status |
|---|---|
| Agent Runners | Operational |
| AI Gateway | Operational |
| Analytics | Operational |
| API | Operational |
| Atlassian Bitbucket API | Operational |
| Atlassian Bitbucket SSH | Operational |
| Atlassian Bitbucket Webhooks | Operational |
| Billing | Operational |
| Build Pipeline | Operational |
| Collaborative Deploy Previews | Operational |
| Domain Purchasing | Operational |
| Edge Functions | Operational |
| Git Gateway | Operational |
| GitHub API Requests | Operational |
| GitHub Git Operations | Operational |
| GitHub Webhooks | Operational |
| High-Performance Edge Network | Operational |
| Hosted DNS | Operational |
| Identity | Operational |
| Live Tunnel | Operational |
| Log Drains | Operational |
| Name.com | Operational |
| Netlify Application UI | Operational |
| Netlify Blobs | Operational |
| Netlify Connect | Operational |
| Netlify Create API | Operational |
| Netlify Forms | Operational |
| Netlify Functions | Operational |
| Netlify Helpdesk | Operational |
| Netlify Image CDN | Operational |
| Netlify Observability | Operational |
| Netlify Support Forums | Operational |
| npm, Inc. Registry Reads | Operational |
| NS1 API | Operational |
| NS1 Management Portal | Operational |
| Origin Servers | Operational |
| Prerendering | Operational |
| Standard Edge Network | Operational |
| Third-Party Services | Operational |
| Visual Editor | Operational |
100.000%
Uptime
62m
MTTR
6.7
Avg Incidents / Mo
90 Days AgoToday
Netlify Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 30m
Affected: Website, DNS Services
Netlify API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 53m
Affected: API Requests, API Portal
Netlify Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 1h 23m
Affected: Core Service, Website
Netlify Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 49m
Affected: Core Service, Website
Netlify API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 42m
Affected: API Requests, API Portal
Are you having problems with Netlify?
Submit your report to help alert other developers.
Downtime Reports: Last 2 Hours
2 Hours AgoNow
Troubleshooting Guide
- 1Hard RefreshBypass cache (Ctrl+F5 or Cmd+Shift+R).
- 2Flush DNSRun
ipconfig /flushdns.
Uptime Alternatives
GitHub
Leading developer platform.
Slack
Real-time team communication.
Yes, Netlify maintains an official status page. However, our real-time tracker aggregates reports faster.
Historical records indicate that the mean time to resolve (MTTR) is approximately 62 minutes.
Outages can happen due to configuration mistakes, database freezes, edge network issues, or infrastructure drops.
You can subscribe to live alerts on this page. We send emails on status updates.
Try bypass caching by executing hard refresh, flush local DNS, or use alternatives listed below.