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

Forums › Slingshot and CallPlus › slingshot 35% - 40% packetloss to slingshot website and dns servers

skiik

17 posts

Geek

Topic # 14368 30-Jun-2007 11:48
My slingshot internet got connected yesterday (30/06/2007) and it is soooooo slow. I know there is already a thread about bandwidth issues to international sites, however my problem are affecting everything, onliine local gaming, vpn access to work, remote desktop, vnc. I being a IT geek need to remote into pcs at work, which are all hosted in New Zealand. The 35% - 40% packetloss is bringing my connection to worse than dialup speeds. Get disconnected every few minutes assuming the connection/authentication handshaking can complete with the high packetloss. Anyway i called slingshot and they were like "Ummmmmmmmm, leave it with us". I asked if someone would be in contact to let me know the situation, they said "Ummm no, you just call back if the problem continues, we have logged a job". I said well umm so should i just call back everyday and see what the next operator has to say. They replied "Oh no sir, second level tech support dont work on the weekends". :/ Anyway i just wanted to know if this packetloss is specific to me, or are other people suffering the same problem. I am in Palmerston North area, and the command i ran was ping www.slingshot.co.nz /n 100 >c:\packetloss.txt ping 202.180.64.9 /n 100 >c:\packetloss2.txt If others could post their output, i would be much appreciated. I am beginning to wonder if slingshot is worth its trouble. I know its only been 1 day since its been connected, however it seems they are a bit disorganized and have some issues with their business processes that affect customer service. Too many techies, and not enough Business analysts in my opinion. Below is a paste of my ping results to their dns server. have tested with two dsl modems, with computer connected directly to the router, and all over phone accessories unplugged. Also there is no extension cord from the wall outlet to the router. I also tested on multiple computers Pinging 202.180.64.9 with 32 bytes of data: Request timed out. Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=48ms TTL=60 Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=51ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=60ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=57ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=58ms TTL=60 Reply from 202.180.64.9: bytes=32 time=63ms TTL=60 Request timed out. Request timed out. Reply from 202.180.64.9: bytes=32 time=64ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=54ms TTL=60 Reply from 202.180.64.9: bytes=32 time=63ms TTL=60 Reply from 202.180.64.9: bytes=32 time=77ms TTL=60 Reply from 202.180.64.9: bytes=32 time=90ms TTL=60 Reply from 202.180.64.9: bytes=32 time=66ms TTL=60 Reply from 202.180.64.9: bytes=32 time=55ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=55ms TTL=60 Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=73ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=48ms TTL=60 Request timed out. Request timed out. Reply from 202.180.64.9: bytes=32 time=80ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=49ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=61ms TTL=60 Reply from 202.180.64.9: bytes=32 time=52ms TTL=60 Reply from 202.180.64.9: bytes=32 time=56ms TTL=60 Reply from 202.180.64.9: bytes=32 time=66ms TTL=60 Reply from 202.180.64.9: bytes=32 time=51ms TTL=60 Reply from 202.180.64.9: bytes=32 time=69ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=63ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=57ms TTL=60 Request timed out. Request timed out. Reply from 202.180.64.9: bytes=32 time=55ms TTL=60 Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=63ms TTL=60 Reply from 202.180.64.9: bytes=32 time=56ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=51ms TTL=60 Reply from 202.180.64.9: bytes=32 time=53ms TTL=60 Reply from 202.180.64.9: bytes=32 time=54ms TTL=60 Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Request timed out. Request timed out. Reply from 202.180.64.9: bytes=32 time=60ms TTL=60 Reply from 202.180.64.9: bytes=32 time=96ms TTL=60 Reply from 202.180.64.9: bytes=32 time=63ms TTL=60 Reply from 202.180.64.9: bytes=32 time=52ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=53ms TTL=60 Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=53ms TTL=60 Reply from 202.180.64.9: bytes=32 time=52ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=51ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=49ms TTL=60 Reply from 202.180.64.9: bytes=32 time=50ms TTL=60 Reply from 202.180.64.9: bytes=32 time=51ms TTL=60 Request timed out. Request timed out. Reply from 202.180.64.9: bytes=32 time=52ms TTL=60 Reply from 202.180.64.9: bytes=32 time=54ms TTL=60 Request timed out. Request timed out. Reply from 202.180.64.9: bytes=32 time=54ms TTL=60 Reply from 202.180.64.9: bytes=32 time=54ms TTL=60 Reply from 202.180.64.9: bytes=32 time=57ms TTL=60 Request timed out. Request timed out. Reply from 202.180.64.9: bytes=32 time=61ms TTL=60 Request timed out. Request timed out. Reply from 202.180.64.9: bytes=32 time=51ms TTL=60 Request timed out. Request timed out. Reply from 202.180.64.9: bytes=32 time=52ms TTL=60 Request timed out. Reply from 202.180.64.9: bytes=32 time=52ms TTL=60 Ping statistics for 202.180.64.9: Packets: Sent = 100, Received = 65, Lost = 35 (35% loss), Approximate round trip times in milli-seconds: Minimum = 48ms, Maximum = 96ms, Average = 56ms

