View Single Post
Old 02-10-2016, 09:34 AM   #11
rebl
r.eads e.njoys b.ooks lol
rebl ought to be getting tired of karma fortunes by now.rebl ought to be getting tired of karma fortunes by now.rebl ought to be getting tired of karma fortunes by now.rebl ought to be getting tired of karma fortunes by now.rebl ought to be getting tired of karma fortunes by now.rebl ought to be getting tired of karma fortunes by now.rebl ought to be getting tired of karma fortunes by now.rebl ought to be getting tired of karma fortunes by now.rebl ought to be getting tired of karma fortunes by now.rebl ought to be getting tired of karma fortunes by now.rebl ought to be getting tired of karma fortunes by now.
 
rebl's Avatar
 
Posts: 76
Karma: 580748
Join Date: Mar 2010
Location: It's time to get this Book a Rest
Device: Kindle 4 NT
Quote:
Originally Posted by HarryT View Post
Could be routing delays. Try doing a "tracert" to the sites concerned and see if there are any long delays on the route.
I'm not sure if the tracert really explains this (it could explain the ping/latency I guess) but I did notice something.
I did two tracert tests and a ping with dropbox vs box.com and i noticed that dropbox needs 12 hops and has one request timeout while box.com needs 8 hops and has no timeout.
Strengly enough, both tracert routes pass through some Jan Jose server (dropbox gets to SanJose2.Level3.net and the timout is right after this while box.com to SanJose1.Level3.net)
But I also did a ping and actually the total ping is lower for dropbox (191 vs 194 ms).

Nah, I actually think these interruptions might be some kind of limitation established by the providers (Microsoft and dropbox) to limit the bandwidth usage and/or prevent attacks/abuse. Or maybe they are a technical requirement for the stability of their systems.
rebl is offline   Reply With Quote