Unable to move

This is looking VERY promising...

My source IP is in the 80.126.x.x range and I have been on a "bad sim" (72.5.x.x) for 5,5 hours straight, without a problem !

same for me, 80 range, if its solved for us i am so damm happy and wanna thnk all for not giving up. Yet if people still are suffering, i will keep my hopes up for you all and hope it will be solved soon for you all as well and let us not let them down either. You have our support cause we know how it sucks.!!!! PLZ help all that cant stay as well.
A very gratefull andHyper Cloudy....

Go to google or another search engine and type "what is my IP" then click the top link. That tells you your IP number. There's no need to type your whole IP here, just the first 2 numbers will show the range.

Are you in the Netherlands and use XS4ALL ? If not then perhaps your problems aren't related to this thread.

Thanks Mandy

i am in the 80.xx range too and it looks like the problems are over for me too...

*sighs releived after more then 14 days...finally....*

I was happy to have been able to SL for some time properly without issues some hours ago, but as I write this message the issues have returned. Just as confirment that not everyone's connection is fixed yet.

Still abandoned from my home, my ip is 82.161.*.*.
I cannot understand why not all of us are unbugged. *unsmiles*

Very happy for those of us that are "cured", still missing any respons from the responsible persons...

When in the middle of 2006 Demon (my ISP) was sold to XS4ALL there ware many reactions of Demon customers, most of them people who do more with internet then just surfing and emailing and know what they are talking about.
They wanted to go everywhere, as long as it wasn´t XS4ALL.
At that time I didn´t quite understand that, XS4ALL couldn´t be all that bad as they described?
Well, now I know they were right.
I have received a migration offer, which is 5 Euro more expensive than Demon and they call this an offer, because normally I would pay + 20 Euro for the same "service".
In the meantime Demon´s usenet is replaced with XS4ALL´s newsgroups and that is a huge step back.
This SL problem is also a typical example of how XS4ALL handles problems of customers.
There is some activity but absolutely not enough to solve this problem.
And yes, it is an XS4ALL problem, only customers of this ISP suffer from problems of not being able to move in certain areas and that for 16 days now!
And I´m afraid that it is going to be a long, long time before a solution will be provided.

Greetz,
Eva

Ok, it works for me now too. I assume it is the last mail Timo sent about the ranges to redirect via sprintlink.

For the Demon users, please post on Jira (not working now??), what I see is that you have a different routing information than the one mentioned in Timo's post there. One email from Timo to SL might fix the problems for you too!

Ah ah ah , you forget that users from other countries have reported issues on Jira / this thread as well .
It is not specific to XS4all / Holland .