1 | 2

BDFL
43665 posts

Uber Geek

Administrator

Trusted

Geekzone

Subscriber

Reply # 76363 30-Jun-2007 12:05
As a benchmark I did the PING To the 202.180.64.9 server from my TCL connection and got 100% ok, minimum 18ms, maximum 46 ms, average 20 ms. The slowest pings from TCL to this server are much better than any of your faster pings. Now back to someone that can actually help debugging this... Mauricio Freitas (Geekzone Admin, Devil's Advocate, my blog, technology disclosure, my tweets, Web Performance Optimization) Geekzone Price comparison \| Amazon Kindle order page \| How to get the best out of Geekzone \| New Zealand IT Jobs \| Geekzone News \| Jinglebugs

Hypernova

50 posts

Geek

Reply # 76371 30-Jun-2007 12:57
Same is happening to me since 3 days ago.

skiik

17 posts

Geek

Reply # 76373 30-Jun-2007 15:09
When you say same thing is happening to you, do you you also get high packetloss pinging slingshot servers using a slingshot internet connection? Or are you talking about packetloss connecting to other websites? Hypernova: Same is happening to me since 3 days ago.

stuzzo

491 posts

Ultimate Geek

Reply # 76374 30-Jun-2007 15:28
Ping statistics for 202.180.68.145: Packets: Sent = 100, Received = 56, Lost = 44 (44% loss), Approximate round trip times in milli-seconds: Minimum = 59ms, Maximum = 69ms, Average = 63ms My Slingshot connection currently.

awew0lf

4 posts

Wannabe Geek

Reply # 76393 30-Jun-2007 18:54
Slingshot are having major probs and they gave me 20$ to my next bill dont believe that they dont know cause they do know about ther probs kk

skiik

17 posts

Geek

Reply # 76400 30-Jun-2007 19:43
Im glad someone knows they are having problems. when i spoke to them, its like asking me for modem up/down speeds, traceroutes, and outputs. I hope they get it sorted soon, else its prolly off to telstraclear, which offers a similar chargin structure as slingshot. awew0lf: Slingshot are having major probs and they gave me 20$ to my next bill dont believe that they dont know cause they do know about ther probs kk

Spyware

957 posts

Ultimate Geek

Subscriber

Reply # 76414 30-Jun-2007 21:35
Disconnection problems will likely exist with any provider and are caused by a line or exchange equipment fault. Ross ADSL2+ sync (Kbps): 11577/945, attenuation (dB): 33.0/16.9, Noise margin (dB): 11.5/11.5

skiik

17 posts

Geek

Reply # 76420 30-Jun-2007 22:27
Only two problems with that reasoning. 1. We are not talking about disconnection problems, we are talking about packetloss 2. Had a slingshot customer on another fourm reply who lives in christchurch with the same packet loss issues. Actually many slingshot customers nationwide are having the same problem. Im actually a bit relived it is a slingshot problem. I originally thought it was just me. If it was just me, i could easily expect a few weeks of back and forth with Telecom and slingshot both blaming each other. It seems to be the norm in the ISP industry. Spyware: Disconnection problems will likely exist with any provider and are caused by a line or exchange equipment fault.

Spyware

957 posts

Ultimate Geek

Subscriber

Reply # 76423 30-Jun-2007 23:19
On initial reading of the post I thought you were implying disconnection issues also. My apologies. Maybe you can identify the node at which the packet loss is occurring. Tracing route to ns.tranzpeer.net [202.180.64.9] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.1 2 48 ms 64 ms 45 ms 222-154-128-1.jetstream.xtra.co.nz [222.154.128.1] 3 73 ms 253 ms 212 ms fid-dom.aksw7.global-gateway.net.nz [202.50.245.194] 4 66 ms 66 ms 65 ms v282.aksw7.global-gateway.net.nz [202.50.245.193] 5 64 ms 66 ms 65 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202.49] 6 64 ms 66 ms 64 ms g1-0-0-4.akpr1.global-gateway.net.nz [210.55.202.52] 7 76 ms 67 ms 67 ms g1-0-0-906.u11.telstraclear.net [203.98.18.65] 8 65 ms 69 ms 66 ms jcore2-ge-0-2-0-927-acld.auckland.clix.net.nz [218.101.61.14] 9 70 ms 66 ms 64 ms ge-1-0-0-927.ie1.telstraclear.net [218.101.61.8] 10 66 ms 69 ms 69 ms 203.167.221.213 11 66 ms 71 ms 68 ms 202.180.65.20 12 69 ms 67 ms 69 ms ns.tranzpeer.net [202.180.64.9] Trace complete. Ross ADSL2+ sync (Kbps): 11577/945, attenuation (dB): 33.0/16.9, Noise margin (dB): 11.5/11.5

