Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Unable to move

Colin Splash
Registered User
Join date: 5 Mar 2006
Posts: 3
04-26-2007 13:53
!!##@#@@!@$@@$$@@!! Sorry
Annabelle you can see the in the top of your screen en in the help/about window. Somewhere in this post a website is mention where you can lookup sims.
Geeyz XS4all how hard is it to recognize that it is your resonsibility? Since only YOUR customers are suffering from problems. And why the f**k did it work this afternoon? do we have ping logs of people connecting to bad sims which have other ISP then xs4all. Paying the most getting the least nice slogan xs4all!!!
Annabelle Fleury
Registered User
Join date: 9 Dec 2006
Posts: 22
if i can loggin I'll look
04-26-2007 14:17
Its very difficult for me to loggin since the .15 release. Anyone else having that trouble too? Tnx Colin for answering me about the sims, Ill look for it when I manage to get loggin. And I'm also sick and tired of those problems in SL whoever's fault it is.
Tameryn Banshee
I'm Lovin' It
Join date: 16 Jan 2006
Posts: 22
04-26-2007 14:54
From: Colin Splash
Geeyz XS4all how hard is it to recognize that it is your resonsibility? Since only YOUR customers are suffering from problems. And why the f**k did it work this afternoon? do we have ping logs of people connecting to bad sims which have other ISP then xs4all. Paying the most getting the least nice slogan xs4all!!!


Like mentioned several tiiiimes.. This is beyond xs4all's power to fix. Only way they can help is by contacting LL (which they've done a few days ago) and contacting the server hosts (I believe both LL and xs4all have contacted Sprintlink already, along with several of us) and find where the problem is. Second Life has been working on and off for us, it HAS worked for a few hours several times before, this isn't the first time (funny enough someone found out that during at least one moment where SL worked, Sprintlink was having an emergency maintenance so it could've been that we were put on another server.)

Also, it seems us Dutch aren't the only ones with problems. If you scroll back in this thread, you'll come along posts of someone from Brazil who has the exact same problems as we do, exactly down to the details and another, Denmark? I'm not sure you'd have to scroll back if you want to know.

Threatening, flaming, whatever won't turn on some turbo switch. And no I'm not defending, I just understand some situations may well be much more complex than they may seem, speaking out of experience. I, not sure if I'm the only one, am convinced this will get fixed, it just needs more time. (and yes, I *am* just as frustrated as everyone. cursing, flaming, etc. just won't help anything)

The issue is very frustrating to every single one of us. But it is being worked on from both xs4all's side and LL's, so Jira posts have told us. Apparently it's just a very complex situation.

*goes back to coding now*
_____________________
"You've dug your hole, now sleep in it."

"I wanted to walk through the empty streets,
And feel something constant under my feet,
But all the news reports recommended that I stay indoors."
Jos Young
Registered User
Join date: 11 Dec 2006
Posts: 22
An observation
04-26-2007 15:11
Round 21:15 dutch time (12:15 pm slt) I crashed from the beta grid and the problem reappeared again. This was round the time the main grid got back on line.

Just a while ago the main grid went off line again (0 logon). And guess: I can reach the beta grid again without any problem. No packet loss no freezing, just move around normally.

So I wonder, isn't this all just a capacity problem somewhere in the route?

Greetz,

Jos
Zho Golem
Registered User
Join date: 22 Oct 2005
Posts: 34
04-26-2007 15:15
Ok people, let's PLEASE stay on topic here, we want to get this resolved, we all have to think together and try to find the cause to this.

- As I said a few posts earlier, from my University the trace towards a bad sim takes nearly the exact same route through sprintlink, and I can move around just fine there. Not to mention the people from OTHER countries having the same problem but a completely different trace route. So it's not Sprintlink.

- As we also know, everything we DO in SL does happen, we just don't see it. After all, other people see us move and can hear what we say. However, we do not see these things happening ourselves. Thus - Data from SL never makes it back to us hence the Sims look like they're going down. After all, if the program gets no Data, it thinks it's not transmitting it in the first place

- Most people's traceroutes and pings occur wihout packetloss or too big of a delay. It's not our connection towards SL as we know it. Data from SL takes a different route back towards us?

Thus we must ask the question
What IS the traceroute from one of the bad sims towards any Xs4all user? And what is it from a good sim? Not to mention what they are during good times.

