Is anyone else seeing this.
I work for a large web hosting company and for the last week we have
customers in Europe and Saudi Arabia that cannot contact any of our sites
every time we trace back to there IP we hang in new york at multiple backbone
providers.
TIA for any thing you can provide.
Hope this makes more sence. 
Are seeing traffic from the Saudi Arabinan Caching servers on our netowork
from ips
212.138.47.4,5,11,12,13
But we cannot trace back to them from our site.
Example traceroute.
traceroute 212.138.47.4
traceroute: Warning: Multiple interfaces found; using 66.34.21.243 @ eth0
traceroute to 212.138.47.4 (212.138.47.4), 30 hops max, 40 byte packets
1 66.34.0.1 (66.34.0.1) 0.950 ms 0.607 ms 1.609 ms
2 gi5.border.propagation.net (66.34.255.1) 2.826 ms 1.092 ms 1.406 ms
3 63.145.32.189 (63.145.32.189) 12.513 ms 14.012 ms 18.513 ms
4 * dal-core-02.inet.qwest.net (205.171.25.57) 10.655 ms 11.819 ms
5 kcm-core-02.inet.qwest.net (205.171.5.201) 28.435 ms 29.907 ms 27.385
ms
6 kcm-core-01.inet.qwest.net (205.171.29.125) 18.600 ms 21.844 ms 29.581
ms 7 chi-core-03.inet.qwest.net (205.171.5.209) 33.321 ms 30.337 ms
28.903 ms
8 chi-brdr-03.inet.qwest.net (205.171.20.142) 31.054 ms 34.613 ms 39.370
ms 9 205.171.1.70 (205.171.1.70) 52.122 ms 51.513 ms 54.461 ms
10 if-0-0.core1.NewYork.Teleglobe.net (64.86.83.210) 54.067 ms 50.172 ms
49.008 ms
11 * * *
12 * * *
13 ix-1-14.core1.NewYork.Teleglobe.net (207.45.196.150) 223.212 ms !X * *
14 ix-1-14.core1.NewYork.Teleglobe.net (207.45.196.150) 221.470 ms !X *
228.179 ms !X
this one happened to stop at Teleglobe others stop in alter.net's network.
Hope this makes more sence. 
Are seeing traffic from the Saudi Arabinan Caching servers on our netowork
from ips
212.138.47.4,5,11,12,13
But we cannot trace back to them from our site.
Example traceroute.
traceroute 212.138.47.4
traceroute: Warning: Multiple interfaces found; using 66.34.21.243 @ eth0
traceroute to 212.138.47.4 (212.138.47.4), 30 hops max, 40 byte packets
1 66.34.0.1 (66.34.0.1) 0.950 ms 0.607 ms 1.609 ms
2 gi5.border.propagation.net (66.34.255.1) 2.826 ms 1.092 ms 1.406 ms
3 63.145.32.189 (63.145.32.189) 12.513 ms 14.012 ms 18.513 ms
4 * dal-core-02.inet.qwest.net (205.171.25.57) 10.655 ms 11.819 ms
Uh, check your upstream instead of looking at the endpoint. I hope that
makes sense.