Sprint midwest/NW backbone issues?

Anyone at sprint care to shed some light on a latency
issue that's been going on since December?

(While the SLA credits are always nice, there's
something to be said for actually getting the traffic
from A to B!)

sl-bb20-fw>ping 144.228.241.75

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 144.228.241.75,
timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip
min/avg/max = 84/115/172 ms
sl-bb20-fw>

... and Seattle to Dallas:
sl-bb20-sea>ping 144.228.241.51

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 144.228.241.51,
timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip
min/avg/max = 76/76/80 ms
sl-bb20-sea>