Edit: I just got the traceroute from Torley Linden. I will be posting my results shortly
Test Day
Registered User
Join date: 18 Apr 2007
Posts: 3
BBned or BabyXl?
04-26-2007 15:52
Are the problems with Xs4all (SL) on BBned or BabyXL?
Zho Golem
Registered User
Join date: 22 Oct 2005
Posts: 34
04-26-2007 16:51
Warning, huge post incoming. Text file available @ Jira.

//NB: Removed Pings for readability
//At time of writing, Second Life had the same errors. Unable to move and a
//disconnect soon after.

When tracing. I will go from closest (higher number) to farthest (lower number)

CODE

traceroute to 82.95.223.87 (82.95.223.87), 30 hops max, 46 byte packets
1 border2.g6-4.linden-11.sfo002.pnap.net (66.150.245.253)
2 core4.pc-2-bbnet2.sfo002.pnap.net (63.251.63.66)
3 border4.g2-5.sfo002-sje-336.sje.pnap.net (66.151.157.209)
4 core4.t6-2-bbnet2.sje.pnap.net (66.151.144.73)
5 cr1.sje007.inappnet-28.core4.sje.internap.net (66.79.148.129)
6 sjo-ix.he.net (206.223.116.37)
7 gige-g12-1-0.gsr12416.sjc2.he.net (72.52.81.182)
8 pos4-3.gsr12416.nyc.he.net (216.218.223.134)
9 pos0-1.gsr12416.lon.he.net (216.218.200.102)
10 pos3-1.core1.ams1.he.net (216.66.24.158)
11 154.41.66.216.in-addr.arpa (216.66.41.154)
12 0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)
13 0.so-0-0-0.xr3.3d12.xs4all.net (194.109.5.202)
14 te2-0-0.dr4.d12.xs4all.net (194.109.7.134)
15 * * *

Let's start with the above.
Doing a trace towards the destination (in this case number 1) 66.150.245.253
takes the usual path through Sprintlink. So instead I traced each IP
individually. The problem starts with
6 sjo-ix.he.net (206.223.116.37)
Trying to trace through the NAME will give the 'Cannot Resolve Hostname' error
But even worse tracing to the ping will show
CODE

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| . - 0 | 5 | 5 | 0 | 0 | 0 | 0 |
| 195.190.249.11 - 0 | 5 | 5 | 0 | 22 | 47 | 47 |
| 42.ge-4-0-0.xr1.3d12.xs4all.net - 0 | 5 | 5 | 0 | 37 | 93 | 0 |
| Network Unreachable - 100 | 5 | 0 | 0 | 0 | 0 | 15 |
|________________________________________________|______|______|______|____|______|______|

If I try to trace to the next step
5 cr1.sje007.inappnet-28.core4.sje.internap.net (66.79.148.129)
It will take a COMPLETELY different path through
CODE

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| . - 0 | 7 | 7 | 0 | 0 | 0 | 0 |
| 195.190.249.11 - 0 | 7 | 7 | 0 | 22 | 47 | 16 |
| 42.10ge-4-0-0.xr1.d12.xs4all.net - 0 | 7 | 7 | 0 | 13 | 31 | 15 |
| 0.so-7-0-0.xr1.sara.xs4all.net - 0 | 7 | 7 | 0 | 33 | 78 | 15 |
| so-7-0-0.nar1.AMS1.gblx.net - 0 | 7 | 7 | 0 | 35 | 93 | 15 |
| so2-1-0-2488M.ar1.DCA3.gblx.net - 0 | 7 | 7 | 79 | 105 | 141 | 93 |
|InterNAP-Ken-Schmid-Ashburn-3.ge-2-3-0.ar1.DCA3.gblx.net - 0 | 6 | 6 | 93 | 125 | 156 | 141 |
| core2.te5-2-bbnet2.wdc002.pnap.net - 0 | 6 | 6 | 110 | 140 | 157 | 125 |
|cr1.wdc005.inappnet-62.core2.wdc002.internap.net - 0 | 6 | 6 | 78 | 91 | 110 | 94 |
|cr1.sje007.inappnet-28.core4.sje.internap.net - 0 | 6 | 6 | 157 | 185 | 219 | 187 |
|________________________________________________|______|______|______|____|______|______|


