We’re seeing a routing loop at “sl-yahoo4-2-0.sprintlink.net” (144.223.36.174) for traffic destined for 64.115.0.0/22 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?