Jump to content

Network related issue

Vermus Dryke

By Vermus Dryke,
in Second Life Server

 Share
You are about to reply to a thread that has been inactive for 3699 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Vermus Dryke

Vermus Dryke

Posted
Posted

I have experiencing an issue with connectivity to SL; in this case it causes my ping to rise to somewhat ridiculous levels before settling, my usual ping is between 175-225 but now the ping races up to sometimes 900+ for up to a few seconds. This has been going on for almost three months and I have run numerous checks with my ISP who tell me there is nothing wrong with the line and service,  I believe I have found the reason for my problem but I'm unsure what could be causing it. I am in the UK and on a wired connection and depending upon rolling restarts I get 22-23 hops to the region I'm on when I test using CMD program.

 In all tests now the 21st and 22nd hop both register as; Request Timed out.


In this case below I ran a Tracert to my home sim Minten:

Tracing route to sim10265.agni.lindenlab.com [216.82.49.187]
over a maximum of 30 hops:

 
  2    35 ms    36 ms    35 ms  217.32.98.186
  3    41 ms    40 ms    38 ms  217.32.98.161
  4    37 ms    35 ms    34 ms  213.1.69.70
  5    41 ms    38 ms    40 ms  217.41.168.102
  6    37 ms    36 ms    36 ms  217.41.168.145
  7    37 ms    39 ms    39 ms  217.41.168.107
  8    37 ms    37 ms    37 ms  109.159.249.122
  9    41 ms    38 ms    40 ms  core1-te0-0-0-5.faraday.ukcore.bt.net [109.159.2
49.43]
 10    37 ms    36 ms    37 ms  peer2-xe8-1-0.telehouse.ukcore.bt.net [109.159.2
55.101]
 11    36 ms    36 ms    34 ms  t2c3-xe-0-2-0-0.uk-lon1.eu.bt.net [166.49.211.17
0]
 12    41 ms    39 ms    40 ms  195.66.224.130195.66.224.130
 13   136 ms   133 ms   131 ms  vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
 14   188 ms   193 ms   190 ms  te-3-0-0.rar3.washington-dc.us.xo.net [207.88.12
.74]
 15   189 ms   186 ms   183 ms  207.88.12.99.ptr.us.xo.net [207.88.12.99]
 16   186 ms   183 ms   206 ms  207.88.12.128.ptr.us.xo.net [207.88.12.128]
 17   197 ms   192 ms   188 ms  207.88.12.96.ptr.us.xo.net [207.88.12.96]
 18   190 ms   241 ms   185 ms  ae0d0.mcr2.phoenix-az.us.xo.net [216.156.0.134]

 19   188 ms   187 ms   187 ms  ip67-155-242-74.z242-155-67.customer.algx.net [6
7.155.242.74]
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22   190 ms   185 ms   185 ms  sim10265.agni.lindenlab.com [216.82.49.187]

Trace complete.

 

Any idea what could be causing those two hops to simply not respond?

Link to comment
Share on other sites
Theresa Tennyson

Theresa Tennyson

Posted
Posted

Vermus Dryke wrote:

I have experiencing an issue with connectivity to SL; in this case it causes my ping to rise to somewhat ridiculous levels before settling, my usual ping is between 175-225 but now the ping races up to sometimes 900+ for up to a few seconds. This has been going on for almost three months and I have run numerous checks with my ISP who tell me there is nothing wrong with the line and service,  I believe I have found the reason for my problem but I'm unsure what could be causing it. I am in the UK and on a wired connection and depending upon rolling restarts I get 22-23 hops to the region I'm on when I test using CMD program.

 In all tests now the 21st and 22nd hop both register as; Request Timed out.

 

In this case below I ran a Tracert to my home sim Minten:

Tracing route to sim10265.agni.lindenlab.com [216.82.49.187]

over a maximum of 30 hops:

 

 

  2    35 ms    36 ms    35 ms  217.32.98.186

  3    41 ms    40 ms    38 ms  217.32.98.161

  4    37 ms    35 ms    34 ms  213.1.69.70

  5    41 ms    38 ms    40 ms  217.41.168.102

  6    37 ms    36 ms    36 ms  217.41.168.145

  7    37 ms    39 ms    39 ms  217.41.168.107

  8    37 ms    37 ms    37 ms  109.159.249.122

  9    41 ms    38 ms    40 ms  core1-te0-0-0-5.faraday.ukcore.bt.net [109.159.2

49.43]

 10    37 ms    36 ms    37 ms  peer2-xe8-1-0.telehouse.ukcore.bt.net [109.159.2

55.101]

 11    36 ms    36 ms    34 ms  t2c3-xe-0-2-0-0.uk-lon1.eu.bt.net [166.49.211.17

0]

 12    41 ms    39 ms    40 ms 
195.66.224.130
195.66.224.130

 13   136 ms   133 ms   131 ms  vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]

 14   188 ms   193 ms   190 ms  te-3-0-0.rar3.washington-dc.us.xo.net [207.88.12

.74]

 15   189 ms   186 ms   183 ms  207.88.12.99.ptr.us.xo.net [207.88.12.99]

 16   186 ms   183 ms   206 ms  207.88.12.128.ptr.us.xo.net [207.88.12.128]

 17   197 ms   192 ms   188 ms  207.88.12.96.ptr.us.xo.net [207.88.12.96]

 18   190 ms   241 ms   185 ms  ae0d0.mcr2.phoenix-az.us.xo.net [216.156.0.134]

 

 19   188 ms   187 ms   187 ms  ip67-155-242-74.z242-155-67.customer.algx.net [6

7.155.242.74]

 20     *        *        *     Request timed out.

 21     *        *        *     Request timed out.

 22   190 ms   185 ms   185 ms  sim10265.agni.lindenlab.com [216.82.49.187]

 

Trace complete.

 

Any idea what could be causing those two hops to simply not respond?
Call
Send SMS
Add to Skype
You'll need Skype Credit
Free via Skype

It's pretty common to see timeouts on the last hops before the Lab servers during a ping test. Some applications can detect ping test packets and give them lower priority than "real" traffic.

Your problems are probably happening somewhere between your ISP and Linden Lab. For long-distance communication, your packets will travel on a route determined by the contracts your ISP has with "backbone" providers - in your case, it appears they're using "xo.net". It's like "code-sharing" when you buy airline tickets and you're actually flying on a different airline from the one you bought the ticket from. It sounds like xo.net may be having intermittent issues somewhere in their network and there's little your ISP can do about that directly.

Link to comment
Share on other sites
Vermus Dryke

Vermus Dryke

Posted
  • Author
Posted

I see but is there any way at all I can try and resolve this issue? These days it feels like it's getting worse each day. I try resetting my modem hoping this will in some way help elliviate the issue but my hopes are dashed when I go in-world and see it continuing.

 I like Second life a lot and it's frustrating that seemingly no one else is getting this issue except for me.

 Would talking to my ISP help settle this issue?

Link to comment
Share on other sites
Nova Convair

Nova Convair

Posted
Posted

Not every node answers your trace, so there is a time out.

Even if there is a high difference between min and max that doesnt say much since ping and trace packets have the lowest priority and may even get dropped.

So your trace shows nothing of interest. Looks all good and will not help at your problem.

Link to comment
Share on other sites
You are about to reply to a thread that has been inactive for 3699 days.

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
 Share
Go to topic listing
×
×
  • Create New...