Steps 5 through 3 take the same route as above, and step 2 goes through
Sprintlink again.

-----------------------------------------------------------------------------
-----------------------------------------------------------------------------

CODE

traceroute to 80.126.180.233 (80.126.180.233), 30 hops max, 46 byte packets
1 border2.g6-4.linden-11.sfo002.pnap.net (66.150.245.253)
2 core1.pc-2-bbnet2.sfo002.pnap.net (63.251.63.84)
3 cr1.sje007.inappnet-26.core4.sfo002.internap.net (66.79.148.133)
4 cr1-cr2.sje007.internap.net (66.79.146.189)
5 sjo-ix.he.net (206.223.116.37)
6 gige-g12-1-0.gsr12416.sjc2.he.net (72.52.81.182)
7 pos4-3.gsr12416.nyc.he.net (216.218.223.134)
8 pos0-1.gsr12416.lon.he.net (216.218.200.102)
9 pos3-1.core1.ams1.he.net (216.66.24.158)
10 154.41.66.216.in-addr.arpa (216.66.41.154)
11 0.so-6-0-0.xr1.3d12.xs4all.net (194.109.5.1)
12 42.10ge11-0-0.pe20.fia.xs4all.net (194.109.5.50)
42.10ge14-0-0.pe10.fia.xs4all.net (194.109.5.106)
42.10ge11-0-0.pe20.fia.xs4all.net (194.109.5.50)
13 195.190.249.13 (195.190.249.13)
14 * * *

This is the same route as the first, so see above for results


---------------------------------------------------------------
---------------------------------------------------------------


CODE

traceroute to 194.109.0.123 (194.109.0.123), 30 hops max, 46 byte packets
1 border2.g6-4.linden-11.sfo002.pnap.net (66.150.245.253)
2 core2.pc-2-bbnet2.sfo002.pnap.net (63.251.63.85)
3 ge-6-23.car2.SanFrancisco1.Level3.net (4.78.242.17)
4 ae-4-4.ebr2.SanJose1.Level3.net (4.69.133.158)
5 * ae-24-56.car4.SanJose1.Level3.net (4.68.123.174)
ae-24-52.car4.SanJose1.Level3.net (4.68.123.46)
6 gblx-level3-te.SanJose1.Level3.com (4.68.111.162)
7 146.82.33.178 (146.82.33.178)
8 0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)
9 0.so-7-0-0.xr1.tc2.xs4all.net (194.109.5.14)
10 * * *

Problems here start at number 6
6 gblx-level3-te.SanJose1.Level3.com (4.68.111.162)
CODE

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| . - 0 | 8 | 8 | 0 | 2 | 16 | 0 |
| 195.190.249.11 - 0 | 8 | 8 | 0 | 15 | 47 | 16 |
| 42.ge-4-0-0.xr1.3d12.xs4all.net - 0 | 7 | 7 | 0 | 13 | 31 | 15 |
| 0.so-6-0-0.xr1.tc2.xs4all.net - 0 | 7 | 7 | 16 | 24 | 47 | 16 |
| 217.149.46.21 - 0 | 7 | 7 | 63 | 116 | 250 | 250 |
| sl-bb21-ams-8-1.sprintlink.net - 0 | 7 | 7 | 15 | 31 | 79 | 31 |
| 213.206.131.46 - 0 | 7 | 7 | 0 | 24 | 62 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 110 |
|________________________________________________|______|______|______|____|______|______|

Bad sign again.

CODE

Number 5
5 * ae-24-56.car4.SanJose1.Level3.net (4.68.123.174)
takes a different route. And will give no errors or warnings.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| . - 0 | 14 | 14 | 0 | 8 | 109 | 0 |
| 195.190.249.11 - 0 | 13 | 13 | 0 | 28 | 78 | 15 |
| 42.ge-4-0-0.xr1.3d12.xs4all.net - 0 | 13 | 13 | 0 | 36 | 94 | 78 |
| 0.so-6-0-0.xr1.tc2.xs4all.net - 0 | 13 | 13 | 0 | 24 | 63 | 31 |
| 217.149.46.21 - 0 | 13 | 13 | 0 | 15 | 94 | 0 |
| sl-bb21-ams-8-0.sprintlink.net - 0 | 13 | 13 | 0 | 45 | 203 | 15 |
| 213.206.131.46 - 0 | 13 | 13 | 0 | 51 | 172 | 15 |
| ae-0-56.mp2.Amsterdam1.Level3.net - 0 | 13 | 13 | 0 | 43 | 203 | 47 |
| ae-0-0.bbr2.SanJose1.Level3.net - 8 | 13 | 12 | 156 | 171 | 235 | 156 |
| ae-24-56.car4.SanJose1.Level3.net - 8 | 13 | 12 | 156 | 199 | 359 | 359 |
|________________________________________________|______|______|______|____|______|______|



