Skip to main content
Vendor reliability

Vendor record

Netlify

Vendor reports Operational

Checked

Front door check counts and Netlify’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Netlify endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,878 of 2,878 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    1 more check gave no clear answer and is not counted.

    Endpoint checked
    api.netlify.com
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Netlify product, region or your app worked.

How we count front door checks

Netlify says

Incident posts from Netlify’s status page, with its titles, impact levels and times. They say what Netlify chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

4

incidents Netlify posted, last 30 days

All vendors’ incidents

Most recent records · all dates

  • Error accessing Netlify-hosted sites

    Minor

    Started, per Netlify

    Closed in our record(55m)

    Netlify’s post
  • Error accessing Netlify-hosted sites

    Major

    Started, per Netlify

    Closed in our record(28m)

    Netlify’s post
  • Elevated CDN Errors

    Minor

    Started, per Netlify

    Closed in our record(34m)

    Netlify’s post
  • Errors accessing Netlify-hosted sites

    Major

    Started, per Netlify

    Closed in our record(1h 32m)

    Netlify’s post
  • Elevated Image CDN Errors

    Minor

    Started, per Netlify

    Closed in our record(52m)

    Netlify’s post
15 older records
  • Increased Latency in IAD Region on Global Network

    Minor

    Started, per Netlify

    Closed in our record(1h 30m)

    Netlify’s post
  • Elevated Build Errors

    Major

    Started, per Netlify

    Closed in our record(39m)

    Netlify’s post
  • Errors Uploading Attachments to Agent Runners

    Minor

    Started, per Netlify

    Closed in our record(36m)

    Netlify’s post
  • Increase in Edge Function Errors

    Minor

    Started, per Netlify

    Closed in our record(32m)

    Netlify’s post
  • Connectivity issues affecting Bolt-powered sites

    Minor

    Started, per Netlify

    Closed in our record(5h 49m)

    Netlify’s post
  • AI Gateway: Claude Fable 5 unavailable

    Not specified

    Started, per Netlify

    Closed in our record(2d 1h)

    Netlify’s post
  • Elevated latency affecting image delivery

    Minor

    Started, per Netlify

    Closed in our record(19m)

    Netlify’s post
  • Elevated error rates for a subset of sites using Edge Functions

    Major

    Started, per Netlify

    Closed in our record(37m)

    Netlify’s post
  • Delayed builds due to Github incident

    Major

    Started, per Netlify

    Closed in our record(2h 11m)

    Netlify’s post
  • Image Delivery Issues

    Minor

    Started, per Netlify

    Closed in our record(35m)

    Netlify’s post
  • Support Communication Delivery Issues

    Major

    Started, per Netlify

    Closed in our record(2h 4m)

    Netlify’s post
  • Elevated Build Failures

    Minor

    Started, per Netlify

    Closed in our record(4h 47m)

    Netlify’s post
  • Elevated response times affecting origin services

    Critical

    Started, per Netlify

    Closed in our record(2h 1m)

    Netlify’s post
  • Degraded performance with Create API

    Minor

    Started, per Netlify

    Closed in our record(2h 31m)

    Netlify’s post
  • Degraded performance with Create API

    Minor

    Started, per Netlify

    Closed in our record(28m)

    Netlify’s post

Your code, your dependencies

See which of your code paths call Netlify

Connect GitHub or GitLab to find where your public or private repository uses Netlify. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Netlify status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · NetlifyStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/netlify?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Netlify status badge"></iframe>

Frequently Asked Questions

Is Netlify currently down?

Netlify's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Netlify last have an outage?

The most recent closed incident record began 11 days ago and spans 55 minutes. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Netlify?

No. CheckUpstream checks Netlify’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Netlify in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Netlify?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.