Vercel Blob store blocked after Advanced Operations limit — need data-preserving reactivation - Help

Hello Vercel team and community,

Our production store is currently returning HTTP 403 with “Your store is blocked”, so product images on https://www.blanwhi.com are unavailable to customers, especially on fresh mobile browsers.

www.blanwhi.com

BLANWHI

Project information

Team: khaitamphatphap-9324s-projects
Project: web-blanwhi
Blob host: fwbtazgkzxmhayut.public.blob.vercel-storage.com
Plan: Hobby

Usage shown in the dashboard

Storage: 85.93 MB / 1 GB
Simple Operations: 1,824 / 10,000
Advanced Operations: 2,325 / 2,000
Blob Data Transfer: 1.25 GB / 10 GB

We identified and fixed the cause. The app was calling Blob.list() repeatedly while reading keyed product-link records. Production now uses a compact encrypted index, so Blob.list() is no longer called per request and is retained only for one-time migration. Fix commit: https://github.com/khaitamphatphap-bit/web-blanwhi/commit/bb7fd4a7d812ce4c7fb9478bd5cfe1aff12d98a3

The application has fallback handling now, so the API/admin remains available, but the original product images are still inaccessible while the store is blocked.

Could a Vercel team member please reactivate the existing Blob store without deleting its data? We need to preserve the current product-image URLs and uploaded files.

Thank you.

Hi Khaitamphatphap,

Since the blocked metric is Advanced Operations and you found repeated Blob.list() calls as the cause, I would avoid deleting/recreating the Blob store if you need to preserve the existing image URLs.

This part probably needs a Vercel-side review/reactivation, but you can make the public case easier to verify by adding one compact evidence block:

Store host: fwbtazgkzxmhayut.public.blob.vercel-storage.com
Current error from image URL: HTTP 403 / "Your store is blocked"
Advanced Operations before fix: 2,325 / 2,000
Root cause: Blob.list() called repeatedly during product-link reads
Fix commit: bb7fd4a
Current behavior: normal production reads no longer call Blob.list()
Dashboard banner/resume message, if any:

It would also help to confirm from logs that normal customer page loads now read from the compact index and do not call Blob.list() anymore. That separates “please unblock the existing data” from “the same limit will be hit again immediately.”

I would not post the BLOB_READ_WRITE_TOKEN, private admin URLs, or any signed upload URLs. The store host, failing public image URL, usage screenshot, and fix commit should be enough for a public thread.