Connectivity issues?

[mygoditsfullofstars]

16 minutes ago, Ardy Lay said:

Blame space weather.

https://spaceweather.com/

I'm not saying it is space weather, but space weather!

It's those damn solar flares again.

 

[MBeatrix]

15 minutes ago, Aishagain said:

This is a silly question and one that may have already been adressed but is there any corealation between this login stalling issue and the Operating system for are using?  Like is it just Mac or are all OSs being affected?

I ask because I am still completely unaffected.

I'm using Windows 10 up-to-date. And as I wrote before, it all worked just fine early today.

Support seems to be out of solutions. Now they recommend that I contact my ISP, which isn't the same ISP people with the same problem in the UK, France, Germany and Brazil (and who knows where else) have.

My PC is hardwired to the router, as it's always been. That was another suggestion from Support besides recommending me to contact my ISP.

If this issue persists over time, I will be forced to cancel my membership and take out all the money stored in my Tilia account.

Edited December 14, 2023 by MBeatrix
typo correction

[mygoditsfullofstars]

11 minutes ago, Aishagain said:

This is a silly question and one that may have already been adressed but is there any corealation between this login stalling issue and the Operating system for are using?  Like is it just Mac or are all OSs being affected?

I ask because I am still completely unaffected.

I am unaffected too. Using Linux here. Unsure if there is any pattern to operating system/os version.

Looking at the data in this thread so far, it doesn't appear to be Country or ISP specific. It could be a problem with an intermediate network carrier somewhere along the network path into Amazon that's having issues and those who are unlucky are being routed via that carrier..

Anyway pure speculation on my part - it will be interesting to see what it actually is.

[MBeatrix]

2 minutes ago, mygoditsfullofstars said:

It could be a problem with an intermediate network carrier somewhere along the network path into Amazon that's having issues and those who are unlucky are being routed via that carrier.

Yes! That's the only thing that makes sense to me.

[Chat Waifu]

I get the same issue with my main connexion but with the connexion since my mobile I don't have any problem...

[mygoditsfullofstars]

It might be interesting to know whether or not if any of the affected people are using VPN's (some AV software like Norton, and I am sure there are others also includes a VPN service that runs in the background, often without the end users knowledge its even rerouting their network traffic).

 

[Axel Naxos]

Windows 11 Pro, no VPN

[Chat Waifu]

I accept, I just testint with VPN since my antivirus and all work correctely but maybe modified the files hosts

Edit: don't work too

C:\Windows\System32\drivers\etc\hosts

Edited December 14, 2023 by Chat Waifu

[MBeatrix]

4 minutes ago, mygoditsfullofstars said:

It might be interesting to know whether or not if any of the affected people are using VPN's (some AV software like Norton, and I am sure there are others also includes a VPN service that runs in the background, often without the end users knowledge its even rerouting their network traffic).

 

No VPN here. I only use the built-in Windows security tools. And all Firestorm and Second Life Viewer critical folders are whitelisted.

[Brilliant Price]

Now here's the odd thing.

I Cleaned out my tired old iMac and loaded FS 6.6.17 onto it. (Just for desperations sake) And to my surprie I was able to get in-world to my home. Without any region handshake conectivity problems. Twice in fact. But I am afraid to try to teleport and I'm not going to because I want to keep channels open for my customer queries.

However on my more modern Macbook Air the original problem persists. This tells me that at least my fibre internet connection is not the issue. And now my finger points back to my laptop and to Firestorm. I suspect a file or something got corrupted during the installation. A file that other viewers also need access to.

But hey I'm no techy - far from it but surely  this is a clue.

[Chat Waifu]

Maybe it's the update windows 23h2

[MBeatrix]

6 minutes ago, Brilliant Price said:

Now here's the odd thing.

I Cleaned out my tired old iMac and loaded FS 6.6.17 onto it. (Just for desperations sake) And to my surprie I was able to get in-world to my home. Without any region handshake conectivity problems. Twice in fact. But I am afraid to try to teleport and I'm not going to because I want to keep channels open for my customer queries.

However on my more modern Macbook Air the original problem persists. This tells me that at least my fibre internet connection is not the issue. And now my finger points back to my laptop and to Firestorm. I suspect a file or something got corrupted during the installation. A file that other viewers also need access to.

But hey I'm no techy - far from it but surely  this is a clue.

My Firestorm 6.6.17 worked fine between about 9:30 and around 2 am SLT. Doesn't make sense to me that at some point it would change whatever might be needed by other viewers.

[EDIT] Unless it's an inventory problem. Hmmm...

Edited December 14, 2023 by MBeatrix
adding an idea

[Brilliant Price]

3 minutes ago, MBeatrix said:

My Firestorm 6.6.17 worked fine between about 9:30 and around 2 am SLT. Doesn't make sense to me that at some point it would change whatever might be needed by other viewers.

