Try running a tracert in command prompt window and see what you get. I’m on the east coast with a 1G line and patches usually take about 20-30 minutes, but even today I see that at times it bounces against the wall during a trace, mainly once it gets to microsoft. My understanding from other posts is this is the IP, I can’t say for certain it is.
Tracing route to 13.107.246.10 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms 96.120.80.197
3 8 ms 7 ms 8 ms 24.124.162.145
4 18 ms 19 ms 24 ms ae-33-ar02.charlvilleco.va.richmond.comcast.net [68.86.173.93]
5 19 ms 18 ms 18 ms be-31542-cs04.ashburn.va.ibone.comcast.net [96.110.42.141]
6 17 ms 18 ms 18 ms be-2407-pe07.ashburn.va.ibone.comcast.net [96.110.32.198]
7 18 ms 17 ms 19 ms 66.208.229.218
8 19 ms 18 ms 17 ms ae34-0.icr01.bl7.ntwk.msn.net [104.44.233.18]
9 19 ms 17 ms 23 ms ae20-0.bl2-96c-1a.ntwk.msn.net [104.44.237.24]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 18 ms 20 ms 18 ms 13.107.246.10
Trace complete.