Number 4
4 ae-4-4.ebr2.SanJose1.Level3.net (4.69.133.158)

Will once again take a different route
CODE

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| . - 9 | 12 | 11 | 0 | 0 | 0 | 0 |
| 195.190.249.11 - 0 | 11 | 11 | 0 | 42 | 125 | 110 |
| 42.ge-5-0-0.xr1.3d12.xs4all.net - 0 | 11 | 11 | 15 | 52 | 125 | 62 |
| 0.so-6-0-0.xr1.tc2.xs4all.net - 0 | 11 | 11 | 0 | 39 | 157 | 0 |
| 217.149.46.21 - 0 | 11 | 11 | 0 | 29 | 93 | 0 |
| sl-bb21-ams-8-1.sprintlink.net - 0 | 11 | 11 | 0 | 66 | 234 | 234 |
| 213.206.131.46 - 0 | 11 | 11 | 0 | 52 | 218 | 16 |
| ae-32-56.ebr2.Amsterdam1.Level3.net - 0 | 11 | 11 | 0 | 52 | 109 | 94 |
| ae-2.ebr2.London1.Level3.net - 0 | 11 | 11 | 15 | 63 | 125 | 125 |
| ae-4.ebr1.NewYork1.Level3.net - 0 | 11 | 11 | 78 | 123 | 235 | 203 |
| ae-1-100.ebr2.NewYork1.Level3.net - 0 | 11 | 11 | 93 | 109 | 157 | 109 |
| ae-2.ebr1.Chicago1.Level3.net - 0 | 11 | 11 | 109 | 136 | 188 | 172 |
| ae-3.ebr2.Denver1.Level3.net - 0 | 11 | 11 | 140 | 170 | 234 | 188 |
| ae-1-100.ebr1.Denver1.Level3.net - 0 | 11 | 11 | 140 | 156 | 187 | 156 |
| ae-4-4.ebr2.SanJose1.Level3.net - 0 | 11 | 11 | 171 | 293 | 1156 | 1156 |
|________________________________________________|______|______|______|____|______|______|

Number 3
3 ge-6-23.car2.SanFrancisco1.Level3.net (4.78.242.17)
Will take the same route as number 4

And finally number 2
core2.pc-2-bbnet2.sfo002.pnap.net (63.251.63.85)
Will take the usual route through Sprintlink.

------------------------------------------------------------------------
------------------------------------------------------------------------
CODE

