40ms is pretty amazing if true

For normal world somewhere around the 100 is about right. Also where in the US makes a big difference as it is such a wide country.

Routing can change as pipes fill up and alternate routes are chosen depending on the 'cost' of the various routes.

In reply to a post by MrSaffron:

For normal world somewhere around the 100 is about right. Also where in the US makes a big difference as it is such a wide country.

Virginia/east coast

In reply to a post by MrSaffron:

40ms is pretty amazing if true

For normal world somewhere around the 100 is about right. Also where in the US makes a big difference as it is such a wide country.

Routing can change as pipes fill up and alternate routes are chosen depending on the 'cost' of the various routes.

He's definitely not getting 40ms, suspect user error.

It's about 70ms from London to NY - I get about 77-78ms to NY on Sky FTTC and used to get a little lower (75-76) on Be ADSL.

What's the IP of the server you're connecting to OP?

In reply to a post by MrSaffron:

Routing can change as pipes fill up and alternate routes are chosen depending on the 'cost' of the various routes.

That would be done manually through traffic engineering. BGP does not use utilisation as part of its routing decisions.

It would be very odd for an ISP to change routing during evenings then change it back during off-peak periods.

In reply to a post by driz:

What's the IP of the server you're connecting to OP?

199.108.194.41

87 ms