Purely a curiosity on my part… But has anyone ever looked at how their Microsoft Teams calls get routed? During Teams calls I’ll check OpenWrt to see the endpoint IP I’m sending all my traffic to, then do a traceroute to that IP. So far, I think, it’s always been a bizarre path.
For instance, today:
$ tracepath 52.115.76.111
1?: [LOCALHOST] pmtu 1500
1: OpenWrt.lan 1.200ms
1: OpenWrt.lan 1.511ms
2: ... 15.008ms
3: ... 18.429ms asymm 4
4: ... 22.477ms asymm 5
5: six2.microsoft.com 39.117ms asymm 6
6: ae32-0.icr02.mwh01.ntwk.msn.net 40.610ms
7: be-162-0.ibr04.mwh01.ntwk.msn.net 190.062ms asymm 15
8: be-2-0.ibr04.fra30.ntwk.msn.net 78.997ms asymm 12
9: be-8-0.ibr02.dsm05.ntwk.msn.net 77.944ms asymm 12
10: 51.10.19.124 78.474ms asymm 11
11: 104.44.54.110 75.460ms asymm 10
12: no reply
^C
I think that:
- mwh01 = Moses Lake, WA
- fra30 = Frankfurt
- dsm05 = Des Moines, Iowa
- ibr04 = ??
Assuming I’m right on those names - and the hostnames can be trusted - what a strange way to route traffic…
Most the time when I check these Teams IPs I’m just routing through Southern states before being sent back to the Eastern US, but today’s was weird enough I thought I should ask if anyone else ever looks at these things.
Were you talking with anyone in Europe, by any chance?
No, all within the province. I thought… that would be a funny way to out someone who is “working from home” in Europe.
Yeah, that would be a possibility.
Another thing could be that some of packets are routed out of the optimal path to avoid getting “stuck” in some local maxima? Just a guess, it’s been a while since I played with routing tables.