>>> Seems to be only source-prefix-based, but several ISPs in europe are >>> affected. > source: 131.220.0.0/16, 212.201.68.0/22, 212.201.72.0/21, > destination: 65.122.178.73, 63.228.223.104 > traceroute to 65.122.178.73 (65.122.178.73), 30 hops max, 40 byte packets > 1 er-rz-gig-3-3.stw-bonn.de (131.220.99.62) 1.792 ms 1.275 ms 1.125 ms > 2 xr-bon1-te2-3.x-win.dfn.de (188.1.233.193) 0.705 ms 2.132 ms 0.755 ms > 3 xr-bir1-te2-3.x-win.dfn.de (188.1.144.9) 1.477 ms 1.936 ms 1.051 ms > 4 zr-fra1-te0-7-0-5.x-win.dfn.de (188.1.145.46) 4.034 ms 3.734 ms 4.957 > ms > 5 64.213.78.237 (64.213.78.237) 3.866 ms 3.295 ms 26.854 ms > 6 jfk-brdr-04.inet.qwest.net (63.146.26.225) 119.511 ms 92.735 ms > 99.019 ms
Based on all that, it looks like Qwest is not propogating your routes within their network. I was going to recommend route-views, but it might not reflect that now if you have dropped GBLX. Historical routing updates will show though if Qwest were advertising reachability to you (which would be a good indicator if they were filtering at their edge)
