IPFS Gateways #

Please note that this website is a preview and is subject to change at any time. We strive to provide accurate and up-to-date information, but we cannot guarantee the completeness or reliability of the information presented during the preview.

An IPFS gateway is a web-based interface that allows users to access IPFS content using a regular web browser. The gateway acts as a bridge between the IPFS network and the traditional web, allowing users to browse and retrieve IPFS content without having to install any specialized software or run a full IPFS node.

When a user requests content through an IPFS gateway, the gateway retrieves the content from the IPFS network (through Bitswap and/or kubo) and delivers it to the user’s browser using standard web protocols such as HTTP or HTTPS. This allows users to access IPFS content in the same way they would access any other web content, with a simple URL or link. IPFS gateways are a key part of the IPFS ecosystem, as they make IPFS content accessible to a wider audience and help to bridge the gap between the traditional web and the decentralized web.

HTTP Requests to ipfs.io / dweb.link #

IPFS gateways can be run by anyone who has access to an IPFS node, and there are many public gateways available on the internet. The following measurements are made using data derived from the nginx access logs for ipfs.io and dweb.link, the gateway services operated by Protocol Labs.

In the following plots, requests are not deduplicated, i.e., if there are two requests for the same CID, they count as two requests and not one. This is what makes sense for requests. Deduplicating requests would effectively count the number of CIDs requested and not the requests themselves.

Daily HTTP Requests to ipfs.io / dweb.link #

Daily HTTP Requests to ipfs.io / dweb.link, by region #

Daily HTTP Requests to ipfs.io / dweb.link, by type #

Daily Unique Clients accessing ipfs.io / dweb.link #

In the following plot we aggregate the total number of unique client IP addresses that appear in the ipfs.io and dweb.link log files for each day.