This weekend (particularly Sunday 6/22), I experienced disconnects every handful of teleports using SL Viewer, Firestorm, and Alchemy viewers alternately. While that's an immediate inconvenience and concern, it's not the root of the problem:
The problem is that I don't even know there's a problem. As is
always
the case with networking issues, "everything else" was working fine; video streaming in web browsers, connections to SL and other websites, Discord servers etc so I was not having an overall internet outage... but then, I can't really
do
anything here. If there's a problem on my end, I can't tell; if the grid is struggling, I can't send you anything to determine what might have been bottle-necking.
When I have a viewer crash, at least I get a bugsplat thing, right? But what happens when I go to teleport to a new region, and 20% of the time, I get a progress bar just sitting still at "Requesting region capabilities" or region handshake? What's really happening under there? I know that after 60 seconds, it'll time out and "Quit" the viewer, but that leaves me with nothing to tell you about what has happened. Nothing crashed and yet, something's wrong~
I've heard many (including Lindens) refer to region changing as an indecipherable and scary mess of spaghetti code, but this is the lifeblood of the platform, and it seems to have phases where error rates go through the roof (anecdotally, during the half-day I had these issues, various group chats indicated I was not alone). A thousand little cuts in silence, and it's hard to know what to report and how.
The request here is a bit nebulous, I apologize, but that's because I don't even know what LL needs, but please add something to the viewer to log region changes in some way that is meaningful to you, and that presents itself when the viewer times out and disconnects. You know that screen where I can choose to view IMs offline or Quit, when I have a timeout? Add something there, please, to open the region change log folder. (And pls make a region change log, even just to track the most recent change; it sounds as though this one area of SL activity could use better investigation). That way, when things are acting up, there's something to send to support that hyper-focuses on the specific region-change that caused the problem. I could attach that here, or send it to customer support etc.