IPFS Foundation
ipfs.tech · 2 records in Storage · JSON
Records 2
- fails: egressIPFS Foundation public gateways (ipfs.io / dweb.link / trustless-gateway.link)
Storagefree tieridentity email?card?evidence reportedstale on 2026-11-05
- self-hosted, last resortSelf-hosted Kubo/Rainbow gateway (own VPS)
Storageverdict fails-egressfree tieridentity email?card?limit per-ip-shapingevidence reportedstale on 2026-11-05
- Free allowance
- No storage at all — gateway only.
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported4 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | No storage at all — gateway only. And the gateway itself is being retired: ipfs.io/dweb.link return HTTP 429 with 'Retry-After: 900' and 'Sunset: Mon, 21 Sep 2026', and redirect browsers to inbrowser.link. unit mixed; metered on stored-bytes |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | Rate-limited to the point of unusability from a datacenter IP: 10/10 requests returned 429 on a cold burst, and a single request after a 5 s pause also returned 429. Published posture: 'Rate limiting has begun on ipfs.io and dweb.link for hotlinked and backend traffic, and will be increasing.' Docs: 'no SLA, no support, and shared rate limits that can throttle or block your traffic at any time, without notice.' |
| Per-object cap | not stated |
| Retention | not stated |
| Interface | rest rest |
| Tooling | curl/any HTTP client; path gateway at ipfs.io, subdomain at dweb.link; trustless subset at trustless-gateway.link. |
| Composes with | none. The three hostnames are one backend: 'They are not three separate services... sharing the same cache, the same connections to the IPFS network, and the same rate limits.' Rotating hostnames burns the same budget. |
| Reliability | This is the single most important measurement in the slot: the 'free IPFS CDN' that every tutorial assumes is (a) gone as of 2026-09-21 and (b) already 429-ing datacenter IPs before that date. Any architecture that depends on ipfs.io/dweb.link for serving is dead on arrival. |
| Parsed numbers |
|
Evidence 4
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | ipfs.io/ipfs/bafybei...5u4 | probe: GET -> HTTP/1.1 429, Retry-After: 900, Link: rel="sunset", Sunset: Mon, 21 Sep 2026; 10/10 subsequent requests 429 |
| 2026-10-21 | dweb.link/ipfs/bafybei...5u4 | probe: GET -> 429, Retry-After: 900 (identical body, 188 bytes) |
| 2026-10-21 | blog.ipfs.tech/2026-08-beyond-sponsored-gateways/ | (2026-08-25) — 'Rate limiting has begun on ipfs.io and dweb.link for hotlinked and backend traffic, and will be increasing.' |
| 2026-10-21 | gatewaychanges.ipfs.io/ | 'these pauses keep growing until it retires for good on September 21 (UTC)' |
More fields 1
| dead end | {"failure_class": "dead-service","why": "No storage at all — gateway only. And the gateway itself is being retired: ipfs.io/dweb.link return HTTP 429 with 'Retry-After: 900' and 'Sunset: Mon, 21 Sep 2026', and redirect browsers to inbrowser.link.","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 4
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read
- Free allowance
- Storage and egress are whatever your VPS/host allows.
- Verdict
- self-hosted, last resortverdict fails-egress: data cannot be read back out at a usable rate or price. Self-hosted options are listed last, because this site is for users who have no hardware.
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-ip-shaping1 TiB/day
- Evidence
- reported2 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Storage and egress are whatever your VPS/host allows. No provider quota exists — the cost moves to the host's bandwidth allowance. unit mixed; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits |
Bandwidth of the VPS; DHT lookup latency on cold CIDs; no excess-use protection by default ('Unlike ipfs.io, a self-hosted gateway has no abuse protection by default'). |
| Identity | email (placeholder) not published |
| Egress | You pay the host. IPFS docs recommend putting a CDN like Cloudflare in front of the gateway and setting Cache-Control/ETag/X-Ipfs-Roots for cacheability — which is the one genuinely correct architectural move, but it is Cloudflare's free egress you are relying on, not IPFS's. |
| Per-object cap | not stated |
| Retention | not stated |
| Interface | rest, webdav, rclone rest |
| Tooling | Kubo (go-ipfs), Rainbow (github.com/ipfs/rainbow), Someguy for delegated routing, Helia in-browser; rclone can talk to the Kubo RPC API via a webdav/MFS shim but there is no first-class rclone backend. |
| Composes with | Does not multiply free storage — it only re-serves content you already paid to pin. Combined with a free pinning service it can turn 5 GB of free pinning into unmetered-looking reads, but only for 5 GB of content. |
| Reliability | This is the honest answer to 'does self-hosting change the economics?': it changes who meters you, not whether you are metered. It just moves the bill to the VPS or CDN. |
| Parsed numbers |
|
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | docs.ipfs.tech/how-to/replace-public-gateways-with-self-host | 'Put a CDN like Cloudflare in front of the IPFS gateway'; 'a self-hosted gateway has no abuse protection by default' (the vendor means it applies no excess-use protection) |
| 2026-10-21 | docs.ipfs.tech/how-to/gateway-best-practices/ | 'Ensure that you are correctly returning HTTP cache headers... Consider leveraging the list of CIDs in X-Ipfs-Roots' |
More fields 1
| dead end | {"failure_class": "egress","why": "Storage and egress are whatever your VPS/host allows. No provider quota exists — the cost moves to the host's bandwidth allowance.","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 4
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read