Hatsya Posted November 14, 2019 Share Posted November 14, 2019 (edited) Today, I am having issues with quite a few sim crossings, even trying to walk from one sim to another. Flying a plane seems to be a complete waste of time. On trying to cross, I am getting a message that I have never seen before; ''Unable to create pending connection''. The other message I get is ''Failed to grant capabilities''. Is anyone else having issues? Edited November 14, 2019 by Hatsya Additional info Link to comment Share on other sites More sharing options...
KT Kingsley Posted November 14, 2019 Share Posted November 14, 2019 It's not something that's happened to me, but there do seem to have been quite of few questions about this in the Firestorm Support chat just recently. Link to comment Share on other sites More sharing options...
Hatsya Posted November 14, 2019 Author Share Posted November 14, 2019 Thanks KT. This has just been posted on the Status Page, which may explain things - Investigating - We are currently investigating an issue that has affected access to a number of regions. During this time you may get teleport failures, or the region might appear to be offline.Nov 13, 23:09 PST 2 Link to comment Share on other sites More sharing options...
Logan Elf Posted November 14, 2019 Share Posted November 14, 2019 Wauaria (water region in Heterocera) seems to be one region that is affected. Link to comment Share on other sites More sharing options...
Hatsya Posted November 15, 2019 Author Share Posted November 15, 2019 This is supposed to have been resolved, but I am now getting "'Sorry, the system was unable to complete your region crossing in a timely fashion. Please try again in a few minutes''. 1 Link to comment Share on other sites More sharing options...
Lucifera Morningstar Posted November 16, 2019 Share Posted November 16, 2019 This isn't resolved at all. It's so bad in some areas of the Blake Sea that after crashing fairly badly, trying to log in gave me the error "agent is no longer in the region." And after another sim crossing via vehicle ended in failure, I couldn't TP home till I figured to WALK to the next region (under water) and then could TP home. Link to comment Share on other sites More sharing options...
arabellajones Posted November 19, 2019 Share Posted November 19, 2019 When I ran the Grid Drive on Saturday there did seem to be some horrible grid crossings, and the sims involved, in or out, had issues with sound effects. The Grid Drive huds have some voice messages, warning of ban-lines by the road, sim-corners, upcoming rez zones, useful things like that, but when I had a bad sim-crossing into a sim, the sound effects would go into a Max Headroom stammer mode, repeatedly restarting until I left the sim, and then all the problems stopped. There were other times when I just crashed out of SL on a sim crossing. And not even a warning message from the Viewer, which is unusual. So was it my connection? That seems unlikely, because when I crashed out I had to restart that leg of the Grid Drive, and the bad sims hadn't changed. I got the impression that a small set of physical servers was affected, and the sims they are running are scattered all over the Grid. I can't rule out some problems here as well. I don't see these things happening now, but I am not holding my breath waiting for info from the Lindens. Link to comment Share on other sites More sharing options...
jaja2939 Posted December 23, 2019 Share Posted December 23, 2019 It's still happen on some ISP. Nothing Improved over 1 months and Linden Doesn't need attraction to fix the Sim Crossing Disconnect in Some Users on side of the World. After Back to SL over a months. It's happen as network symptom from the Level 3 Hosting. which is not fixed and Here's Example Traceroute of the Simulator from my Country Tracing route to sim10413.agni.lindenlab.com [216.82.51.63] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 4 ms 3 ms 2 ms mx-ll-183.89.184-1.dynamic.3bb.in.th [183.89.184.1] 3 2 ms 1 ms 1 ms 10.121.50.98 4 13 ms 14 ms 13 ms mx-ll-110.164.0-235.static.3bb.co.th [110.164.0.235] 5 17 ms 15 ms 15 ms mx-ll-110.164.14-218.static.3bb.co.th [110.164.14.218] 6 11 ms 13 ms 11 ms mx-ll-110.164.14-244.static.3bb.co.th [110.164.14.244] 7 11 ms * 11 ms mx-ll-110.164.1-123.static.3bb.co.th [110.164.1.123] 8 12 ms 12 ms 12 ms mx-ll-110.164.1-21.static.3bb.co.th [110.164.1.21] 9 54 ms 53 ms 55 ms mx-ll-110.164.0-223.static.3bb.co.th [110.164.0.223] 10 212 ms * 210 ms mx-ll-110.164.0-23.static.3bb.co.th [110.164.0.23] 11 220 ms * 220 ms xe-4-1-0.bar1.SanFrancisco1.Level3.net [4.35.160.121] 12 * * * Request timed out. 13 248 ms 248 ms 246 ms LINDEN-RESE.bar1.Phoenix1.Level3.net [4.53.104.14] 14 * * * Request timed out. 15 * * * Request timed out. 16 239 ms 240 ms * sim10413.agni.lindenlab.com [216.82.51.63] 17 240 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 18 241 ms 240 ms * sim10413.agni.lindenlab.com [216.82.51.63] 19 240 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 20 240 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 21 240 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 22 239 ms 240 ms * sim10413.agni.lindenlab.com [216.82.51.63] 23 241 ms 240 ms * sim10413.agni.lindenlab.com [216.82.51.63] 24 239 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 25 241 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 26 241 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 27 240 ms 240 ms 241 ms sim10413.agni.lindenlab.com [216.82.51.63] 12,14 and 15 from Level 3 are having Request Timed Out. so. The CenturyLink will fix the Request Timed Out to have better networking. from my Country. Link to comment Share on other sites More sharing options...
Ansariel Hiller Posted December 23, 2019 Share Posted December 23, 2019 It's timing out on some hosts because they don't reply to ICMP ping messages. This doesn't have any effect on region crossings at all. Apart from that I have no clue what you are actually trying to say. Link to comment Share on other sites More sharing options...
Theresa Tennyson Posted December 23, 2019 Share Posted December 23, 2019 (edited) 45 minutes ago, jaja2939 said: It's still happen on some ISP. Nothing Improved over 1 months and Linden Doesn't need attraction to fix the Sim Crossing Disconnect in Some Users on side of the World. After Back to SL over a months. It's happen as network symptom from the Level 3 Hosting. which is not fixed and Here's Example Traceroute of the Simulator from my Country Tracing route to sim10413.agni.lindenlab.com [216.82.51.63] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 4 ms 3 ms 2 ms mx-ll-183.89.184-1.dynamic.3bb.in.th [183.89.184.1] 3 2 ms 1 ms 1 ms 10.121.50.98 4 13 ms 14 ms 13 ms mx-ll-110.164.0-235.static.3bb.co.th [110.164.0.235] 5 17 ms 15 ms 15 ms mx-ll-110.164.14-218.static.3bb.co.th [110.164.14.218] 6 11 ms 13 ms 11 ms mx-ll-110.164.14-244.static.3bb.co.th [110.164.14.244] 7 11 ms * 11 ms mx-ll-110.164.1-123.static.3bb.co.th [110.164.1.123] 8 12 ms 12 ms 12 ms mx-ll-110.164.1-21.static.3bb.co.th [110.164.1.21] 9 54 ms 53 ms 55 ms mx-ll-110.164.0-223.static.3bb.co.th [110.164.0.223] 10 212 ms * 210 ms mx-ll-110.164.0-23.static.3bb.co.th [110.164.0.23] 11 220 ms * 220 ms xe-4-1-0.bar1.SanFrancisco1.Level3.net [4.35.160.121] 12 * * * Request timed out. 13 248 ms 248 ms 246 ms LINDEN-RESE.bar1.Phoenix1.Level3.net [4.53.104.14] 14 * * * Request timed out. 15 * * * Request timed out. 16 239 ms 240 ms * sim10413.agni.lindenlab.com [216.82.51.63] 17 240 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 18 241 ms 240 ms * sim10413.agni.lindenlab.com [216.82.51.63] 19 240 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 20 240 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 21 240 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 22 239 ms 240 ms * sim10413.agni.lindenlab.com [216.82.51.63] 23 241 ms 240 ms * sim10413.agni.lindenlab.com [216.82.51.63] 24 239 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 25 241 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 26 241 ms 241 ms * sim10413.agni.lindenlab.com [216.82.51.63] 27 240 ms 240 ms 241 ms sim10413.agni.lindenlab.com [216.82.51.63] 12,14 and 15 from Level 3 are having Request Timed Out. so. The CenturyLink will fix the Request Timed Out to have better networking. from my Country. Look at steps 8, 9 and 10. The ping time is increasing around 200 ms within your provider's system, and one out of the three times failed. Edited December 23, 2019 by Theresa Tennyson Link to comment Share on other sites More sharing options...
Ansariel Hiller Posted December 23, 2019 Share Posted December 23, 2019 Which can easily be caused by an overseas connection and looks exactly the same if you do a trace route from Europe. Link to comment Share on other sites More sharing options...
jaja2939 Posted December 24, 2019 Share Posted December 24, 2019 These Californian/Asians having some sim Crossing/TP Failures at the moment! due to Level 3 Communication Issues that not been resolved. It's fine if it on the USA East Coast or Europe!. Link to comment Share on other sites More sharing options...
Ansariel Hiller Posted December 24, 2019 Share Posted December 24, 2019 (edited) If any, it's within the BB3 network, which is a different company than Level 3. But since 3BB is apparently a network provider in Thailand, it's more that the ping time increase from hop 9 to 10 is the oversea connection from Thailand to the US. And a "high" ping time is not an indicator for region crossing fails. Instead, you should run a constant ping to one of the regions the disconnect occurred and check the packet loss to determine if it's a network issue or not. Edited December 24, 2019 by Ansariel Hiller Link to comment Share on other sites More sharing options...
jaja2939 Posted December 25, 2019 Share Posted December 25, 2019 yes. this situation are not fixed yet. It's had packet losses and maybe. I'll do the ping test on the command line. Here's Results that i got. from Windows Power Shell. Pinging sim10494.agni.lindenlab.com [216.82.51.200] with 32 bytes of data: Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=240ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Request timed out. Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=240ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=243ms TTL=49 Reply from 216.82.51.200: bytes=32 time=243ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=240ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=243ms TTL=49 Reply from 216.82.51.200: bytes=32 time=242ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=241ms TTL=49 Reply from 216.82.51.200: bytes=32 time=240ms TTL=49 Lots of Request Timed out here. if i diagnose the problem before launching sl. use ping -w 1 everytime. Link to comment Share on other sites More sharing options...
Love Zhaoying Posted December 25, 2019 Share Posted December 25, 2019 (edited) If you use "tracert" to find the route, that may help find the weak link in your network that is resulting in the timeouts. Edited December 25, 2019 by Love Zhaoying Link to comment Share on other sites More sharing options...
Ansariel Hiller Posted December 25, 2019 Share Posted December 25, 2019 (edited) "Lots of requests" = 1 🙄 I don't see anything unusual in that ping results, particularly not lots of failed requests. Edited December 25, 2019 by Ansariel Hiller Link to comment Share on other sites More sharing options...
Facebook
Instagram
Twitter
YouTube
Flickr
Recommended Posts
Please take a moment to consider if this thread is worth bumping.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now