The lower latency ~7ms to any datacenter in KC, and knowing that all your traffic is not even leaving the area when you go to these places. Also it means lower latency over all. I get on avg. 30ms lower latency with Surewest than I did with TWC as they route all traffic to Chicago before being handed off.
Tracing route to 1and1.com [74.208.4.12]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 4 ms 5 ms 5 ms 64-126-2-213.static.everestkc.net[64.126.2.213]
4 5 ms 7 ms 5 ms 64-126-2-5.static.everestkc.net [64.126.2.5]
5 5 ms 5 ms 5 ms 64-126-2-14.static.everestkc.net [64.126.2.14]
6 6 ms 7 ms 6 ms te-4-2.car1.KansasCity1.Level3.net [4.53.32.33]
7 6 ms 11 ms 5 ms 11-INTERNET.car1.KansasCity1.Level3.net [4.53.32.10]
8 6 ms 7 ms 7 ms te-2-2.bb-d.slr.lxa.us.oneandone.net [74.208.1.77]
9 27 ms 7 ms 9 ms ae-2.gw-dists-a.slr.lxa.us.oneandone.net [74.208.1.115]
10 7 ms 7 ms 7 ms www.1and1.com [74.208.4.12]
Trace complete.
Tracing route to joesdatacenter.com [96.43.134.146]
over a maximum of 30 hops:
1 <1 ms * <1 ms 192.168.0.1
2 * * * Request timed out.
3 6 ms 6 ms 6 ms 64-126-2-213.static.everestkc.net [64.126.2.213]
4 187 ms 102 ms 6 ms 64-126-2-5.static.everestkc.net [64.126.2.5]
5 10 ms 6 ms 6 ms 64-126-2-22.static.everestkc.net [64.126.2.22]
6 6 ms 7 ms 7 ms te0-0-0-4.ccr21.mci01.atlas.cogentco.com [38.104.86.101]
7 9 ms 7 ms 7 ms te0-2-0-0.mpd22.mci01.atlas.cogentco.com [154.54.30.158]
8 7 ms 7 ms 7 ms te2-1.mag02.mci01.atlas.cogentco.com [154.54.30.166]
9 7 ms 7 ms 9 ms 38.104.86.74
10 8 ms 9 ms 13 ms SW1.KCMODATACENTER.COM [96.43.134.6]
11 7 ms 7 ms 7 ms 96.43.134.146
Trace complete.