iroh
iroh.computer · 7 records in Egress and tunnels, Storage · JSON
Records 7
- caveatiroh public relays
Egress and tunnelsfree tieridentity anonymousno cardlimit per-ip-shapingevidence documentedstale on 2026-11-22
- caveatiroh public relays (n0.computer)
Storagefree tieridentity anonymousno cardlimit per-ip-shapingevidence reportedstale on 2026-11-05
- fails: egressiroh n0 public relays
Storageidentity email?card?evidence documentedstale on 2026-12-05
- fails: egressiroh Services — Community (free tier)
Storagefree tieridentity emailno cardevidence reportedstale on 2026-11-05
- fails: quotairoh Shared relay
Egress and tunnelsfree tieridentity emailno cardlimit volume-quotaevidence documentedstale on 2026-11-22
- fails: quotaipfs / shipyard
Storageidentity email?card?evidence reportedstale on 2026-11-05
- fails: quotan0 hosted blob pinning / storage service
Storageidentity email?card?evidence reportedstale on 2026-11-05
iroh public relays
Egress and tunnels- Free allowance
- Four public relay regions, no authentication, rate-limited per connection
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- per-ip-shapingper connection, value not published and retuned as needed
- Evidence
- documented1 source; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-22checked 2026-10-22 (live); stale on 2026-11-22
| Free tier | four public relay regions, no authentication, rate-limited per connection unit unlimited; metered on downloaded-bytes |
|---|---|
| Price | none stated |
| Limits |
|
| Identity | anonymous no authentication on the public relays |
| Egress | no byte quota; a per-connection rate limit that is retuned |
| Per-object cap | not applicable: a stream |
| Interface | unknown the n0 public relay preset, spoken over QUIC |
| Tooling | iroh |
| Composes with | a zero-cost relay for the connections that fail to hole-punch, which makes it a redundancy layer rather than a capacity layer. |
| Reliability | the documentation says not to rely on the public relays for production |
| Notes | A relay that transits bytes is metered by definition, and this one meters rate rather than volume. No number, so no capacity claim. |
| Parsed numbers |
|
Evidence 1
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | docs.iroh.computer/relays/rate-limiting | 'The exact rate limits aren't published today, as they get tuned as needed', plus the warning that public relays are not for production workloads |
More fields 3
| stale after days | 180 |
|---|---|
| bytes transit | yes |
| transit note | a relay that transits bytes when hole-punching fails, at a per-connection rate it does not publish |
Unknown values 1
- interface: the access interface was not established
- Free allowance
- No storage. Free, no account, no card.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- per-ip-shaping5 MB/s; 10,000 concurrent connections
- Evidence
- reported5 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. Free, no account, no card. Public relays are rate-limited per connection but the rate limits are deliberately unpublished. The paid Shared tier is the only one with published figures: 100 GB relayed egress/month then $0.09/GB, 5 MB/s, 10,000 concurrent connections. unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits | Not a storage provider. Only relayed bytes hit the operator, hence the per-connection rate limit rather than a byte quota. |
| Identity | anonymous anonymous |
| Egress | Free public relays, rate-limited. Self-hosting a relay is free and unlimited (open licence) — the cost moves to your own bandwidth. |
| Per-object cap | not stated |
| Retention | not stated |
| Interface | unknown QUIC over TLS 1.3; Rust crate iroh, bindings for other languages |
| Tooling | iroh crate; relay is a library, not a service with an upload endpoint |
| Composes with | This is SIGNALLING, not relaying, in the normal case: 'roughly 9 out of 10 connections go direct; the relay is only a fallback'. The relay carries bytes only when hole punching fails, which is what makes the free tier viable at all. |
| Reliability | 'The exact rate limits aren't published today, as they get tuned as needed' and 'Do not rely on it for production workloads' — the free tier is explicitly capacity-unstable by design. |
| Parsed numbers |
|
Evidence 5
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | docs.iroh.computer/about/faq | 'In practice, roughly 9 out of 10 connections go direct; the relay is only a fallback'; relays are stateless and cannot read traffic (QUIC/TLS 1.3) |
| 2026-10-21 | docs.iroh.computer/relays/rate-limiting | 'The exact rate limits aren't published today, as they get tuned as needed ... applied per connection'; 'Do not rely on it for production workloads' |
| 2026-10-21 | www.iroh.computer/pricing | Free: 'Rate limited' / 'Variable'; Pro $19/mo: 10,000 connections, shared relays, 5 MB/s; Dedicated $199/mo/region: unlimited |
| 2026-10-21 | docs.iroh.computer/iroh-services/relays/shared | '100 GB of relay egress per month, then $0.09/GB'; 'A 5 MB/s rate limit' |
| 2026-10-21 | www.iroh.computer/blog/shared-relays | worked example: 2,000 users x 10 GB/mo; 'if 98% of the traffic could travel directly ... only the remaining 2% (400 GB) would pass through' |
Unknown values 5
- interface: the access interface was not established
- 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
iroh n0 public relays
Storage- Free allowance
- Community plan, $0 per month: public relays in US, EU and Singapore, rate-limited traffic, no uptime guarantees, no auth; the rate limit is not published
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- documented16 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | Community plan, $0 per month: public relays in US, EU and Singapore, rate-limited traffic, no uptime guarantees, no auth; the rate limit is not published unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | Public relays are rate-limited per connection with no published limit; the pricing page lists egress and rate limit as 'Variable'. Paid routes: Pro $19/month has a 5 MB/s rate limit and 100 GB egress then $0.09/GB; Dedicated adds $199/month per region with no rate limits and 250 GB egress then $0.09/GB. |
| Interface | unknown |
| Tooling | not recorded |
| Reliability | Free public relays: rate-limited traffic with an unpublished limit, no uptime guarantees, development and hobby use only; no published limit supports 1 TiB a day. The paid Dedicated route has no rate limit and bills $0.09/GB beyond 250 GB. |
| Evidence note | documented documented from vendor pages read on 2026-11-03: the plan rates and egress (https://www.iroh.computer/pricing), and the rate limiting and hobby-use statements (https://docs.iroh.computer/iroh-services/relays/public and https://docs.iroh.computer/relays/rate-limiting). Identity, retention and per-object cap were not read. |
Evidence 16
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | docs.iroh.computer/relays/rate-limiting | Free tier is 'rate-limited traffic' with 'No uptime guarantees' and the exact limits are deliberately unpublished 'The exact rate limits aren't published today, as they get tuned as needed' |
| 2026-10-21 | www.iroh.computer/pricing | cited as the basis of the rejection: Free tier is 'rate-limited traffic' with 'No uptime guarantees' and the exact limits are deliberately unpublished 'The exact rate limits aren't published today, as they get tuned as needed' |
| 2026-10-21 | docs.iroh.computer/iroh-services/relays/public | cited as the basis of the rejection: Free tier is 'rate-limited traffic' with 'No uptime guarantees' and the exact limits are deliberately unpublished 'The exact rate limits aren't published today, as they get tuned as needed' |
| 2026-11-03 | www.iroh.computer/pricing | rate limit per plan: Variable on Community, 5 MB/s on Pro, Unlimited on Dedicated |
| 2026-11-03 | www.iroh.computer/pricing | egress per plan: Variable on Community, 100 GB then $0.09/GB on Pro, 250 GB then $0.09/GB on Dedicated |
| 2026-11-03 | docs.iroh.computer/iroh-services/relays/public | public relay traffic is rate-limited |
| 2026-11-03 | docs.iroh.computer/iroh-services/relays/public | public relays are for development and hobby use only |
| 2026-11-03 | docs.iroh.computer/relays/rate-limiting | dedicated relays have no rate limits |
| 2026-11-03 | docs.iroh.computer/relays/rate-limiting | the public relays' rate limit has no published number |
| 2026-11-03 | www.iroh.computer/pricing | the Community plan lists rate-limited traffic |
| 2026-11-03 | www.iroh.computer/pricing | the Community plan row of the public relays carries no egress price and no volume quota; the $0.09/GB figures are on Pro and Dedicated |
| 2026-11-03 | docs.iroh.computer/relays/rate-limiting | the public relays' limit is a per-connection throttle, not a volume quota or a price |
| 2026-11-03 | docs.iroh.computer/iroh-services/relays/public | the public relays have no price |
| 2026-11-04 | www.iroh.computer/pricing | rate limit per plan: Variable on Community, 5 MB/s on Pro, Unlimited on Dedicated |
| 2026-11-04 | docs.iroh.computer/relays/rate-limiting | the public relays' rate limit has no published number |
| 2026-11-04 | docs.iroh.computer/iroh-services/relays/public | public relays are for development and hobby use only |
More fields 1
| dead end | {"failure_class": "egress","why": "Free tier is 'rate-limited traffic' with 'No uptime guarantees' and the exact limits are deliberately unpublished ('The exact rate limits aren't published today, as they get tuned as needed'","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 6
- chaining: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field
- Free allowance
- 0 bytes of storage. Free plan = public relays in US/EU/Singapore, 7-day metrics retention, no auth, rate-limited traffic, no uptime guarantee.
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | 0 bytes of storage. Free plan = public relays in US/EU/Singapore, 7-day metrics retention, no auth, rate-limited traffic, no uptime guarantee. unit mixed; metered on stored-bytes |
|---|---|
| Price | none stated |
| Identity | email email |
| Egress | Variable / unpublished (inherits public relay limits). |
| Per-object cap | not stated |
| Retention | Free plan = public relays in US/EU/Singapore, 7-day metrics retention, no auth, rate-limited traffic, no uptime guarantee (7 days) |
| Interface | unknown Dashboard at services.iroh.computer + iroh-services crate; account is username + email + password. |
| Tooling | iroh_services::Client pushes endpoint metrics on an interval; net-diagnostics can dial back into your endpoint (requires granting Caps::net_diagnostics_get_any()). |
| Composes with | Free tier covers signalling and discovery for an unlimited number of endpoints — which is exactly the part a self-hosted origin needs. It contributes nothing to bytes at rest or bytes served. |
| Reliability | Free tier requires an account only to see metrics; the relays themselves need no account at all. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | www.iroh.computer/pricing | plan table: Free/Pro $19/Dedicated $199 per region/Enterprise; rows are Connections, Relays, Rate limit, Egress, Auth, Custom DNS, Metrics, Support. No storage row exists. |
| 2026-10-21 | www.iroh.computer/services/hosting | Public free / Cloud $19+ / Open Source self-host. 'Hosting' here means relays and discovery. |
| 2026-10-21 | services.iroh.computer/ | signup form is username + email + password (no card, no institution) |
More fields 1
| dead end | {"failure_class": "retention","why": "0 bytes of storage. Free plan = public relays in US/EU/Singapore, 7-day metrics retention, no auth, rate-limited traffic, no uptime guarantee.","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 4
- interface: the access interface was not established
- 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
ipfs / shipyard
Storage- Free allowance
- The IPFS pinning lane is closing, not opening — and free IPFS pinning was already excluded at <=6 GB in earlier waves. iroh's own blog frames Mainline+blake3.net as the successor, which is…
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- 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 | The IPFS pinning lane is closing, not opening — and free IPFS pinning was already excluded at <=6 GB in earlier waves. iroh's own blog frames Mainline+blake3.net as the successor, which is… unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | www.iroh.computer/blog/iroh-global-content-discovery | the text of Free tier, above |
| 2026-10-21 | www.iroh.computer/blog/iroh-global-content-discovery | the iroh post the record cites is the source of the name; the provider name keeps the service and drops a personal note |
More fields 1
| dead end | {"failure_class": "quota","why": "The IPFS pinning lane is closing, not opening — and free IPFS pinning was already excluded at <=6 GB in earlier waves. iroh's own blog frames Mainline+blake3.net as the successor, which is…","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field
- Free allowance
- Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest. Checked the pricing table, the hosting page, the services dashboard, the org's 100-repo… unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | www.iroh.computer/pricing | Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest. Checked the pricing table, the hosting page, the services dashboard, the org's 100-repo listing |
| 2026-10-21 | www.iroh.computer/services/hosting | cited as the basis of the rejection: Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest. Checked the pricing table, the hosting page, the services dashboard, the org's 100-repo listing |
| 2026-10-21 | docs.iroh.computer/iroh-services/relays/shared | cited as the basis of the rejection: Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest. Checked the pricing table, the hosting page, the services dashboard, the org's 100-repo listing |
More fields 1
| dead end | {"failure_class": "quota","why": "Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest. Checked the pricing table, the hosting page, the services dashboard, the org's 100-repo…","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field