Anyone noticing poor routing to/from Softlayer’s network, specific to Dallas, Texas from remote locations?

Seeing things like this from Kansas City to Softlayer in Dallas:
4 10gigabitethernet1-3.core1.mci2.he.net (216.66.78.89) 0.372 ms 0.442 ms 0.500 ms
5 10gigabitethernet1-4.core1.mci1.he.net (184.105.213.1) 0.457 ms 0.525 ms 0.576 ms
6 10gigabitethernet6-1.core1.chi1.he.net (72.52.92.1) 19.267 ms 19.260 ms 19.222 ms
7 te1-7.bbr01.eq01.chi01.networklayer.com (206.223.119.63) 11.417 ms 11.538 ms 11.528 ms
8 ae7.bbr02.eq01.chi01.networklayer.com (173.192.18.171) 11.581 ms 11.536 ms 11.518 ms
9 ae1.bbr02.cf01.den01.networklayer.com (173.192.18.131) 27.835 ms 27.970 ms 26.837 ms
10 ae7.bbr01.cf01.den01.networklayer.com (173.192.18.168) 26.904 ms 27.710 ms 27.565 ms
11 ae12.bbr02.eq01.dal03.networklayer.com (173.192.18.138) 134.504 ms 134.788 ms 134.781 ms
12 ae1.dar01.sr01.dal01.networklayer.com (173.192.18.255) 134.788 ms ae0.dar02.sr01.dal01.networklayer.com (173.192.18.213) 134.445 ms ae1.dar01.sr01.dal01.networklayer.com (173.192.18.255) 144.685 ms

64 bytes from www.softlayer.com (66.228.118.51): icmp_req=1 ttl=245 time=137 ms
64 bytes from www.softlayer.com (66.228.118.51): icmp_req=2 ttl=245 time=130 ms
64 bytes from www.softlayer.com (66.228.118.51): icmp_req=3 ttl=245 time=132 ms
64 bytes from www.softlayer.com (66.228.118.51): icmp_req=4 ttl=245 time=136 ms
64 bytes from www.softlayer.com (66.228.118.51): icmp_req=5 ttl=245 time=130 ms

From Denver, Colorado on FDCServer’s network, earlier was seeing:
Denver to Chicago to Denver to Dallas

Times/latency was inflated as a result.

Seeing lots of this route to Softlayer Dallas that goes Chicago, Denver then Dallas. Don’t understand that route at all since Softlayer has facility in Dallas and POP in Chicago. Everyone seems to have direct connect from Dallas to Chicago.

Anyone aware of anything ongoing with Softlayer that might be causing these odd routes?

For more information click here.