Skip to main content

Bandwidth usage

Filebase tracks outbound data transfer, also called egress. For IPFS storage, the bandwidth chart breaks usage into categories that map to the different ways IPFS content can leave Filebase.

Uploads to Filebase are inbound transfer and do not count as bandwidth usage.

warning

IPFS bandwidth is not free. The free-egress benefit applies only to S3-compatible object storage buckets on the non-IPFS tier at s3.filebase.io.

IPFS bandwidth categories

S3

Data downloaded through the IPFS S3-compatible endpoint at s3.filebase.com. This includes GetObject responses, multipart download reads, and other object reads from IPFS buckets.

Gateway

Data served through your dedicated IPFS gateways. Each time a user or application fetches content through a dedicated gateway URL, the response size counts toward this category.

Public GW

Data served through the shared Filebase public IPFS gateway:

https://ipfs.filebase.io/ipfs/{CID}

The public gateway is intended for testing and light usage. For production traffic, use a dedicated gateway.

Bitswap

Data transferred to other IPFS peers through the Bitswap protocol. When external IPFS nodes request blocks of content pinned to your Filebase account, the outbound transfer counts toward this category.

Trustless

Data served through the IPFS Trustless Gateway protocol. Trustless gateway responses are content-addressed and verifiable, so clients can validate that the returned blocks match the requested CID.

RPC

Data returned by IPFS RPC API calls. This covers response data from Filebase's Kubo-compatible RPC endpoints.

Sites

Data served from Filebase Sites. When visitors load a site published through Filebase Sites, page and asset responses count toward this category.

How usage is counted

All IPFS bandwidth categories are added to your account's total outbound bandwidth usage. IPFS outbound transfer is billable, including bandwidth served through IPFS gateways, Bitswap, trustless gateway responses, RPC responses, and Filebase Sites.

Bandwidth counters update on a rolling basis, typically within a few minutes of a request completing.

What's next