public-gateway-checker
public-gateway-checker copied to clipboard
ipfs
Test and report public writeable status
Would be a nice attribute to add! So if a gateway is actually online, try writing some content as well to see if it's writable and report back status. Would love to see a PR for adding this :)
@victorb I created a similar tool that makes this, measure gateway latency, status code, etc, you can check it out here https://gateway.ipfs.io/ipfs/QmXHzertynCrRi9A99JH1fbxLATtGCaU4L3gkLo6ov9JEW
@fooock that is amazing. It is weird that it is not considering siderus.io as writable. How do you perform the check?
@koalalorenzo I make a post request to the gateway domain plus :5001/api/v0/add. For example, in siderus.io, the final post request will be https://siderus.io:5001/api/v0/add, if this request return success, then the node is writable, otherwise isn't. Do you see it correct?
No it is not correct since :5001 is exposing API. By definition in the settings a writable gateway basically allows POST methods. You should be able to check just that, right?
@koalalorenzo it is fixed now, can you check it and write some feedback in the referenced issue if needed?
@fooock Looks pretty good!
I've found that based on my VPN current exit point I have significantly different latency values. Could you guys perhaps add separate latency columns for US, Europe and Asia for example? Or a dropdown at the top of the page to select the testing location?
I often timeout with the default ipfs.io gateway and it would be great to know what gateways are working fast from where I'm trying to access IPFS from.
Edit: Latency depending on the exit point while using ipfs.io to open an IPFS vs IPNS link: US Florida: 511 ms vs 1.02 mins Switzerland: 368 ms vs 1.01 mins Japan: 775 ms vs 1.02 mins
So my presumption was wrong, because it was not the VPN's exit point, but the IPNS lookup that timed out my queries. Sorry about that!
@andrasfuchs yeah IPNS is crazy slow
FWIW the gateway checker here: https://ipfs.github.io/public-gateway-checker/ -- runs the checks on your local computer. So those latencies are from your current location and setup (e.g. w/ VPN vs without)
This would be a nice add inside this repository too -- wonder if we could bundle requests more intelligently, so we're not just making 3 requests per server? That's not end of the world
Following up on some stale issues -- @fooock, are you interested in adding your writeable status feature into this repo's codebase?
Looks like the code for fooock's implementation is in Java: https://github.com/fooock/ipfs-gateway-checker/search?q=writable
we should implement this feature but in js
