On Windows XP Pro with IE 8 (accessing from North Carolina) it seems to be instantious and fast as ever, if not faster. This XP Pro is in a virtual box within Windows 7.

>My perception of UT responsiveness is it's slower than before your recent change of ISP.
>
>Before the change response was almost always very snappy, and in some cases so fast I wasn't sure the new page had loaded until I looked at it and saw the content was different.
>
>Right now (and IIRC most of the time since the change), I'm seeing page load times of roughly 0.25 - 0.50 seconds. This is still very acceptable but not as snappy as before. I just thought I'd bring this to your attention, especially if one of the reasons for the change was to get better performance/responsiveness.
>
>Browser is FireFox 20.0.1.
>
>Here is a tracert (ISTR there used to be more hops, only 13 now seems pretty good).
>

Tracing route to levelextreme.com [198.72.113.6]
>over a maximum of 30 hops:
>
>  1    <1 ms     1 ms     1 ms  XXXXXX [192.168.1.1] 
>  2     *        *        *     Request timed out.
>  3    13 ms    15 ms    24 ms  tl2ca.vc.shawcable.net [64.59.148.141] 
>  4    13 ms    24 ms    23 ms  66.163.68.241 
>  5    16 ms    15 ms    31 ms  66.163.68.149 
>  6    16 ms    16 ms    15 ms  rc1wt-pos4-0-0.wa.shawcable.net [66.163.76.126] 
>  7    15 ms    12 ms    13 ms  ix-0-0-2-0.tcore1.00S-Seattle.as6453.net [64.86.123.29] 
>  8    15 ms    17 ms    14 ms  if-13-0-0-4.core1.00S-Seattle.as6453.net [64.86.124.13] 
>  9    95 ms    79 ms    95 ms  if-4-1-0-0.tcore2.CT8-Chicago.as6453.net [64.86.124.10] 
> 10    77 ms    79 ms    82 ms  if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45] 
> 11    99 ms    87 ms    86 ms  66.198.96.58 
> 12   107 ms    94 ms    97 ms  te7-4.dr9.mtl.iweb.com [184.107.1.110] 
> 13    97 ms   104 ms    97 ms  198.72.113.6 
>
>Trace complete
>