Read on Twitter
So let's explain how a recently updated app could bring down RD 3 days in a row
This app is parsing the web for compatible links from filelockers
Instead of checking these files on its own it is using our API to generate the link, not checking it only ...
This app is parsing the web for compatible links from filelockers
Instead of checking these files on its own it is using our API to generate the link, not checking it only ...
so even if you have no intention to download/stream the concerned files you will have the link inside your downloads history.
Every single link is generated and the list can be big, instead of checking these links one by one the app is sending dozens of simultaneous requests
Every single link is generated and the list can be big, instead of checking these links one by one the app is sending dozens of simultaneous requests
(the entire list, so you can send 100req/s if the list has 100 links)
Some of these filelockers are quite small, they can be slow or even temporarily down and stall your request to our API because we have to wait for the original host to answer.
Some of these filelockers are quite small, they can be slow or even temporarily down and stall your request to our API because we have to wait for the original host to answer.
That's how RD went from dozens of simultaneous requests to thousands ( peak at 40.000 req/s )
Hardware capacity is not unlimited ...
We are still working on limiting this behavior to keep our services running for everybody without impacting a normal behavior.
Hardware capacity is not unlimited ...
We are still working on limiting this behavior to keep our services running for everybody without impacting a normal behavior.
The concerning developers clearly have no knowledge on how to create an app, they created a DDoS botnet instead.
