Unable to move

Same problem here - also XS4ALL. Same as all the others - since yesterday afternoon.

I hae the same problem as others mentioned. At certain regions I loose connection within a minute or so.

Yes I am Holland and XS4all too!

For me it depends on the place. Some regions don't give any problems, others do all the time.

I noticed that in problem regions I have little bandwidth (like 25k in stead of the normal 250k or so) and huge packet loss.

Greetz,

Jos

Exact same problem for me , some Sims ok others 1-3 Mins and I lose all Bandwidth also Xs4all ,any solutions ?

Just logged into Amsterdam and still had the same issue

I tried logging into Tourmaline from the login screen, but it didn't want to put me there. It put me into Miramare instead: sim3675.agni.lindenlab.com (64.129.46.186:13005)

Looks ok sofar...

I did some experiments, I think the San Francisco sims are the ones giving the problems.... not sure yet...

Whenever I see sprintlink.net in the traceroute I get the problems....

You could be right. The one where I didn't have problems was going through Cogentco.

I also created a help request to LL and pointed them to this thread.

Did the same with an e-mail to the Xs4all helpdesk.

No reply from either of them sofar.

Texas.

Texas.

California.

Of course, that's only 3 sims out of several thousand..

If you're interested in this stuff and don't want to run tracert on every sim, try Max Case's Sim Neighbors page.. It will tell you which colo a sim is in by just entering the sim name.

I have exactly the same problem, also from the Netherlands..Some sims (even very busy/prim heavy ones) load fine, others I can get in, move for a few secs, then talk for maybe a min before things get horribly stuck. This happens only at certain sims and started about two days ago..Really frustrating.

EDIT: Im on Xs4all/KPN as well and the sims giving problems do go through Sprintlink..I really hope someone will figure out a fix to this soon because I wouldnt be happy if I had to switch my ISP only to get the problem sorted.

Ohh thank GOD it's not just us!!

XS4All here too, and in the Netherlands. This problem started just a few days ago. It is only in SOME sims. One being our OWN land, so we are unable to do anything there whatsoever, can't even move - and we have rentals there too to take care of!

The other being a sim where I rented a house. I can TP to the sim, but once there, I take one or two steps and BOOM! stuck. Ping sim is on 1000 msec and Ping user is the same. Everything worked fine before a couple of days ago. ARGH

Please don't tell us to uninstall and install SL again - Did that
Empty cache etc - Did that

It's clearly something to do with either a) XS4ALL or b) the connection from SL to Holland.

Please please does anyone have any answers as to what the cause is, it's a living nightmare!

In hope
Mandy Lurra and Jim Lurra


EDITED TO SAY -

Just been on the phone with XS4ALL and they assure us that it is a problem with the servers at Second Life, and not them. There is nothing blocked at XS4ALL whatsoever, therefore have advised us to contact SL helpdesk to erase the problem. XS4ALL also said that SL are quite welcome to give them a call should they want, or need to discuss the issue.

Soooo please, everyone with this problem, send in a Help Request and perhaps the issue will be resolved sooner rather than later.

Thnx

Ok, I have just submitted my second support request to the Lindens.

The problem was solved for me yesterday, but now back again.

Fine in Tourmaline, stuck in Zarathud.

Please everyone submit a support request !

And the same problem here and also from Holland, i have a ping user of 10000 lol and when i TP to some places my simping goes up to 10000 too, i freeze still hear music for a few seconds, can't move nor use IM and than, voila i loose connection to the server.
Is Holland doomed, do Lindens no longer want Dutch people in SL??
Hoping this will be solved or anyone can explain what is happening ehre cause obviously i'm not the only Dutch person cursing when i log in and find my ass all froozen up again once more

Hmm well i forgot to mention XS4all here too and erhm, can't even go home cause there i have the same problem and same goes for my shop

Still same problem , can not go to my home ,can not go to island i use to build , have just got of phone to US office , did not get to talk to anyone but left voicemail and will get voiceticket ?? have filed bug report , and everything else * fingers crossed

Hi,

same problem as yesterday, same ISP.

I have some locations that are all right and some that are not:

Good:
Korea1 located at sim2973.agni.lindenlab.com (64.129.43.215:13005)
Swingers Island located at sim3586.agni.lindenlab.com (64.129.46.97:13005)
Peacehaven located at sim2943.agni.lindenlab.com (64.129.43.185:13006)
Badlands located at sim3257.agni.lindenlab.com (64.129.45.22:13005)
Martys Somnium located at sim3383.agni.lindenlab.com (64.129.45.148:12035)


Problem:
Exotica Island located at sim633.agni.lindenlab.com (69.25.105.65:12035)
Busiris located at sim745.agni.lindenlab.com (69.25.105.177:13004)
Hypatia located at sim660.agni.lindenlab.com (69.25.105.92:12035)
Plush Sigma located at sim354.agni.lindenlab.com (69.25.104.40:13006)
Tecta located at sim730.agni.lindenlab.com (69.25.105.162:13004)
Nipigon located at sim1102.agni.lindenlab.com (72.5.12.252:13005)


It looks like IP 64.129.*.* is alright but 69.25.*.* (and 72.5.*.*?) is not

You can get these numbers from the help, about ... menu. Maybe more people can post their good and bad places. And maybe someone can figure it out.

Greetz,

Jos