I agree , but there is no discernable reason why it works on one machine for the same account with the same ISP and not on the other. And if FS isn't the problem then it surely must be SLs servers that are hoodwinking the engineers.

As the evening progresses I am hearing of more and more people suffering the same trouble. But not a whisper from the lab other than Monty's notes earlier.

[MBeatrix]

1 minute ago, Brilliant Price said:

I agree , but there is no discernable reason why it works on one machine for the same account with the same ISP and not on the other. And if FS isn't the problem then it surely must be SLs servers that are hoodwinking the engineers.

As the evening progresses I am hearing of more and more people suffering the same trouble. But not a whisper from the lab other than Monty's notes earlier.

Yeah, LL seems ready to discard whatever they might be responsible for. Anyway, I'm off to sleep. We'll see how it goes tomorrow and the next few days. I'd hate to cancel my membership but if I can't enjoy SL, I'll find some other entertainment and maybe even save some money.

[mygoditsfullofstars]

5 minutes ago, Brilliant Price said:

I agree , but there is no discernable reason why it works on one machine for the same account with the same ISP and not on the other.

It has also been hit and miss for some people rather than constant - could it just be pure luck that the other machine worked when tested (ie: is it consistently able to log in and out and tp around with no issues?)

 

[Wired Georgia]

done some packet sniffing, it seems its an UDP issue, tried a specific region "pak" which seems to be located on "54.187.85.225" / "ec2-54-187-85-225.us-west-2.compute.amazonaws.com.13000"

i see UDP packets leaving my PC but i never see incomming UDP traffic from that IP

traceroute to that IP looks verry sick!

traceroute to 54.187.85.225 (54.187.85.225), 64 hops max
  1   192.168.x.x  0,614ms  0,293ms  0,319ms
  2   94.134.x.x  6,441ms  5,032ms  4,956ms
  3   62.214.42.136  6,582ms  5,696ms  7,504ms
  4   149.6.139.138  7,693ms  7,061ms  6,819ms
  5   62.115.161.20  12,051ms  11,152ms  11,172ms
  6   62.154.5.173  167,047ms  166,061ms  166,526ms
  7   154.54.56.93  111,277ms  110,115ms  110,490ms
  8   150.222.234.79  160,182ms  160,141ms  159,512ms
  9   66.28.4.237  110,564ms  109,193ms  109,376ms
 10   154.54.82.253  119,447ms  118,550ms  118,392ms
 11   *  *  *
 12   *  *  *
 13   154.54.42.97  144,449ms  143,361ms  143,097ms
 14   *  *  *
 15   *  *  *
 16   *  *  *
 17   *  *  *
 18   *  *  *
 19   *  *  *
 20   *  *  *
 21   *  *  *
 22   108.166.240.56  175,300ms  174,214ms  174,439ms
 23   *  *  *
 24   *  *  *
 25   *  *  *
 26   *  *  *
 27   *  *  *
 28   108.166.232.71  172,465ms  171,037ms  170,694ms
 29   *  *  *
 30   *  *  *
 31   *  *  *
 32   *  *  *
 33   *  *  *
 34   *  *  *
 35   *  *  *
 36   *  *  *
 37   *  *  *
 38   *  *  *
 39   *  *  *
 40   *  *  *
 41   *  *  *
 42   *  *  *
 43   *  *  *

 

anybody else who is having problems able to look at UDP traffic level or traceroute / tracert the region IP?

[Chat Waifu]

Well I did log now 3 time in Second Life Viewer and 1 time in Firestorm Viewer and not anymore issue atm

[mygoditsfullofstars]

19 minutes ago, Wired Georgia said:

done some packet sniffing, it seems its an UDP issue, tried a specific region "pak" which seems to be located on "54.187.85.225" / "ec2-54-187-85-225.us-west-2.compute.amazonaws.com.13000"

i see UDP packets leaving my PC but i never see incomming UDP traffic from that IP

traceroute to that IP looks verry sick!

