Content Retrieval is too slow

I worked a lot with IPFS and tried out many of its features. I want to say that I am still in love with this network, because of its simplicity and its usability in so many contexts. However, it is sometimes an unhappy love! My main problem with the pride is content resolution. Any content that I add to a specific node, just takes way too long to be available “on the other end” of the public network.

I understand that this is a very hard problem to solve, even for the brightest developers. And I am sure there are very smart people working on this.

Please give me some good reasons for more optimism! Will it ever be solved/improved? How will it be solved? — Make IPFS quicker, please !!!


Which usecase do you have? Just two nodes you own? Then you can connect them together to speed this up.

You know that you can start your daemon with --enable-pubsub-experiment and use IPNS names, to speed the resolution up as well? :slight_smile:

I would like to use public ipfs gateways to serve my single page applications. So if I add the page to my node, there is too much delay until it is found by the gateways. So if my node is up and running, it would be absolutely fantastic if any public gateway could serve my page in no time.

Which public gateway do you use?

I think @lyrx is referring to the official ipfs gateway.

I’m not sure how the status of the gateway is considered in terms of performance. But at my location the Cloudflare gateway is better in terms of performance.

@lyrx do you use ipns with pubsub?

Edit: Just checked with a freshly generated CID, the Cloudflare gateway loads the page within 2 seconds.

I am not thinking about specific gateways. My usecase is cloudflare as a gateway and pinata for pinning – and my own node for adding. Anyway, if we had k nodes for pinning [P_1 … P_k] and m gateways [G_1 … G_m] If you randomly choose a gateway and a pinning node, than it should work even if all the other nodes were down. That would be real censorship resistance. m * k combinations would have to work for that, and that would be fantastic.

Also, if I used pubsub, maybe that would help me, I do not known enough about it. But if I would just like to be part of the swarm, then it would only help me if everybody had it. Look at a swarm of birds in the sky: There is no leader, but the information which direction to take propagates almost instantanously from one bird to the whole swarm. That would be exciting: Be a node and add any information, and in a minute it is available everywhere …

1 Like

Pubsub is basically direct communication, instead of talking thru the DHT, which is much faster.

You asked how you get the gateway access faster: That’s how.

And birds can’t propagate an information world wide in real time either :wink:

Maybe this can help:

Maybe @obo20 can help you out more on this :slight_smile:

UPDATE: As you don’t own the nodes at Pinata & Cloudflare, you can setup a node yourself and connect it to the nodes at pinata & Cloudflare. This would ensure atleast 2nd degree connection, if not 1st.

Hi, you give me valuable information, thanks! Sorry to ask for even more: I think I would need the ipfs multiaddresses for the cloudflare/ipfs gateways, and then I could connect my own node with them.

For the pubsub thingy: How to use pubsub and ipns to speed up content publication to gateways: Is there any doc out there that could be linked related to this?

EDIT: I found this:


I think I would need the ipfs multiaddresses for the cloudflare/ipfs gateways, and then I could connect my own node with them.

You may need to contact them. I’m not sure if they(cloudflare guys) will be in for this.

@lyrx Let us know if you are still stuck.

You don’t have to excuse. This board is meant to be used for discussions and exchange of knowledge.

Feel free to extend the currently available information on the docs if you think they are not clear enough, or there are gaps.

This webpage is available via CloudFlares gateway and stored on three nodes by the author on IPFS.

It’s pretty fast.

The author explains in a linked howto how he set up this webpage.

Best regards


1 Like

Very well! For me this P2P stuff is not only about technology, it is also social – social learning. I paid some money to have my own IPFS node on a hosting platform, and I even started my own private dedicated IPFS network, because I thought it could be a good idea. It wasn’t! I learned that P2P is about sharing and participating. That is why I am back in the public IPFS network, and I want to have my node on each of my hardware pieces, and maybe have other people who share my data on their nodes. There are still problems: NAT, latency and others, but they seem to be on the decline, these problems! I think that cloudflare does a good job with their IPFS integration, and it might be a beginning only …

I already took over one charity site from some people, and I think I can save them mire than a 100 dollars a year for hosting, because I have put it on IPFS+cloudflare. Underprivileged might soon be able to share their content, because it is much cheaper to do so (less hosting costs), and it might be censorship resistent !!


Rest assure there are a lot of efforts being put into making content resolution great again, with many things in progress at the moment, and many others in testing. These should start landing in a few weeks.

Regarding gateways, here are a few you can connect to (but they will rather aggressively prune your connections from their side):


Did you try a pinning service?

I use pinata as a pinning service, and it works very well.

I also tried out the list hector sent to me. Thanks! – You know, there are a lot of aspects in this, and I am not a real expert. But I just feel that this can really become great if nothing depends on a single node (or on a list of nodes). So for example today I have trouble with the cloudflare IPFS gateway that is inside my DNS configuration. So my websites do depend on this specific gateway, and today this gateway is just having a bad day. But my content is on IPFS, so the whole configuration should be more resilient, and it isnt. There should be no reason to configure specific IPFS nodes anywhere.