cokemaster

Nate wants an iphone
3842 posts

Uber Geek

Mod Emeritus

Trusted

Subscriber

Reply # 76424 30-Jun-2007 23:29
We've been having problems here with slingshot now and then... at the moment it appears to be fine with our two lines here, although the slingshot connection is always having higher pings than my Xtra connection (coming in the same household/room) slingshot: Ping statistics for 202.180.64.9: Packets: Sent = 100, Received = 99, Lost = 1 (1% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 452ms, Average = 58ms Xtra: Ping statistics for 202.180.64.9: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 67ms, Average = 30ms webhosting \|New Zealand connections \| geekzone IRC chat Loose lips may sink ships - Be smart - Don't post internal/commercially sensitive or confidential information!

skiik

17 posts

Geek

Reply # 76426 30-Jun-2007 23:33
droool 1% packetloss. Id pay good money for that. I think i have a way narrow the problem down. Ill tracert the dns server and do a n 100 ping test on each node to see if i can identify the node causing the issue. If even the first node has errors, more likely something wrong at the exchange. cokemaster: We've been having problems here with slingshot now and then... at the moment it appears to be fine with our two lines here, although the slingshot connection is always having higher pings than my Xtra connection (coming in the same household/room) slingshot: Ping statistics for 202.180.64.9: Packets: Sent = 100, Received = 99, Lost = 1 (1% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 452ms, Average = 58ms Xtra: Ping statistics for 202.180.64.9: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 67ms, Average = 30ms

skiik

17 posts

Geek

Reply # 76450 1-Jul-2007 11:20
Can i get some people to help me diagnose the problem. using my broken slingshot connection i get about 26% packetloss pinging 202.180.81.28 with a count of 50 could someone else run this as well. the command is ping 202.180.81.28 /n50 and post your results, and your isp. This may be able to help me determine weather or not it is a problem at the exchange. Regards

allstarnz

1616 posts

Uber Geek

Trusted

Reply # 76452 1-Jul-2007 11:30
Ihug, north west Palmerston North Ping statistics for 202.180.81.28: Packets: Sent = 50, Received = 49, Lost = 1 (2% Approximate round trip times in milli-seconds: Minimum = 55ms, Maximum = 803ms, Average = 71ms

cokemaster

Nate wants an iphone
3842 posts

Uber Geek

Mod Emeritus

Trusted

Subscriber

Reply # 76455 1-Jul-2007 11:34
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 Xtra 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 = 3ms, Maximum = 63ms, Average = 29ms Xtra connection (attempt 2) Ping statistics for 202.180.81.28: Packets: Sent = 50, Received = 50, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 69ms, Average = 29ms Could be something specific in your area, however it is worth noting that on my slingshot connection which wiring mirrors the Xtra, the slingshot connection almost always gets higher pings or higher percentages of time out error messages than the Xtra connection. Unfortunately, I do not have other ISP connections here except for my EVDO, GPRS and HSPDA connections which would beat the averages set by slingshot above. webhosting \|New Zealand connections \| geekzone IRC chat Loose lips may sink ships - Be smart - Don't post internal/commercially sensitive or confidential information!

skiik

17 posts

Geek

Reply # 76464 1-Jul-2007 12:35
Thanks guys for your replies. The feedback would strongly suggest there is something with my connection specific, and likely a problem at the exchange setup. That ip address i asked you guys to test was the slingshot gateway server my router uses for all traffic. The fact that im getting packetloss pinging it whereas nobody else is suggests the problem is being caused between my router and the gateway server. :/

1 | 2