Is Pinboard.in Down Again?
3 comments
I have noticed the problem on a few different days this week including right now (Oct 24 @ 14:25 EST).
From what I see, the issue is the API url (https://api.pinboard.in) timing out.
The web interface seems working, albeit a bit slow.
From what I see, the issue is the API url (https://api.pinboard.in) timing out.
The web interface seems working, albeit a bit slow.
I don't use Pinboard, but I was able to open the website in my browser without any issues. Both https and http seem to work fine.
Thanks very much!
As an experiment I turned off the WiFi on my phone and tried accessing the site through the mobile network and... you are correct, it is up and running!
So judging from the tracert I think packet routing is failing when it tries to leave England and go to the US!
I think my fibre broadband company needs to get a new Visa!
As an experiment I turned off the WiFi on my phone and tried accessing the site through the mobile network and... you are correct, it is up and running!
So judging from the tracert I think packet routing is failing when it tries to leave England and go to the US!
I think my fibre broadband company needs to get a new Visa!
I see this question has been asked before and usually the outages are a few hours so it is worrying that this one is so long. I also see that the single owner has a record of not maintaining the site and seems to prefer writing comments on X. I joined pinboard some 10 years ago having jumped ship from the doomed Delicious service. I have had no major problems in all that time which makes me sad that I may have to leave again. I'm hoping it comes back briefly so I can update my backups. Failing that I may have to hack the Android app to extract them from that.
Interestingly all the downdetector web sites say it is up and running for them. I think this is because they simply check for a connection and don't care if they ever get a 200 response code. I found the IP address of the domain and noticed that a ping fails completely to connect whereas if I simulate a web browser using the wget command to port 80 or 443 it connects but never gets a response.
Anyhoo it would be nice to know I'm not the only person in the world who noticed!