Hello, the loading times for help.devsense.com are atrocious, while all other subdomains seem to work fine.
A comparison with a traceroute:
6 * * * Request timed out.
7 32 ms 35 ms 36 ms ae22-0.amb-96cbe-1b.ntwk.msn.net [104.44.224.99]
8 187 ms 176 ms 172 ms be-62-0.ibr01.amb.ntwk.msn.net [104.44.9.134]
9 171 ms 169 ms 193 ms be-5-0.ibr01.lts.ntwk.msn.net [104.44.4.233]
10 171 ms 174 ms 178 ms be-2-0.ibr01.lon30.ntwk.msn.net [104.44.5.38]
11 184 ms 170 ms 183 ms be-1-0.ibr02.lon30.ntwk.msn.net [104.44.5.37]
12 185 ms 173 ms 173 ms be-12-0.ibr02.nyc30.ntwk.msn.net [104.44.5.106]
13 172 ms 173 ms 174 ms be-6-0.ibr02.was05.ntwk.msn.net [104.44.4.29]
14 179 ms 174 ms 172 ms be-5-0.ibr01.bn6.ntwk.msn.net [104.44.16.47]
15 177 ms 192 ms 182 ms be-4-0.ibr02.atb.ntwk.msn.net [104.44.16.42]
16 178 ms 169 ms 169 ms be-1-0.ibr01.atb.ntwk.msn.net [104.44.4.38]
17 174 ms 171 ms 173 ms be-6-0.ibr02.sn4.ntwk.msn.net [104.44.4.47]
18 189 ms 170 ms 177 ms be-1-0.ibr01.sn4.ntwk.msn.net [104.44.4.205]
19 177 ms 184 ms 181 ms be-3-0.ibr02.lax03.ntwk.msn.net [104.44.4.4]
20 169 ms 175 ms 182 ms be-1-0.ibr01.lax03.ntwk.msn.net [104.44.4.0]
21 173 ms 177 ms 173 ms be-4-0.ibr01.by2.ntwk.msn.net [104.44.4.3]
22 194 ms 177 ms 175 ms be-5-0.ibr03.by21.ntwk.msn.net [104.44.18.104]
23 171 ms 179 ms 184 ms ae123-0.icr02.by4.ntwk.msn.net [104.44.22.164]
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
and for other websites:
7 26 ms 19 ms 20 ms ae0-429.fra20.core-backbone.com [81.95.2.153]
8 31 ms 36 ms 36 ms ae1-2053.prg10.core-backbone.com [81.95.15.118]
9 41 ms 38 ms 44 ms core-backbone.superhosting.cz [80.255.14.50]
10 36 ms 31 ms 29 ms vl5.sit-ar-core1.superhosting.cz [88.86.96.210]
11 33 ms 34 ms 34 ms vl13.ttc-ar-klc1.superhosting.cz [88.86.96.89]
12 31 ms 33 ms 44 ms unn-95-168-195-180.superhosting.cz [95.168.195.180]
This is reproducable from multiple locations. Maybe something to inform your server host about. Appears to be an issue on microsofts end.