In reply to a post by Pheasant:

It’s a good point Amazon, Apple, Google, Microsoft et al don’t exactly advertise where they plop their various mega datacentres.

I think it's known within the industry. I certainly know where some other sites are but I don't recall the London ones. I just know Telehouse is more an interconnect site than a hosting one (to the extent we pay a lot more to host in there)

seb

In reply to a post by Stargazer99:

Here's the route from Truespeed (see linked image - note that the ping time is now back where it should be):
Link to image


My own routing (from Giganet/CityFibre) looks a lot simpler...
Tracing route to jam.********.uk [51.104.x.x]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.1]
2 5 ms 5 ms 5 ms thn-bn-3.giga.net.uk [37.48.224.36]
3 5 ms 5 ms 5 ms 217-168-248-67.m12solutions.net [217.168.248.67]
4 6 ms 6 ms 6 ms lonap01.msn.net [5.57.81.17]
5 7 ms 6 ms 6 ms ae28-0.icr02.lon22.ntwk.msn.net [104.44.239.121]
6 *

What sort of latency are you seeing? Also what about jitter? if you ping for a minute what's the average vs worst?
Above looks ok.

I know the latency on VoIP before people notice is quite high - I'm not sure what it's like for interactive music where you have to co-ordinate rather than speak one at a time .. I imagine it's a bit smaller.

The latency on hops on traces is a but unreliable (as routers don't respond to pings with high priority) e.g. from us:


Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. ncuk-gw.core-rs3.thdo.ncuk.net 0.0% 48 0.8 0.7 0.6 0.9 0.0
2. xe-1-3-0-36.edge-rt5.thdo.ncuk.net 0.0% 47 0.6 1.5 0.4 31.5 4.7
3. ae11-11.edge-rt1.thn.ncuk.net 0.0% 47 0.8 0.7 0.4 4.4 0.6
4. lonap01.msn.net 0.0% 47 29.7 3.0 1.3 36.1 6.4
5. ae28-0.icr02.lon22.ntwk.msn.net 0.0% 47 1.7 5.9 1.4 60.0 10.7
6. ???

..the variation for worst is quite high.. you can ping to your server though and see what that looks like..

seb

UK West is out in Newport on the old LG site, UK South is Slough.

In reply to a post by jpm:

UK West is out in Newport on the old LG site, UK South is Slough.

I thought I knew Slough but not if it's Equinix or one of the others out there. I doubt it's Iron Mountain

seb

My ping is very consistent - completely rock solid at 5-6ms for bbc.co.uk and 8.8.8.8 - it wasn't my own broadband that I was concerned about. The guitarist in our online band also gets similar results for bbc.co.uk and 8.8.8.8, again very stable. The problem he was having was a ping of 35ms for the Microsoft Azure server - this seems to have been a temporary glitch in the routing as it's fine now.

Tor playing online music you ideally need <30ms total round trip time including buffering and delays introduced by equipment - this equates to a ping of around 15-18ms or less typically, so the application is pretty demanding. For some more demanding types of music a total delay of <20ms is desirable, so a ping to the server no more than of 5-8ms. This is achievable if you're all in the same general part of the UK with FTTP, and most of our band members have FTTP and just about achieve this.

In reply to a post by Stargazer99:

My ping is very consistent - completely rock solid at 5-6ms for bbc.co.uk and 8.8.8.8 - it wasn't my own broadband that I was concerned about. The guitarist in our online band also gets similar results for bbc.co.uk and 8.8.8.8, again very stable. The problem he was having was a ping of 35ms for the Microsoft Azure server - this seems to have been a temporary glitch in the routing as it's fine now.

Tor playing online music you ideally need <30ms total round trip time including buffering and delays introduced by equipment - this equates to a ping of around 15-18ms or less typically, so the application is pretty demanding. For some more demanding types of music a total delay of <20ms is desirable, so a ping to the server no more than of 5-8ms. This is achievable if you're all in the same general part of the UK with FTTP, and most of our band members have FTTP and just about achieve this.

I think this makes for an interesting case study about why latency matters. You don't happen to have any video/audio recordings of when you had problems?

Routing is dynamic and there are multiple reason sit may change so it's usually not simply down to the provider having an issue but possibly the path to a destination. The larger companies will be very slow to admit problems, usually because staff on the front line just son't know about issues and say there aren't any.