CustomersREXE
REXE uses Proxynet for attack data collection and internet research
“Our business is protection. We do not want to deal with data collection infrastructure. In Proxynet we pick the country, the city and the session length, and the rest just works.”
Challenge
DDoS protection needs constantly fresh data. Attack-source IP lists, public blocklists, threat reports and industry data are collected from dozens of different sources. Most of these sources rate-limit requests from datacenter IPs or show different content by region.
Solution
The REXE team runs its data collection and testing through Proxynet. Multi-source scraping jobs and connectivity tests from different countries, cities and carriers go through the Residential proxy pool; long-running monitoring sessions are kept on ISP proxies.
Results
Attack-source IP data and blocklists are collected from different sources without interruption
Connectivity and availability tests are run from different countries, cities and carriers with real user IPs
Long-running monitoring sessions run on fixed IPs without dropping
All data collection jobs are managed from a single panel
About REXE
REXE Teknoloji provides DDoS-protected virtual servers, dedicated servers and hosting from its Tier 3 datacenter in Istanbul. What sets the company apart is its protection layer: it runs with 200 Gbps of local Path.net appliance capacity in Türkiye and can route traffic to Path.net's global scrubbing network when needed. A large share of its customers are game servers and high-traffic projects.
Protection runs on data
DDoS protection is not something you set up once and leave. Which sources attacks come from, which IP blocks are being abused and which attack types are on the rise keep changing. To keep that picture current, the REXE team collects data regularly: attack-source IP lists, public block and reputation lists, threat reports, and the announcements and prices of other providers in the industry.
Most of these sources rate-limit automated requests from datacenter IPs. Some show different content by region, and some cut off a single IP that sends frequent requests within minutes. The team kept hitting that wall in the collection jobs it ran from its own infrastructure.
"Collecting data with our own IPs created two problems: either the source cut us off, or we were burning our own blocks on this job," says the REXE team. "Data collection had to move to a separate infrastructure."
Proxynet's role
REXE runs its data collection and research through Proxynet.
The same infrastructure is also a test network for the team. By connecting to the protected systems from different countries, cities and carriers, latency and availability are measured from where the real user is. Much like services such as ipinfo look from different points, REXE can look at its own network from the outside with realistic traffic.
"Our business is protection. We do not want to deal with data collection infrastructure. In Proxynet we pick the country, the city and the session length, and the rest just works."
How the collected data is processed and how it feeds the protection rules is REXE's own method. Proxynet is only in the first link of that chain: getting the data reliably from its source.
Outcome
REXE's data collection now runs without tying up its own IP blocks, without being blocked by the sources, and from a single panel. Trusting the continuity of the collected data, the team focuses on the protection side.
"The proxy became an invisible layer for us. It causes no trouble, so we do not think about it. That is exactly what one infrastructure provider would ask of another."