Intermittent Internal Server Error on Next.js site, MissingBlobsEnvironmentError in NetlifyCacheHandler

[Parkin1234]

Hi Netlify support,

My Netlify site is:

market-day-group-creator.netlify.app

This is not a DNS issue. I am not using a custom domain.

This is not a build failure. The deploys build successfully, but the deployed site intermittently returns:

Internal Server Error

Framework and versions:

Next.js 16.2.6
React 19.2.4
React DOM 19.2.4
@supabase/ssr ^0.10.3
@supabase/supabase-js ^2.106.2

The app does not directly use Netlify Blobs.

The function logs repeatedly show this error:

Error [MissingBlobsEnvironmentError]: The environment has not been configured to use Netlify Blobs. To use it manually, supply the following properties when creating a store: deployID
at getDeployStore (.netlify/dist/run/storage/regional-blob-store.cjs:780:11)
at getRegionalBlobStore (.netlify/dist/run/storage/regional-blob-store.cjs:833:10)
at getMemoizedKeyValueStoreBackedByRegionalBlobStore (.netlify/dist/run/storage/storage.cjs:48:69)
at new NetlifyCacheHandler (.netlify/dist/run/handlers/cache.cjs:55:92)

What happens:

1. The site works initially.

2. After clicking around, or sometimes after leaving the browser open and then navigating again, pages begin returning Internal Server Error.

3. Once the error starts, it can affect multiple routes, including /login and /dashboard/proposed-teams.

4. The error appears in the Netlify function logs as MissingBlobsEnvironmentError in NetlifyCacheHandler.

5. There is no app-code stack trace shown in the log.

Routes where I have seen the error include:

/login
/dashboard/proposed-teams
/dashboard/create-event
/dashboard/guides/poster?eventId=…

Things already tried:

1. Local production build succeeds.

2. Netlify deploy succeeds.

3. Retried deploy with cleared cache.

4. Set NETLIFY_NEXT_SKEW_PROTECTION=true and redeployed.

5. Removed explicit revalidatePath calls from the app and redeployed.

6. Rolled production back to an earlier deploy, which restored the live site.

7. Tested branch deploys. A branch deploy using code that appears stable in production still eventually produced the same MissingBlobsEnvironmentError.

Current state:

Production is currently rolled back and stable at main@50e79d7.

The problematic deploys include later production and branch deploys where the runtime function logs show MissingBlobsEnvironmentError.

My question:

Is this a known issue with the Netlify Next.js runtime/cache handler or Netlify Blobs deploy-store setup for Next.js sites?

What is the recommended fix or workaround when the app does not use Netlify Blobs directly, but NetlifyCacheHandler is throwing MissingBlobsEnvironmentError?

I can provide deploy IDs, timestamps, build settings screenshots, and fuller logs if needed.

Example function log:

May 31, 03:51:09 PM: facbaac0 ERROR ⨯ Error [MissingBlobsEnvironmentError]: The environment has not been configured to use Netlify Blobs. To use it manually, supply the following properties when creating a store: deployID
at getDeployStore (.netlify/dist/run/storage/regional-blob-store.cjs:780:11)
at getRegionalBlobStore (.netlify/dist/run/storage/regional-blob-store.cjs:833:10)
at getMemoizedKeyValueStoreBackedByRegionalBlobStore (.netlify/dist/run/storage/storage.cjs:48:69)
at new NetlifyCacheHandler (.netlify/dist/run/handlers/cache.cjs:55:92)
May 31, 03:51:09 PM: facbaac0 Duration: 1802.23 ms Memory Usage: 156 MB

[Parkin1234]

I saw related forum posts where MissingBlobsEnvironmentError was caused by user code initializing a Netlify Blobs store outside a handler, or by using the Blobs API directly from a function. My case seems different because my app does not call getStore(), getDeployStore(), or use @netlify/blobs directly. The stack trace points to NetlifyCacheHandler inside .netlify/dist/run/handlers/cache.cjs.

[peades]

Exact same intermittent issue here. Also Next 16, also do not use any netlify blob features explicitly.

[Kathryn-Marie]

Same here. Would love an update on a fix.

[Parkin1234]

Thanks both. That is helpful confirmation. My app also uses Next 16 and does not directly use any Netlify Blobs APIs. The stack trace points to NetlifyCacheHandler inside the generated Netlify runtime. I have temporarily moved testing to a Vercel clone, where I have not reproduced the issue so far, but I would still like to know whether there is a Netlify-side fix or workaround.

[rodrigo4635]

Same here, it started happening today without any deploy or change in the project

[emersonvisuals]