traceroute to 213.84.9.189 (213.84.9.189), 30 hops max, 46 byte packets
1 border2.g6-4.linden-11.sfo002.pnap.net (66.150.245.253) 0.329 ms 0.235 ms 0.239 ms
2 core4.pc-2-bbnet2.sfo002.pnap.net (63.251.63.66) 0.308 ms 0.588 ms 0.247 ms
3 border4.g2-4.sfo002-sje-335.sje.pnap.net (66.151.157.93) 81.523 ms 190.029 ms 2.493 ms
4 core2.t6-1-bbnet1.sje.pnap.net (66.151.144.2) 1.747 ms 1.762 ms 1.779 ms
5 sl-st21-sj-8-1-0.sprintlink.net (144.223.242.85) 1.917 ms 1.897 ms 1.790 ms
6 sl-bb25-sj-2-0.sprintlink.net (144.232.9.241) 2.455 ms 2.361 ms 2.275 ms
7 sl-bb22-sj-12-0.sprintlink.net (144.232.3.209) 2.548 ms 2.334 ms 2.295 ms
8 sl-bb22-rly-8-0-0.sprintlink.net (144.232.8.126) 77.422 ms 77.459 ms 77.507 ms
9 sl-bb26-rly-12-0.sprintlink.net (144.232.14.174) 70.707 ms 70.728 ms 70.726 ms
10 sl-bb20-rly-12-0.sprintlink.net (144.232.7.249) 75.978 ms 81.467 ms 70.679 ms
11 sl-bb20-tuk-11-0.sprintlink.net (144.232.20.137) 92.302 ms 92.114 ms 92.207 ms
12 sl-bb21-tuk-5-0-0.sprintlink.net (144.232.9.171) 92.043 ms 91.999 ms 91.949 ms
13 sl-bb21-lon-14-0.sprintlink.net (144.232.19.70) 161.160 ms 161.216 ms 161.058 ms
14 213.206.128.54 (213.206.128.54) 161.139 ms 162.495 ms 161.293 ms
15 213.206.129.142 (213.206.129.142) 168.743 ms 168.846 ms 168.629 ms
16 217.149.32.42 (217.149.32.42) 308.153 ms 169.165 ms 169.068 ms
17 217.149.46.22 (217.149.46.22) 169.234 ms 169.092 ms 169.168 ms
18 0.so-7-0-0.xr1.3d12.xs4all.net (194.109.5.9) 181.045 ms
0.so-7-0-0.xr2.3d12.xs4all.net (194.109.5.13) 169.281 ms
0.so-7-0-0.xr1.3d12.xs4all.net (194.109.5.9) 169.168 ms
19 42.10ge14-0-0.pe20.fia.xs4all.net (194.109.5.114) 169.103 ms
42.10ge11-0-0.pe20.fia.xs4all.net (194.109.5.50) 169.108 ms
42.10ge14-0-0.pe20.fia.xs4all.net (194.109.5.114) 169.184 ms
20 195.190.249.10 (195.190.249.10) 169.240 ms 169.398 ms 169.321 ms
21 * * *

This is the usual route we take through Sprintlink, only in reverse of course
nothing to comment here.
Algenight Cline
Shadow Walker
Join date: 30 Jun 2005
Posts: 14
04-27-2007 03:19
Just bumping this up cuz problems still don't seem to be fixed
Colin Splash
Registered User
Join date: 5 Mar 2006
Posts: 3
Sorry
04-27-2007 04:02
Sorry guys, just needed to vent 11 days of frustration. I'm luckily i renewed the lease for my house so its going strong again for 25 days. Zho thanks for your torough analysis! So we landed is DNS resolver cache hell is that it? Was my fear yesterday after i calmed down again... Apart from the post in later read about the rerouting while in maintenance. But now it seems other hops in the route BACK are to blame. Zho again thanks for your hard work. You must be a IT-person :-) I'm too but i only do client stuff, no DNS-tweaking for me ;-) Now hopefully they get the sync between all the DNS-servers to work correctly when they fix this else we're still in deep sh*t
Tara Tagore
Registered User
Join date: 19 Jul 2006
Posts: 20
04-27-2007 04:20
Ok on phone with xs4all ..according to this gentleman they are going to do nothing about it as the problem lays only with LL ................... the data that is coming back at us is the problem , so in essence he said the issue is with LL the data we are recieving back .. is insufficient and only they can resolve this .... so ..... i guess for me its time to find a new Provider
Pieter Fonda
Registered User
Join date: 16 Jan 2007
Posts: 8
04-27-2007 08:09
Just had a call from my new provider :-) (First time smilling in days) They are coming next wednesday.... I'll hope that's works..... But i keep supporting you guys!
Colin Splash
Registered User
Join date: 5 Mar 2006
Posts: 3
Sim/region info list
04-27-2007 08:09
Hi, i remember somebody saying something about a region/sim list with ip info in this thread, but i can't seem to find it any longer. Does anybody know if such a list is available? It was called something like Neighbouring sims list i think. Although i could have dreamt it, you never know... I found a regionlist with stats on slstats.com, but no ip-info is on thats list, and no way to find out if sims neighbour except looking at coordinates.
Mandy Lurra
Registered User
Join date: 8 Oct 2006
Posts: 39
04-27-2007 08:15
Why I am posting this I don't know. Maybe third time lucky ?

My connection is stable right now again. Both ping user, and ping sim are around 200 - 300. First time since the update.

Is it going to last, is the big question.
Cloudy Numbers
MF-Designs @ MANifesto
Join date: 7 Oct 2006
Posts: 64
04-27-2007 08:48
Still cant get into my homebases Eaton and Bluenose. Day 11. How many more to go
Mandy Lurra
Registered User
Join date: 8 Oct 2006
Posts: 39
04-27-2007 10:05
From: Mandy Lurra
Why I am posting this I don't know. Maybe third time lucky ?

