#We have discontinued the publicly hosted version of RequestBin due to ongoing abuse that made it very difficult to keep the site up reliably. Please see instructions below for setting up your own self-hosted instance.
Originally Created by [Jeff Lindsay](http://progrium.com)
Thanks for providing this great service for such a long time!
Just curious, even captchas made it impossible to control abuse?
Would you consider accepting donations (via Patreon?) and/or make the site available again for users that would pay 1$ for a lifetime of use? (a minimal cost to weed out abuse)
All the best
P.S. Thanks for making it easy to deploy to Heroku as well -- just did and it was a single button click. Would still love to see this back up as a community service
A captcha does not solve the problem. The problem is that people continue to send traffic (sometimes in very large amounts) after they're done debugging and the bin is long gone. Over time, it's added up to a very large amount of 'zombie' traffic.
We tried running this as a commercial service (launched in 2013) but that wasn't financially feasible. It was only possible because we were 'subsidized' by VCs.
If someone decides to pick this up and run it publicly again, use DNS subdomains instead of paths. That way you can blackhole bins getting flooded.
Guys, if anyone is unable to create a private host for himself. Full contact has a public one for testing its API. use it without abuse please https://requestbin.fullcontact.com/
If someone decides to pick this up and run it publicly again, use DNS subdomains instead of paths. That way you can blackhole bins getting flooded.
I changed the code for this, then I stopped...
This also introduces other problems.. e.g. dns provider limits, so would probably require to roll your own dns.
With possible tens of thousands(?) of semi-permanent (block for a year?) blackholes.
Though it is the only way to be able to block incoming traffic, as such the only workable solution.
For those thinking about deploying a public service:
Require account creation, each account gets an own subdomain.. each subdomain gets /bins.
This just alleviates the number of blackholes. Blackhole per account, instead of per bin.
Still possible dns limits based on accounts
There is not really a workable public solution. Host your own ;-)
I did not know that RequestBin has really shut down, until one of the user of my service told me so yesterday. Then I find this discussion.
For last 6-8 months, I have been working on a similar service, Beeceptor, which is sub-domain based. It provides sub-domain based endpoints for creating Mock APIs and acts as proxy if someone have a real API endpoint. I would love to know feedback from you all.
Reading @johnsheehan's comment above, I realize that the same problem may occur for me, and DNS/blackhole/ip-firewall is a solution for long term. What other problems can occur in this domain that I should be aware of? Should I stop giving away free plans?
This comment has been minimized.
shaneqld repliedMar 21, 2018
RIP
This comment has been minimized.
pauledenburg repliedMar 21, 2018
Man, that's really sad. I loved the service! Will go and set-up a self-hosted version....
This comment has been minimized.
Clivern repliedMar 21, 2018
That is really sad😩
This comment has been minimized.
hakiemaul repliedMar 21, 2018
:(
This comment has been minimized.
jacktuck repliedMar 21, 2018
:(
This comment has been minimized.
gregsadetsky repliedMar 21, 2018
•
edited
Thanks for providing this great service for such a long time!
Just curious, even captchas made it impossible to control abuse?
Would you consider accepting donations (via Patreon?) and/or make the site available again for users that would pay 1$ for a lifetime of use? (a minimal cost to weed out abuse)
All the best
P.S. Thanks for making it easy to deploy to Heroku as well -- just did and it was a single button click. Would still love to see this back up as a community service
This comment has been minimized.
johnsheehan repliedMar 21, 2018
A captcha does not solve the problem. The problem is that people continue to send traffic (sometimes in very large amounts) after they're done debugging and the bin is long gone. Over time, it's added up to a very large amount of 'zombie' traffic.
We tried running this as a commercial service (launched in 2013) but that wasn't financially feasible. It was only possible because we were 'subsidized' by VCs.
If someone decides to pick this up and run it publicly again, use DNS subdomains instead of paths. That way you can blackhole bins getting flooded.
This comment has been minimized.
njmote repliedMar 21, 2018
This was super useful for the day I used it ;) Thanks again
This comment has been minimized.
temurih repliedMar 21, 2018
I just got to know about this service today, and its already been closed! I didn't get a chance to use it once.
This comment has been minimized.
colestrode repliedMar 22, 2018
Thanks for all your work on this project, I've used it for years and am sorry to see it go.
This comment has been minimized.
Technifocal repliedMar 22, 2018
RIP
This comment has been minimized.
JukieWalsh repliedMar 22, 2018
Thanks for maintaining this while you could, was a great service!
This comment has been minimized.
Clivern repliedMar 22, 2018
Guys, if anyone is unable to create a private host for himself. Full contact has a public one for testing its API. use it without abuse please https://requestbin.fullcontact.com/
This comment has been minimized.
mauroarcet repliedMar 22, 2018
:(
This comment has been minimized.
KarlaRobinson repliedMar 23, 2018
:( Hopefully there is a way to get it running again, but THANKS for the great service you offered!! We used you a lot
This comment has been minimized.
stevenscg repliedMar 26, 2018
RIP
This comment has been minimized.
AubreyHewes repliedMar 26, 2018
I host my own now and am grateful for the service that was provided, thanks to all!
This comment has been minimized.
AubreyHewes repliedMar 26, 2018
•
edited
@johnsheehan
I changed the code for this, then I stopped...
This also introduces other problems.. e.g. dns provider limits, so would probably require to roll your own dns.
With possible tens of thousands(?) of semi-permanent (block for a year?) blackholes.
Though it is the only way to be able to block incoming traffic, as such the only workable solution.
For those thinking about deploying a public service:
Require account creation, each account gets an own subdomain.. each subdomain gets /bins.
This just alleviates the number of blackholes. Blackhole per account, instead of per bin.
Still possible dns limits based on accounts
There is not really a workable public solution. Host your own ;-)
This comment has been minimized.
ankitjaininfo repliedApr 14, 2018
I did not know that RequestBin has really shut down, until one of the user of my service told me so yesterday. Then I find this discussion.
For last 6-8 months, I have been working on a similar service, Beeceptor, which is sub-domain based. It provides sub-domain based endpoints for creating Mock APIs and acts as proxy if someone have a real API endpoint. I would love to know feedback from you all.
Reading @johnsheehan's comment above, I realize that the same problem may occur for me, and DNS/blackhole/ip-firewall is a solution for long term. What other problems can occur in this domain that I should be aware of? Should I stop giving away free plans?