I am also facing the same issues across all my sites. Most are using Next.js / Sanity for the CMS whereas others are using React and they are also getting the same errors. I have checked my function logs and can see this error:

RROR ⨯ Error [MissingBlobsEnvironmentError]: The environment has not been configured to use Netlify Blobs. To use it manually, supply the following properties when creating a store: deployID
at getDeployStore (.netlify/dist/run/storage/regional-blob-store.cjs:780:11)
at getRegionalBlobStore (.netlify/dist/run/storage/regional-blob-store.cjs:833:10)
at getMemoizedKeyValueStoreBackedByRegionalBlobStore (.netlify/dist/run/storage/storage.cjs:48:69)
at new NetlifyCacheHandler (.netlify/dist/run/handlers/cache.cjs:55:92)

Appears to be the same as what you are experiencing

[sbrokenshire]

We also are experiencing the same issue. Would appreciate a fast response as we are in a critical donation period.

Here’s what Claude AI said:
That’s the key detail. This error is coming from Netlify’s own Next.js runtime (@netlify/plugin-nextjs), not your code. Netlify uses Blobs internally to power Next.js’s Incremental Cache (ISR, fetch caching, etc.) — you can see it in the stack trace:

NetlifyCacheHandler → getRegionalBlobStore → getDeployStore

This means the NETLIFY_BLOBS_CONTEXT environment variable isn’t being injected into your function at runtime, which is a Netlify platform/plugin configuration issue.This is a known, active issue with Netlify’s Next.js runtime (opennextjs-netlify), not your code. The error occurs intermittently — the site works initially, then after navigating around, multiple routes begin returning Internal Server Errors with this exact MissingBlobsEnvironmentError in NetlifyCacheHandler. The root cause is that Netlify’s cache handler loses its Blobs environment context between requests.

Here are your options, from easiest to most involved:

---

Option 1 — Force a fresh redeploy (with cache cleared)

Sometimes the deployed function bundle gets into a bad state. In the Netlify UI:

Deploys → Trigger deploy → Clear cache and deploy site

If it’s intermittent, this may resolve it temporarily but probably won’t fix it permanently.

---

Option 2 — Pin @netlify/plugin-nextjs to a stable version

The runtime is injected automatically, but you can pin it in netlify.toml to avoid being silently upgraded to a broken version:

[[plugins]]
package = "@netlify/plugin-nextjs"

Then in package.json:

"devDependencies": {
  "@netlify/plugin-nextjs": "5.x.x"
}

Check the releases page for the latest stable tag and use a specific version you know works.

---

Option 3 — Disable the Netlify cache handler entirely

If you don’t need ISR/on-demand revalidation, you can bypass NetlifyCacheHandler entirely by setting this in your next.config.js:

/** @type {import('next').NextConfig} */
const nextConfig = {
  // Disable ISR/fetch caching so Netlify's Blobs-backed handler isn't used
  experimental: {
    isrMemoryCacheSize: 0,
  },
};

module.exports = nextConfig;

Or more directly, tell Next.js not to use the Netlify-injected handler by setting:

// next.config.js
module.exports = {
  cacheMaxMemorySize: 0,
};

---

Option 4 — Set NETLIFY_NEXT_SKEW_PROTECTION

Add this environment variable in your Netlify site settings (Site configuration → Environment variables):

NETLIFY_NEXT_SKEW_PROTECTION = true

This was one of the suggested mitigations in the community thread for this exact error pattern, though it didn’t fully resolve it for everyone.

---

Option 5 — Open a support ticket with Netlify

This appears to be a platform-side issue with the Netlify Next.js runtime/cache handler or the Blobs deploy-store setup. Since your code doesn’t use Blobs at all and it’s the runtime that’s failing, this warrants a Netlify support ticket. Include:

• Your site name

• Affected deploy IDs

• The full function log snippet showing the error and the preceding request ID (e.g. facbaac0)

The Netlify support forum thread for this specific issue is very recent (May 31, 2026), so it may be an active regression in their runtime.

---

What Next.js version and @netlify/plugin-nextjs version are you on? That’ll help narrow down whether a specific version combo is the culprit.

[CEMort]

Adding another affected production site — criticalexam.com.au (Next.js 16.1.4, @netlify/plugin-nextjs v5.15.11, Supabase, no direct use of @netlify/blobs). Identical stack trace:

"
MissingBlobsEnvironmentError: … supply the following properties when creating a store: deployID
at getDeployStore (.netlify/dist/run/storage/regional-blob-store.cjs:780)
at getRegionalBlobStore (.netlify/dist/run/storage/regional-blob-store.cjs:833)
at getMemoizedKeyValueStoreBackedByRegionalBlobStore (.netlify/dist/run/storage/storage.cjs:48)
at new NetlifyCacheHandler (.netlify/dist/run/handlers/cache.cjs:55)
"

A few things I’ve observed:

• It appears to be per-function-instance. Once an instance starts throwing, it does so on every request it serves. Loading from a different device/network (escaping keep-alive to the bad instance) returns a healthy response. So some instances have the Blobs context and others don’t.
• Pages that fan out to many endpoints fail ~100% of the time (our admin dashboard fires many API calls at once, so at least one always hits a poisoned instance), while single-document requests fail intermittently.
• Failures happen at handler construction (~8–170 ms), before any of our own code runs.

Importantly, no customer-side workaround restores service for us:

• Clear-cache redeploy doesn’t fix it (fresh deploys/instances also throw).
• Rolling back to a previously-healthy deploy doesn’t fix it either — that deploy now throws the same error.

I’ve also opened a support ticket. Would be great to get this raised as an incident — happy to share request IDs / deploy IDs with staff. Following along here too.

[KJC]

Netlify this is not acceptable.

I have spent more than three days diagnosing this exact issue for a client, assuming it was caused by something in their application. Based on this thread, it’s clear that multiple customers are seeing the same intermittent Internal Server Error caused by MissingBlobsEnvironmentError, including sites that do not use Netlify Blobs directly (my clients site).

My client also opened a support ticket and has received no response. That is extremely frustrating. This has cost us days of engineering time, damaged client confidence, and forced us to investigate rollbacks and alternative hosting options just to keep the site stable.

The fact that multiple customers are reporting the same runtime-level failure, yet this has not been detected, acknowledged, or escalated as an incident, points to a serious failure in Netlify’s monitoring, incident response, and customer support processes.

This needs urgent acknowledgement. From a customer side and an engineer who has never worked with Netlify before, this has been handled very poorly and has been a very frustrating experience.

[MJPrott]

An update on a fix would be appreciated. This should be raised as an incident if not already.

[sbrokenshire]

Not sure if anyone else is noticing an improvement in the error-rate this morning?

There was a definite spike for several days from about May 30 to 1 Jun. Coinciding with a spike in the average duration of requests during that period.

This morning I have been unable to replicate the issue. Fingers crossed they’ve been working on a fix?

[sbrokenshire]

The spike in average duration of requests we saw during the period of high internal server errors.

[CEMort]

Update from our side: as of today we’re also no longer able to reproduce this error, and our site has been running normally, with no code changes on our end. Netlify has also confirmed via our support ticket that they’ve escalated the issue for investigation. Will report back here if it recurs.

[ivaaan]

Hi! I’m Ivan, leading Platform here at Netlify. We sincerely apologize for the incident — one of our CDN nodes in the Sydney region has been impacted. Unfortunately, we weren’t able to detect it on time due to the low error rate for the region. After detecting this, our team retroactively statuspaged at Netlify Status - Blobs issues in Sydney region.

We’re improving our monitoring and anomaly detection mechanisms as an outcome of this incident.

[MJPrott]

Hi Ivan,

Thank you for confirming that the issue was caused by a CDN node in the Sydney region.

To be clear, the apology provided here does not feel sincere. It reads like a generic, AI-generated response (yes your use of the ‘—’ is a give away) , and that is extremely frustrating given the impact this incident has had on our business and our clients. An AI generated apology does not address the damage caused, nor does it reflect the seriousness of the situation.

This incident has created serious and potentially irreparable trust issues for us and our clients. The fact that it was not detected in time, and that we were left dealing with the impact without timely visibility or communication, points to a concerning lack of urgency and care from Netlify’s side.

For us, this was not a minor inconvenience. It directly affected client confidence, created unnecessary operational pressure, and left us having to explain failures that were completely outside of our control. We spent our entire weekend trying to figure out what was going on.

We need more than a generic apology and a broad statement about improving monitoring. We need clear answers on why this was not detected sooner, why affected customers were not informed earlier, and what specific safeguards are being put in place to prevent this from happening again, particularly in the Sydney region.

At this stage, our confidence in Netlify’s platform and incident response has been materially damaged.

[Parkin1234]

Agree with MJPrott. I spent around 8 hours troubleshooting assuming this was an issue at my end. I ended up moving a clone over to Vercel where I am now continuing my build. I’m lucky my build wasn’t a live site like others affected, and I have the luxury of moving platforms easily. @MJPrott I hope nothing like this happens again for you and your clients! AP