My connection is stable right now again. Both ping user, and ping sim are around 200 - 300. First time since the update.

Is it going to last, is the big question.


WHY, oh why do I even bother. Almost 2 hours and all was perfect and now it's gone again. Ping user is straight back up to 10000 msec

*sigh*
Hoaghes Beaumont
Registered User
Join date: 5 Apr 2007
Posts: 7
04-27-2007 10:07
From: Mandy Lurra
WHY, or why do I even bother. Almost 2 hours and all was perfect and now it's gone again. Ping user is straight back up to 1000 msec

*sigh*



Same, problem is back for me as well :(

Time to start the helpdesk/support bugging routine all over again I suppose..

I really wonder how they can have fixed it and now broke it again after a day or so, stinks.
Tara Tagore
Registered User
Join date: 19 Jul 2006
Posts: 20
04-27-2007 10:08
Yup same here went down at 6.57 .... Bandwidth dropped to 0
GRRRRRRRrrrrrrrrrrrr * Reaches for a very large Gin&Tonic
Caitlin Lilliehook
Registered User
Join date: 28 Feb 2007
Posts: 20
04-27-2007 10:17
Same here..unable to move in some regions or the opposite...walk, walk, walk..unable to stop.....
Eurojojo Pinion
Registered User
Join date: 10 Feb 2007
Posts: 11
04-27-2007 11:53
I'm fine now. Wondering how long this will last, but for the moment I am enjoying life (and second life).
Bibi Olivier
Registered User
Join date: 6 Jan 2007
Posts: 3
04-27-2007 13:03
it starts all over
i was fine for two days.
until now
Iva Geesink
Registered User
Join date: 4 Jan 2007
Posts: 45
04-27-2007 15:35
Ok, this problem is going downhill fast:

The 64.129.x.x range (which has always been good) is suffering from the same problem now too right now !!!

Ow, while the 64.129.x.x is screwed now too (I'm on 64.129.46.27 right now), tracing shows this range is still going to Linden through cogento.

Another good argument why sprintlink can't be the problem, but something on the way back...
Annabelle Fleury
Registered User
Join date: 9 Dec 2006
Posts: 22
its now on my own isle Nephrite Island
04-27-2007 16:01
My island was all the time free of the packet lost and now since half an hour I have that problem all of a sudden there too (7.5%-3.5% never that high anywhere else before). Disconnected one time after another, i think maybe 10x in 15 minutes, very difficult to loggin again.
Why suddenly my own sim while before those 10 days no problems at all? Now i'm really desperate!!!!
Pieter Fonda
Registered User
Join date: 16 Jan 2007
Posts: 8
Cosentino dead too
04-27-2007 16:06
Yes, it's also here.... pfff Cosentino is a forbidden zone as well. The only advice i can give is look for an open wireless router of a kind neighbour and pray that he has another provider then XS4ALL.....

I'm done, for today... all sleep well and sweet dreams (not from SL and his problems!)
Maurice Wendt
Registered User
Join date: 22 Jun 2006
Posts: 16
04-27-2007 16:24
From: Iva Geesink
Ok, this problem is going downhill fast:

The 64.129.x.x range (which has always been good) is suffering from the same problem now too right now !!!

I can confirm this :(

I was just in Passion Park (in Cisco), located on sim3342.agni.lindenlab.com [64.129.45.107], wich is routed through Cogentco and I'm experiencing the exact same issues that formerly only existed on a server reached through Sprintlink.

Maybe LL is experimenting with their routing and they changed the route back to Xs4all to the wrong path?
Ruud Lathrop
Registered User
Join date: 4 May 2006
Posts: 11
04-27-2007 16:29
I think it is not the up stream to the server but the down stream that is screwed up. My girlfriend saw me moving while I didnt see anything. And this was also on my own sim. Whixh goes throw cogentco.

I also have a mall in thylacine. This is not bad for me, also a lot of packet lost but not that much that I lose connection.

It all started around 12 oclock my time.

Hope somebody can finally look into where the HARDWARE problem is.
1 ... 11 12 13 14 15 16 17 18 19 ... 22