We've been seeing a lot of customers call in with reports of slow access to their servers in the US. Traceroutes back to them all yield round-trip times of 300ms once the connection gets across the ocean. Anyone have any leads on a root cause? 4. 12.87.122.245 0% 9 9 9 9 10 11 5. cr2.hs1tx.ip.att.net 0% 9 9 46 46 46 46 6. cr1.dlstx.ip.att.net 0% 9 9 47 46 47 47 7. cr2.dlstx.ip.att.net 0% 9 9 47 46 47 47 8. cr2.la2ca.ip.att.net 0% 9 9 46 45 46 46 9. gar4.lsrca.ip.att.net 0% 9 9 47 47 47 48 10. 12.86.240.10 0% 9 9 46 45 46 49 11. segment-124-7.sify.net 0% 8 9 269 268 269 269 12. segment-119-227.sify.net 0% 8 9 268 267 268 271 13. segment-119-227.sify.net 0% 8 8 269 267 268 271 14. segment-119-227.sify.net 0% 8 8 270 269 271 274 15. segment-119-227.sify.net 0% 8 8 270 268 270 276 16. segment-119-227.sify.net 0% 8 8 271 269 270 271 17. 210.18.13.233.sify.net 0% 8 8 268 268 268 269 18. segment-124-30.sify.net 0% 8 8 294 284 292 299 4. 12.87.122.245 0% 11 11 10 9 10 11 5. cr2.hs1tx.ip.att.net 0% 11 11 16 16 16 17 6. cr1.dlstx.ip.att.net 0% 11 11 16 16 16 17 7. ggr7.dlstx.ip.att.net 0% 11 11 170 15 56 170 8. 192.205.36.42 0% 11 11 15 15 22 75 9. customer-side-bharti-4-pal6.pal.seabone.net 0% 10 11 286 286 287 287 10. 125.21.167.114 0% 10 10 285 285 285 285 11. 61.95.240.130 0% 10 10 283 283 283 286 12. abts-tn-static-248.253.246.61.airtelbroadband.in 0% 10 10 290 287 290 294