Actually, the return trip is having an issue.
traceroute 195.0.242.153
traceroute to 195.0.242.153 (195.0.242.153), 30 hops max, 40 byte packets
1 206.16.60.46 (206.16.60.46) 0.397 ms 0.318 ms 0.245 ms
2 mdf001c7613r0001-gig-12-2.dal1.attens.net (63.241.193.13) 0.296 ms 0.401 ms 0.288 ms
3 12.122.251.69 (12.122.251.69) 1.010 ms 12.122.251.65 (12.122.251.65) 1.048 ms 12.122.251.69 (12.122.251.69) 1.048 ms
4 cr2.dlstx.ip.att.net (12.122.138.2) 5.787 ms 2.275 ms 5.151 ms
5 gar27.dlstx.ip.att.net (12.123.16.77) 4.391 ms gar25.dlstx.ip.att.net (12.122.85.233) 3.950 ms 4.182 ms
6 192.205.34.146 (192.205.34.146) 1.765 ms 1.755 ms 1.730 ms
7 ventelo.tengigabitethernet7-4.ar1.osl2.gblx.net (67.17.198.250) 131.415 ms 131.497 ms 131.483 ms
8 te5-0-0.cr1.xa19.as2116.net (195.0.242.29) 131.718 ms 131.566 ms 131.847 ms
9 te4-1-0.cr1.fn3.as2116.net (193.75.3.150) 190.730 ms 191.564 ms 190.665 ms
10 te0-0-0-1.trondh-prinsg39-p2.as2116.net (195.0.242.94) 199.800 ms te0-0-0-0.trondh-prinsg39-p2.as2116.net (195.0.240.90) 201.779 ms 201.253 ms
11 te5-1-0.cr2.bo.as2116.net (193.75.3.41) 202.384 ms 206.874 ms 202.243 ms
12 te5-3-0.cr2.bo.as2116.net (195.0.242.153) 207.120 ms 206.943 ms 204.118 ms
Hope #10 is running around itself and another router (router flap). It can cause a lot of packet loss issues. Probably a temporary problem, but you might as your ISP about it. They could be doing some router and/or switch maintenance.
Hop #3 is showing the same thing, so I have sent in a trouble ticket to AT&T.
There is also a problem between Cogent and AT&T at their gateway on the trip to the servers.
By the way, any time you see packet loss at the last, or next to the last hop, it is always packet loss on the return trip.