As a matter of fact , I know a person in Germany who has the exact same issuse on the exact same sims as I do and that`s T-mobile for provider .

So it isn`t solely XS4all , but you can argue that as a "particulier" you are powerless in the corporate world and need your ISP to represent your problem to the said company that producse the issue for the ISP`s costumers .
But that really isnt their obligation to fulfill , because if they were to put that in their terms then you will get a floodwave of a million and one problems 99.99999 % unrelated .
--------------

At any rate , I`m in the 83. range and still have issues so i`m going to put that up on Jira
A.S.A.P i advise others in non operable ranges 82 , 83 i gather ?
To do the same .

/111/1e/181675/1.html#post1494903

Okee, now Linden really fixed the problem. No more 'get stuck'. wooooh.. great job.... thank you sooooo much that yo fixed the problem after 2 1/2 weeks. Now I cant log in at all.

So...my conection is from Brazil ....19 days:

+ I cant walk. only spin
+ I cant make local chat
+ I cant use IM with my friends list
+ My inventory is incomplete
+ I dont have my money


/

I was online all evening without any problems. Maybe I wasnt on bad sims so I go tomorrow especially trying out some bad sims. Fingers crossed!

Well guys, my conclusion: We are stupids testing this shit without support. Second Life is a hoaxe. 20 days without play SL and, the bad, without support.

Yesterday evening and today I had NO problems!!! So I'm hoping the problem is solved by now...

This is now my problem too. Log in, and if I'm lucky I see my guy loaded (partly) and maybe some of the landscape. No friends list, no inventory, no map. The network monitor shows almost no traffic moving. After a little, I get a SL Not Responding.

On Comcast cable in Annapolis.

Or is it tragedy? Could use my home and all other "bad" sims...
Thanks, unknown magician!

Uhmm hope for all of you out there that still suffer -- the CAN and hopefully WILL cure you!

*blows wet kisses around and sees everyone duck in time*

For 2 days now I can move everywhere without problems in SL. I think the problem is solved. Why dont we receive what they did to let SL work for also like normal?
Anyway I'm hoping it stays this way.

Yes, the pings now are stable and my home does not kick me out after 20 seconds!
Thanks Samantha for posting this thread and all those whose knowledge is far beyond this one.

Cheers, Pillah

Don't know if I missed something and maybe nobody is reading this thread anymore, but I like to know what was the solution of our problems. Anyone knows and wanna publish it here?

Yes! Problem solved!
I also like to know what was the solution of our problem??? Anyone???

As long as we don't know how it was solved, we don't have any guarantee it will not come back...

This was posted on Jira by Sean Linden:

----------------------------------------------
Sean Linden [07/May/07 11:30 AM]
Hi folks. I'm the guy who's been working on this issue.

The problem has never been with Sprintlink, because the XS4ALL networks for which traffic is routed back from us via Sprintlink have never appeared to have any problems. Only the networks for which the return path (toward XS4ALL) went via Hurricane Electric or Level3 were having issues. I can't imagine that this issue was due to the return path's being different because we have asymmetric routing all over the place and this is the first time we've seen this particualr problem. However, having Internap (the ISP in San Francisco which hosts the particular sim hosts on which people were seeing this issue) route all XS4ALL traffic back through Sprintlink seems to have resolved the issue for now.

By Friday all traffic whose routes originated with XS4ALL or Demon should have been going back through Sprintlink, which based on our current understanding of the problem should have resolved this issue for everyone on those ISPs. Unfortunately on Friday another of our ISPs, this one in Dallas, had some strange issues that seem to have been related to a bug or transient failure in one of their routers. I think this is probably the cause of most if not all of the issues people were seeing Friday. I spent most of the day Friday chasing down that issue.

Please post a comment if you continue to see issues on XS4ALL or Demon that seem to be the same issue, i.e. getting disconnected from a region after a while along with high ping and packet loss, *not* login issues or other issues from the 5/4 comments which should be unrelated. My goal this week is to try to actually figure out exactly what was going wrong, since it's not clear yet if it's reordering or duplication of UDP packets (my pet theory), fragmentation, or something else entirely.

Thank you so much for you patience, and I'm sorry that I wasn't able to jump on this harder/sooner; it's a very weird and subtle issue that doesn't show up at the network level (i.e. ping and traceroute were fine).

[ Show » ] Sean Linden [07/May/07 11:30 AM] Hi folks. I'm the guy who's been working on this issue. The problem has never been with Sprintlink, because the XS4ALL networks for which traffic is routed back from us via Sprintlink have never appeared to have any problems. Only the networks for which the return path (toward XS4ALL) went via Hurricane Electric or Level3 were having issues. I can't imagine that this issue was due to the return path's being different because we have asymmetric routing all over the place and this is the first time we've seen this particualr problem. However, having Internap (the ISP in San Francisco which hosts the particular sim hosts on which people were seeing this issue) route all XS4ALL traffic back through Sprintlink seems to have resolved the issue for now. By Friday all traffic whose routes originated with XS4ALL or Demon should have been going back through Sprintlink, which based on our current understanding of the problem should have resolved this issue for everyone on those ISPs. Unfortunately on Friday another of our ISPs, this one in Dallas, had some strange issues that seem to have been related to a bug or transient failure in one of their routers. I think this is probably the cause of most if not all of the issues people were seeing Friday. I spent most of the day Friday chasing down that issue. Please post a comment if you continue to see issues on XS4ALL or Demon that seem to be the same issue, i.e. getting disconnected from a region after a while along with high ping and packet loss, *not* login issues or other issues from the 5/4 comments which should be unrelated. My goal this week is to try to actually figure out exactly what was going wrong, since it's not clear yet if it's reordering or duplication of UDP packets (my pet theory), fragmentation, or something else entirely. Thank you so much for you patience, and I'm sorry that I wasn't able to jump on this harder/sooner; it's a very weird and subtle issue that doesn't show up at the network level (i.e. ping and traceroute were fine).

See https://jira.secondlife.com/browse/SVC-124
Maybe Sean Linden is coming soon with an answer ...
What did Timo (XS4all) said now about the problem (or the solution)?

Anyone knows?

Yesterday 5-8-2007 all well, today after 2- 3 minutes :
Unable to create requested object....Then down.
anyone else with this new phenomene?