Remi Hendriks

Remi Hendriks

Auto-generated profile, based on publicly available information

Remi Hendriks

Department of Design and Analysis of Computer Systems, University of Twente, Enschede, The Netherlands

Research Focus & Metrics

Academic Career Length

2Years (2025-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
28 October 2025
Verified
Conference Paper
Open access
RHRemi Hendriks
Remi Hendriks
MLMatthew Luckie
Matthew Luckie
MJMattijs Jonker
Mattijs Jonker
RSRaffaele Sommese
Raffaele Sommese
RRRoland van Rijswijk-Deij
Roland van Rijswijk-Deij

22 July 2025
Verified
Conference Paper
Open access
RHRemi Hendriks
Remi Hendriks
TBTim Betzer
Tim Betzer
BDBen Du
Ben Du
RSRaffaele Sommese
Raffaele Sommese
MJMattijs Jonker
Mattijs Jonker
RRRoland van Rijswijk-Deij
Roland van Rijswijk-Deij

25 November 2025 in IEEE Transactions on Network and Service Management
Verified
Journal Article
Closed access
RHRemi Hendriks
Remi Hendriks
MJMattijs Jonker
Mattijs Jonker
RRRoland van Rijswijk-Deij
Roland van Rijswijk-Deij
RSRaffaele Sommese
Raffaele Sommese
Load Balancing (LB) is a routing strategy that increases performance by distributing traffic over multiple outgoing paths. In this work, we introduce a novel methodology to detect the influence of LB on anycast routing, which can be used by operators to detect networks that experience anycast site flipping, where traffic from a single client reaches multiple anycast sites. We use our methodology to measure the effects of LB-behavior on anycast routing at a global scale, covering both IPv4 and IPv6. Our results show that LB-induced anycast site flipping is widespread. The results also show our method can detect LB implementations on the global Internet, including detection and classification of Points-of-Presence (PoP) and egress selection techniques deployed by hypergiants, cloud providers, and network operators. We observe LB-induced site flipping directs distinct flows to different anycast sites with significant latency inflation. In cases with two paths between an anycast instance and a load-balanced destination, we observe an average RTT difference of 30 ms with 8% of load-balanced destinations seeing RTT differences of over 100 ms. Being able to detect these cases can help anycast operators significantly improve their service for affected clients.