Random delays during TCP requests to https://graph.microsoft.com

Question

Hi,

Since 2026-06-04, we observe increased TCP-level "read: connection reset by peer" errors and intermittent 3s to 15+ seconds TCP connection establishment delays to https://graph.microsoft.com.

The issue affects high-volume Microsoft Graph workloads hosted on Azure virtual machines (affects platforms in EU, US, Asia, and Germany.)

We can also reproduce intermittent delay with unauthenticated curl requests to https://graph.microsoft.com on the same Azure VMs. Curl timing shows the delay is almost entirely in time_connect, before TLS and before any HTTP Graph response.

$ curl -sS -o /dev
/null       --resolve graph.microsoft.com:443:40.126.49.24       --connect-timeout 15       --max-time 20       -w "ip=40.126.49.24 dns=%{time_namelookup} tcp=%{time_connect} tls=%{time_appconnect} ttfb=%{time_starttransfe
r} total=%{time_total} http=%{http_version}\n"       https://graph.microsoft.com/

Testing 40.126.49.24
ip=40.126.49.24 dns=0.000014 tcp=6.681501 tls=6.742079 ttfb=6.743276 total=6.743304 http=1.1
ip=40.126.49.24 dns=0.000014 tcp=6.100271 tls=6.163114 ttfb=6.164218 total=6.164258 http=1.1
ip=40.126.49.24 dns=0.000014 tcp=11.148318 tls=11.221715 ttfb=11.222242 total=11.222273 http=1.1
ip=40.126.49.24 dns=0.000019 tcp=6.938742 tls=7.020327 ttfb=7.021407 total=7.021450 http=1.1
ip=40.126.49.24 dns=0.000014 tcp=3.041061 tls=3.102234 ttfb=3.103363 total=3.103396 http=1.1
ip=40.126.49.24 dns=0.000014 tcp=0.001829 tls=0.072355 ttfb=0.073550 total=0.073583 http=1.1
ip=40.126.49.24 dns=0.000014 tcp=0.950927 tls=1.019906 ttfb=1.020652 total=1.020689 http=1.1
ip=40.126.49.24 dns=0.000013 tcp=0.001796 tls=0.065331 ttfb=0.066442 total=0.066478 http=1.1
ip=40.126.49.24 dns=0.000017 tcp=0.847009 tls=0.926377 ttfb=0.927713 total=0.927741 http=1.1
ip=40.126.49.24 dns=0.000019 tcp=0.002050 tls=0.072033 ttfb=0.072528 total=0.072562 http=1.1
ip=40.126.49.24 dns=0.000018 tcp=0.009202 tls=0.080443 ttfb=0.081678 total=0.081712 http=1.1

Can you confirm whether there were changes around 2026-06-04 to Microsoft Graph front-door routing, service protection, throttling, abuse detection, or connection handling ?

Thanks