traceroute to 54.187.85.225 (54.187.85.225), 64 hops max
  1   192.168.x.x  0,614ms  0,293ms  0,319ms
  2   94.134.x.x  6,441ms  5,032ms  4,956ms
  3   62.214.42.136  6,582ms  5,696ms  7,504ms
  4   149.6.139.138  7,693ms  7,061ms  6,819ms
  5   62.115.161.20  12,051ms  11,152ms  11,172ms
  6   62.154.5.173  167,047ms  166,061ms  166,526ms
  7   154.54.56.93  111,277ms  110,115ms  110,490ms
  8   150.222.234.79  160,182ms  160,141ms  159,512ms
  9   66.28.4.237  110,564ms  109,193ms  109,376ms
 10   154.54.82.253  119,447ms  118,550ms  118,392ms
 11   *  *  *
 12   *  *  *
 13   154.54.42.97  144,449ms  143,361ms  143,097ms
 14   *  *  *
 15   *  *  *
 16   *  *  *
 17   *  *  *
 18   *  *  *
 19   *  *  *
 20   *  *  *
 21   *  *  *
 22   108.166.240.56  175,300ms  174,214ms  174,439ms
 23   *  *  *
 24   *  *  *
 25   *  *  *
 26   *  *  *
 27   *  *  *
 28   108.166.232.71  172,465ms  171,037ms  170,694ms
 29   *  *  *
 30   *  *  *
 31   *  *  *
 32   *  *  *
 33   *  *  *
 34   *  *  *
 35   *  *  *
 36   *  *  *
 37   *  *  *
 38   *  *  *
 39   *  *  *
 40   *  *  *
 41   *  *  *
 42   *  *  *
 43   *  *  *

 

anybody else who is having problems able to look at UDP traffic level or traceroute / tracert the region IP?

Traceroute, while handy in some scenarios shouldn't be considered a definitive guide as to the health of a network path. By default, traceroute uses ICMP. Many layer 3 devices (routers, firewalls) drop ICMP traffic (or can even de-prioritize it under certain network conditions).

UDP is session-less, and UDP data not being returned could mean it is being lost literally anywhere along the network path, it doesn't necessarily indicate that the simulator or server itself is hosed and is not sending any traffic back.

 

Edited December 14, 2023 by mygoditsfullofstars

[Aishagain]

Having heard much inworld about this issue, I think the best solution in the interim is to try (and most likely) fail too log in with thr Linden Viewer and to pack up the logs and add them to the LL JIRA...I can't see one yet.

Without those Logs LL are going to be fighting with their hands tied.

The solution tagged "highly likely" at this point is one fubarred server node between the hapless users and SL.

 

Edited December 14, 2023 by Aishagain
ETA

[mygoditsfullofstars]

27 minutes ago, Wired Georgia said:

done some packet sniffing, it seems its an UDP issue, tried a specific region "pak" which seems to be located on "54.187.85.225" / "ec2-54-187-85-225.us-west-2.compute.amazonaws.com.13000"

i see UDP packets leaving my PC but i never see incomming UDP traffic from that IP

anybody else who is having problems able to look at UDP traffic level or traceroute / tracert the region IP?

UDP packet loss also wouldn't explain login issues (where some people are having to try 20 or more times before they can log in) since all of that most certainly is TCP (during the initial authentication stage).

Edited December 14, 2023 by mygoditsfullofstars

[Cube Republic]

I'm not alone!

 

It's been all day for me. 

Edited December 14, 2023 by Cube Republic

[Tetsuryu Vlodovic]

1 hour ago, mygoditsfullofstars said:

It could be a problem with an intermediate network carrier somewhere along the network path into Amazon that's having issues and those who are unlucky are being routed via that carrier..

That's my guess as well, considering there's little consistency between all the different reports in terms of environment, just the effect.

I've stayed logged in in the same region all day now but when I walked into a different parcel, the land info shows me as still being in the previous one.

...and as I'm typing this, I finally get disconnected.

[Reuben Blakewell]

Also having this exact same problem.

Suddenly, unable to move around, interact etc and was disconnected. Tried to reconnect same issue "We're having trouble connecting. There may be a problem with your Internet connection or the Second Life Grid.".

Tried to reconnect, unable, same issue as above. Finally got in, nothing then loads and trying to TP away disconnected again. Finally reconnected another 2 times and back in as normal.

My friend meanwhile was in the whole time, their location LA, North America. My location, UK, Euorpe.

[Reuben Blakewell]

37 minutes ago, Aishagain said:

Having heard much inworld about this issue, I think the best solution in the interim is to try (and most likely) fail too log in with thr Linden Viewer and to pack up the logs and add them to the LL JIRA...I can't see one yet.

Without those Logs LL are going to be fighting with their hands tied.

The solution tagged "highly likely" at this point is one fubarred server node between the hapless users and SL.

 

What are the logs they need and where to access I can upload mine.

[Monty Linden]

1 hour ago, mygoditsfullofstars said:

Traceroute, while handy in some scenarios shouldn't be considered a definitive guide as to the health of a network path. By default, traceroute uses ICMP. Many layer 3 devices (routers, firewalls) drop ICMP traffic (or can even de-prioritize it under certain network conditions).

UDP is session-less, and UDP data not being returned could mean it is being lost literally anywhere along the network path, it doesn't necessarily indicate that the simulator or server itself is hosed and is not sending any traffic back.

Correct.  We're happy to get any kind of traceroute between your home systems and a simhost in support tickets.  But here are some hints on better trace routing:

Better in the sense that it will terminate.  It doesn't, for example, detect problems unique to UDP.