A customer of ours 206.40.160.0/20 has been hit by the sprintlink filtering. This is just a datapoint.

I can see it from here. It also looks like (AS 114) Sesquinet is not CIDRizing very well. Humm - the /20 and all of its /24s and inconsistant origin AS as well. --asp@uunet.uu.net (Andrew Partan) Network Next Hop Metric LocPrf Weight Path *>i206.40.160.0 137.39.24.34 1 100 0 114 ? * 206.40.160.0/20 192.41.177.181 73 0 3561 114 i * i 198.32.136.12 69 100 0 3561 114 i *>i 137.39.24.34 100 0 114 3764 i *>i206.40.161.0 137.39.24.34 1 100 0 114 ? *>i206.40.162.0 137.39.24.34 1 100 0 114 ? *>i206.40.163.0 137.39.24.34 1 100 0 114 ? *>i206.40.164.0 137.39.24.34 1 100 0 114 ? *>i206.40.165.0 137.39.24.34 1 100 0 114 ? *>i206.40.166.0 137.39.24.34 1 100 0 114 ? *>i206.40.167.0 137.39.24.34 1 100 0 114 ? *>i206.40.168.0 137.39.24.34 1 100 0 114 ? *>i206.40.169.0 137.39.24.34 1 100 0 114 ? *>i206.40.170.0 137.39.24.34 1 100 0 114 ? *>i206.40.171.0 137.39.24.34 1 100 0 114 ? *>i206.40.172.0 137.39.24.34 1 100 0 114 ? *>i206.40.173.0 137.39.24.34 1 100 0 114 ? *>i206.40.174.0 137.39.24.34 1 100 0 114 ? *>i206.40.175.0 137.39.24.34 1 100 0 114 ?