Large network delay between gateway and linode


13 ( 82.529 ms 83.709 ms 8

4.842 ms

14 ( 90.922 ms 89.219 ms 95.109 ms

15 ( 99.901 ms 98.398 ms 89.797 ms

16 ( 170.146 ms 171.590 ms 169.353 ms

That extra 70->80ms between the previous hop and my linode is quite massive. I know the structure of UML could mean data passing an additional network stack (on my home network pings between one machine and a host server, and between the machine and a UML instance show the UML instance takes almost twice as long… but we're still talking usec's on my local LAN) whereas we're now talking almost doubling of round trip delays.

Could I just be testing at a bad time (00:20 Sunday morning) where the host is overloaded with weekly processing, or what?

This latency is causing some of my connections to take a long time :-(

1 Reply


One way to see if it is your linode that is causing the delay or a general problem is to try tracing to the host.

It is also worth tracing to hosts around yours as well.



Please enter an answer

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct