Anyone seeing issues in the Sprint Network?

We’re seeing a routing loop at “” ( for traffic destined for sourced from several different locales.

Was curious if anyone else was seeing this?

–D. Campbell MacInnes

Dare I ask what part of this made you think that this was a Sprint problem
and not Yahoo's side of a Sprint transit demarc, most likely with a
default route kicking things back to the Sprint transit interface? Or what
made you think that this needed to go to NANOG?