ISP Demon Amsterdam, now XS4all
I´m having big problems at 72.5.12.239
Most other locations are doing well.
Because all complains come from XS4all customers I think it´s an XS4all problem and not a Linden server problem.
Why else can other Dutch people talk and walk around at 72.5.12.239, their connection to Linden obviously works.

Grtz Eva

Just called with the XS4ALL helpdesk, I do think the problem lies with them as theyre the only provider that seems to be affected in the Netherlands..He gave me the following email adress [email]abuse@xs4all.nl[/email] and told me to post here and ask everyone suffering from this to mail there so it gets prioritized..The newspaper today said 44k members of SL were dutch atm so that must mean a pretty large amount of people have to be affected by this.

So if you suffer from these problems, please send a mail to [email]abuse@xs4all.nl[/email] and hopefully we can get them to take some action quickly and get this mess sorted.

Thanks for the IP addresses. I traced them all with the tracert utility. All the good ones go from xs4all to cogentco, see hops 5 and 6:

 5   9 ms  11 ms   9 ms 0.so-6-0-0.xr1.tc2.xs4all.net [194.109.5.10]
 6 218 ms  13 ms 272 ms te3-3.mpd01.ams03.atlas.cogentco.com [195.69.144.124]

All the bad ones go from xs4all to sprintlink. See hops 5, 6 and 7:

 5    9 ms    9 ms   10 ms  0.so-7-0-0.xr1.tc2.xs4all.net [194.109.5.14]
 6    8 ms    9 ms    8 ms  217.149.46.21
 7    9 ms    9 ms    9 ms  sl-bb21-ams-8-0.sprintlink.net [217.149.32.41]

The unnamed 217.149.46.21 IP address belongs to Sprintlink (Netherlands) according to ripe.net's whois database.

The conclusion has to be that there is a problem somewhere in the connection between Xs4all and Sprintlink.

The question is: how can we make the right people aware of this?

As I said before I sent in a help request to LL as well as the Xs4all helpdesk, but I didn't receive an answer from either of them yet.

UPDATE: Sent a mail with the above explanation to [email]abuse@xs4all.nl[/email].

Well, so much for mailing to [email]abuse@xs4all.nl[/email]:


Translation: the advice to mail to [email]abuse@xs4all.nl[/email] was bad advice. You can contact the Xs4all Helpdesk.

Mailing abuse is indeed not a very good thing to do, but everyone do bring the problem under XS4ALL's attention !!!!

Sorry but the advice to mail to [email]abuse@xs4all.nl[/email] was given to me by one of their helpdesk members, he said they were the ones responsible for any possible ip blockades..So if its not good to mail them its xs4all helpdesk members giving out bad information.

I see an emerging pattern here, XS4ALL

I would advise calling their Helpdesk and ask them to do a trace route to one of the regions your are experiencing problems.

I have no problems connecting from Holland (yes I am a dutch Linden) but I am with @Home.

UPDATE: Sent a mail with an explanation to [email]abuse@xs4all.nl[/email] and called the helpdesk.

We ALL need to do this, ASAP, and if possible a telephone call to their helpdesk. They tried to fob me off today saying it was Second Life's problem. Don't let them do that to you when as mentioned in earlier posts, it's an XS4ALL problem.

At this moment everything seems to work again, see tracert:
1 13 ms 103 ms 95 ms dsldevice.lan [xxx.xxx.xxx.xxx]
2 7 ms 7 ms 8 ms xxx.xxx.xxx.xxx
3 19 ms 10 ms 17 ms 42.ge-4-0-0.xr1.3d12.xs4all.net [194.109.5.49]
4 29 ms 8 ms 8 ms 0.so-6-0-0.xr1.tc2.xs4all.net [194.109.5.10]
5 8 ms 9 ms 8 ms 217.149.46.21
6 9 ms 26 ms 9 ms sl-bb21-ams-8-1.sprintlink.net [217.149.32.60]
7 16 ms 16 ms 16 ms sl-bb23-lon-4-0.sprintlink.net [213.206.129.143]

8 16 ms 16 ms 16 ms sl-bb21-lon-13-0.sprintlink.net [213.206.128.55]

9 88 ms 88 ms 88 ms sl-bb21-tuk-8-0-0.sprintlink.net [144.232.9.209]

10 103 ms 87 ms 86 ms sl-bb20-tuk-5-0-0.sprintlink.net [144.232.9.170]

11 110 ms 118 ms 110 ms sl-bb20-rly-11-0.sprintlink.net [144.232.20.136]

12 109 ms 110 ms 110 ms sl-bb26-rly-9-0.sprintlink.net [144.232.7.250]
13 131 ms 108 ms 117 ms sl-bb25-rly-13-0.sprintlink.net [144.232.14.169]

14 198 ms 185 ms 185 ms sl-bb23-sj-9-0.sprintlink.net [144.232.20.11]
15 178 ms 183 ms 178 ms sl-gw19-sj-15-0.sprintlink.net [144.232.0.250]
16 178 ms 181 ms 186 ms sl-internap-140-0.sprintlink.net [144.228.111.94
]
17 193 ms 182 ms 215 ms border2.ge2-1-bbnet2.sfo002.pnap.net [63.251.63.
82]
18 188 ms 186 ms 188 ms sim316.agni.lindenlab.com [69.25.104.2]

Problem is still there for me. Day 4-5 now ?

I had one day without problems; now it has returned
No need to email XS4All helpdesk again: Still waiting for the first reply