#blob

Jacob Paris Pretty much any database would be a good fit for your project. The harder part will be a user login feature, so if you don't have any opinions of your own about it I'd recommend picking either Neon or Supabase since they have auth login systems built in, and they can also store your other data.

Ryu Hi Operendia, Your evidence points away from the app upload code and toward the public Blob serving path. If the Blob API can list the object with `HTTP 200`, but the direct public URL returns: ``` 503 SERVICE_UNAVAILABLE X-Vercel-Error: SERVICE_UNAVAILABLE Body: The deployment is currently unavailable ``` then this is not a normal “file missing” case. A missing blob would be a different kind of failure, and your URL format also matches the public Blob URL format Vercel documents: https://vercel.com/docs/vercel-blob/public-storage I’d do one isolation test before escalating it as store-specific: ``` 1. Create a brand-new public Blob store in the same team 2. Upload one tiny test image/text file with access: "public" 3. Open the returned public URL directly with curl -I ``` If the new store works but `pywla5knjbnow7ji.public.blob.vercel-storage.com` still returns 503 for every object, that strongly suggests the old store’s public serving layer is stuck or unavailable. If the new store also returns 503, then I’d check whether the team/project is paused, blocked, or over a Blob usage limit, because that would affect serving even if the token can still perform some API operations. The useful escalation summary would be: ``` Store ID: pywla5knjbnow7ji Blob API list/upload: 200 Public blob URL: 503 SERVICE_UNAVAILABLE Affects all blobs, old and new Tested from multiple networks Latest X-Vercel-Id: Latest timestamp: New public Blob store test result: Team/project paused or usage-limit banner: yes/no ``` Do not post the `BLOB_READ_WRITE_TOKEN`, but the public blob URL, `X-Vercel-Id`, and timestamp are safe and useful for Vercel to correlate.

Anshuman Bhardwaj Hi @thederpywhale-hotmai, welcome to the Vercel Community! By default, the blob stores don't have any `robots.txt`. The URL you shared is from v0, which has the `robots.txt` limitation. To solve this issue, I'd suggest you to create a **Blob integration** from your v0 chat and store the assets in that. This way, you'll not have to deal with` robots.txt`. I hope this was helpful.