Today I rode in the 09:15 (correction edit - It should have been 08:14 for my D Cat) BST Sea Breeze Stage 1 “race” No mention in the description of this being a TT event, but I had to ride it as a TT because there was nobody else in my pen, nobody else on course during the event and nobody else in Watopia for a further 75 minute of pedaling around.
The ride saved perfectly well. Emails came through. My WiFi connection was robust. Where was everybody else?
Android tablet. I skipped pairing on initial entry into Watopia, but was forced to complete pairing before I could join the event. So no excuses for my solo experience that I can think of.
Looks like there was a substantial field for that event
I don’t see you in the results or on the live tab unless I’m missing something.
I think you got disconnected from the Zwift servers for some reason. Could be a network issue anywhere between your tablet and their backend systems in the US. That’s what it means when you don’t see any riders.
I do not think it was a connection problem in the conventional sense. To see nobody in Watopia for 105 minutes is stretching credibility. Typically a disconnection will fix itself after a bit, and given that my ride and screenshots saved at the end I definitely was connected. This feels to me like a bug related to not being paired before entering the game.
I’m really just flagging it in case it is a bug rather than a one off glitch.
Oops, my bad. I was going from memory and forgot that I was an early riser this morning. Normally I wouldn’t be doing anything on Zwift before 09:00. I actually have an 08:14 start time on Strava (from Zwift) for my Cat D start.
p.s. in my pen I could see the rider count increase, without any riders visible. I saw 0/36 riders displayed at one point, which did seem highly fishy.
it was like 2 weeks ago for me, i was Zwift racing , Zwift DC on me, but the kicker is my Live stream was 100% still going i was chat with the guys look Zwift DC on on me , stream was fine. @Tim_dODZ
Thank you for that, Paul. I don’t know how to interpret the findings, but possibly UDP comms was entirely FUBAR throughout the ride. Everything else looks to be OK, including TCP stuff. Absolutely no changes to network config or my tablet since a successful group workout yesterday.
If you see it again, I would reboot all of your network equipment. Routers that do network address translation sometimes get confused handling UDP while TCP continues to work.
There is also a ping test on the zwiftalizer menu that you can use to check connectivity all the way to Zwift’s backend.
Of course it might also have been a glitch on Zwift’s end - hard to say for sure since the problem doesn’t point to a specific point of failure.
Note that the latency test is using TCP (HTTP) so it checks performance but not UDP connectivity.
I wonder why you are seeing 36ms round trip times to the gateway, which is not great. I assume that’s the first hop past your home equipment (if that’s actually your home router then it’s awful).
Those numbers seem to revolve in unison from a low of about 9ms up to as much as 175ms. That sample is just from when I grabbed a screenshot. No idea if anything can be read into them.
Speed test.net is currently giving pings of 16ms idle, which is slow in my experience. I’ll reboot everything.
