slingshot 35% - 40% packetloss to slingshot website and dns servers

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › slingshot 35% - 40% packetloss to slingshot website and dns servers

1 | 2

stuzzo

534 posts

Ultimate Geek

#76467 1-Jul-2007 13:15

cokemaster: As requested:

All tests were conducted from the same location less than 500 meters away from the Royal Oak exchange located on Mt Albert Road here in Auckland. Same wiring, config etc.

Slingshot connection (attempt 1):
Ping statistics for 202.180.81.28:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 2520ms, Average = 949ms
Slingshot connection (attempt 2):
Ping statistics for 202.180.81.28:
Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 2390ms, Average = 867ms

I assume there must be different settings for packet time-out periods which could explain why ping times are so long in this case but packet-loss is low eg My connection wouldn't have allowed a 2.3 sec ping time.

CerealKilla

1 post

Wannabe Geek

#76535 2-Jul-2007 00:46

Most things seem fine to me (internet is a lil slow), however when i play WoW i seem to get massive lag and get disconnected.

I'm with slingshot in Te Awamutu and haven't had any problems until a few days ago.

Ran a trace to the IP that guy suddested:

Ping statistics for 202.180.81.28:

    Packets: Sent = 50, Received = 38, Lost = 12 (24% loss),

Approximate round trip times in milli-seconds:

    Minimum = 49ms, Maximum = 54ms, Average = 51ms

When i try the logon servers its even worse:

Tracing route to us.logon.worldofwarcraft.com [12.129.232.113]

over a maximum of 30 hops:

1     1 ms    <1 ms    <1 ms mygateway1.ar7 [10.1.1.1]

2     *        *        *     Request timed out.

3     *        *        *     Request timed out.

4     *        *        *     Request timed out.

5     *        *        *     Request timed out.

6     *        *        *     Request timed out.

7     *        *        *     Request timed out.

8     *        *        *     Request timed out.

9     *        *        *     Request timed out.

10     *        *        *     Request timed out.

11     *        *        *     Request timed out.

12     *        *        *     Request timed out.

13     *        *        *     Request timed out.

etc

skiik

17 posts

Geek

#76536 2-Jul-2007 03:11

Thats weird cerealKilla, you have the same problem as me. That ip address is the first hop out on slingshot gateway, theres another slingshot gateway router that we pass through too which adds about the same percentage packetloss. between the two hops we end up with about 40% packetloss which will kill any online gaming, voip, etc and make web surfing slow. Some webpages you will have to rety a few times. Packetloss is probably the worse thing you can have apart from no connection at all. To think of it in simple terms, its actually more complicated that this, its like every 3rd character you type in a post getting dropped.

All my traffic jumps through the below two servers before reaching out:
3     *        *       51 ms p28.cpiak1-l6.tranzpeer.net [202.180.81.28]
4    51 ms    50 ms    50 ms 202-180-83-133.tangent-cust.commverge.net.nz [202.180.83.133]

my packetloss to the first gateway is:

Ping statistics for 202.180.81.28:
    Packets: Sent = 50, Received = 37, Lost = 13 (26% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 51ms, Average = 49ms

my packetloss to the second gateway is:

Ping statistics for 202.180.83.133:
    Packets: Sent = 50, Received = 32, Lost = 18 (36% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 104ms, Average = 52ms

It is interesting that it is only affecting some slingshot customers. That makes no sense at all to me.

CerealKilla: Most things seem fine to me (internet is a lil slow), however when i play WoW i seem to get massive lag and get disconnected.

I'm with slingshot in Te Awamutu and haven't had any problems until a few days ago.

Ran a trace to the IP that guy suddested:

Ping statistics for 202.180.81.28:

Packets: Sent = 50, Received = 38, Lost = 12 (24% loss),

Approximate round trip times in milli-seconds:

Minimum = 49ms, Maximum = 54ms, Average = 51ms

When i try the logon servers its even worse:

Tracing route to us.logon.worldofwarcraft.com [12.129.232.113]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms mygateway1.ar7 [10.1.1.1]

2 * * * Request timed out.

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 * * * Request timed out.

13 * * * Request timed out.

etc

gardner

13 posts

Geek

Lifetime subscriber

#76538 2-Jul-2007 08:33

I have been experiencing the same packet and frequent DSL Carrier loss for about a week now.

I live in Nelson near The Brook.

boulder:~ gardner$ traceroute slingshot.co.nz
traceroute to slingshot.co.nz (202.180.68.145), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2.196 ms 1.134 ms 1.056 ms
2 mygateway1.ar7 (10.1.1.1) 7.509 ms 22.257 ms 1.835 ms
3 * p28.cpiak1-l6.tranzpeer.net (202.180.81.28) 76.531 ms 75.543 ms
4 202-180-83-133.tangent-cust.commverge.net.nz (202.180.83.133) 75.917 ms * *
5 ad2.akl.tranzpeer.net (202.180.66.162) 75.099 ms * 76.142 ms
boulder:~ gardner$ ping -q -c 100 202.180.81.28
PING 202.180.81.28 (202.180.81.28): 56 data bytes

--- 202.180.81.28 ping statistics ---
100 packets transmitted, 78 packets received, 22% packet loss
round-trip min/avg/max/stddev = 71.735/78.589/185.876/18.778 ms
boulder:~ gardner$ cat /etc/resolv.conf
nameserver 202.180.64.2
nameserver 202.180.64.9
nameserver 10.1.1.1
boulder:~ gardner$ ping -q -c 100 202.180.64.2
PING 202.180.64.2 (202.180.64.2): 56 data bytes

--- 202.180.64.2 ping statistics ---
100 packets transmitted, 49 packets received, 51% packet loss
round-trip min/avg/max/stddev = 71.144/79.103/198.514/21.917 ms
boulder:~ gardner$

And my dlink DSL-504t modem reports the following line statistics:

Item	Downstream	Upstream	Unit
SNR Margin	12	24	dB
Line Attenuation	30	18	dB
Data Rate	7488	160	kbps

I have run tests with a brand new modem with similar results.

Here is a link to a recent log file from my router: http://spunts.com/savelog.txt

The connection is unusable.

Oyajipunk

28 posts

Geek

#76607 2-Jul-2007 15:49

Here is the response to my mail to the Slingshot help desk yesterday:

"We had issues with latency and packet loss. This should be resolved as of 1pm today. Please restart your router after this time. If you continue to experience problems please contact us again."

For what it is worth, I made a computer to phone call to the UK on Skype last night at 11PM and the call quality was perfect.

Maybe things will get better, we'll have to wait and see.

gardner

13 posts

Geek

Lifetime subscriber

#76615 2-Jul-2007 17:03

They definitely did something:

boulder:~ gardner$ ping -q -c 100 202.180.81.28
PING 202.180.81.28 (202.180.81.28): 56 data bytes

--- 202.180.81.28 ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 73.001/81.404/152.211/11.839 ms
boulder:~ gardner$

stuzzo

534 posts

Ultimate Geek

#76618 2-Jul-2007 17:35

ping slingshot.co.nz /n 50

Pinging slingshot.co.nz [202.180.68.145] with 32 bytes of data:

Ping statistics for 202.180.68.145:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 67ms, Average = 63ms

Why is it you have to get nasty to get things done, just saying please never works!

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

Oyajipunk

28 posts

Geek

#76717 3-Jul-2007 12:41

I think this constitutes what is commonly known as a happy ending.

I hope people in the other threads about slingshot are reading this.

skiik

17 posts

Geek

#76804 3-Jul-2007 21:01

Yep, all we need now is the ability to turn off interleaving like you can on other ISP's :)

1 | 2