[Snap] High latency, low throughput this weekend

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] High latency, low throughput this weekend

Elpie

1304 posts

Uber Geek

#94018 4-Dec-2011 13:45

I never thought I'd say this but I am seriously unhappy with Snap.

Starting Friday night my Net has been largely unusable. On Saturday, NZ traffic came back but international was crawling. This was the best speed I got all day yesterday.

Snap responded on Twitter to say, "we are experiencing some latency issues - techs are investigating at the moment".

Today is worse:

Two others also on Snap posted their results this afternoon:

There is currently a network status message up on the Snap site: http://www.snap.net.nz/support/network-status/62/3_12-@-2100-high-latency-and-low-throughput.html

Is this latency related to TelstraClear's uncapped weekend? Seems awfully coincidental. Whatever the reason, losing an entire weekend because international traffic is borked makes for at least one very unhappy customer.

1 | 2 | 3

65 posts

Master Geek

#553479 4-Dec-2011 13:49

Yup, on Snap and everything is running ridiculously slow... They use Telstra as their main upstream provider IIRC. Youtube is unusable even on 360p.
Serious BS that other ISP's have to suffer for Telstra's marketing stunt.

What
The
****

I don't mind if Telstra screw over speeds of their entire customer base with this free weekend, but this is just stupid.

GeoffisPure

459 posts

Ultimate Geek

#553507 4-Dec-2011 14:56

Yep... sure is a bit slow today...

RalphFromSnap

776 posts

Ultimate Geek

Trusted

Snap Internet

#553508 4-Dec-2011 14:57

Hey Elpie, if you could PM us your username or customer number I can get someone to call you!

Snap

0800 BROADBAND (276 232)
www.snap.net.nz

@SnapInternet on Twitter
Snap Internet on Facebook

Our Social Media Team:
^RO Ricky - Technical Lead
^AT Ashleigh - Retail Marketing Coordinator

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#553513 4-Dec-2011 15:09

Folks, I got some information Snap today about this... Basically (translating the info): there is a confirmed fault with Reach and that its being worked on. This is the causing issues for some customers and the increase in latency is impacting throughput on single TCP connections. In other words speed tests will be giving these shocking results but multiple streams should be able to get full speed as normal.

Snap is planning another free weekend at some stage very soon, and like the previous ones they don't expect the network to be impacted.

AviZ

214 posts

Master Geek
Inactive user

#553514 4-Dec-2011 15:11

I think everyone on snap are having issues, i have already called snap and they said hurry up and wait till monday.

AviZ

214 posts

Master Geek
Inactive user

#553520 4-Dec-2011 15:18

seeing i have a server in the usa, its unusable

DonGould

3892 posts

Uber Geek

#553521 4-Dec-2011 15:18

Reach problem? Is this being caused by the Telstra free weekend congesting the Reach ports?

I'd be interested to see a traceroute to 7206-gi-0-2.w-link.net to compare the path.

Is there a common Reach router in there that isn't dealing with the flood of traffic Telstra is throwing at it?

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

Lenovo

Shop now for Lenovo laptops and other devices (affiliate link).

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#553523 4-Dec-2011 15:22

No contacts within Reach (no pun intended), I'm afraid...

AviZ

214 posts

Master Geek
Inactive user

#553526 4-Dec-2011 15:26

C:\Users\Andrew>tracert 7206-gi-0-2.w-link.net

Tracing route to 7206-gi-0-2.w-link.net [207.244.149.46]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 15 ms 14 ms 15 ms 20.17.69.111.static.snap.net.nz [111.69.17.20]
3 14 ms 13 ms 14 ms 24.17.69.111.static.snap.net.nz [111.69.17.24]
4 * * * Request timed out.
5 29 ms 29 ms 29 ms 111-69-27-66.core.snap.net.nz [111.69.27.66]
6 95 ms 94 ms 94 ms 203.167.233.10
7 219 ms 218 ms 219 ms i-0-6-4-1.tlot-core01.bx.reach.com [202.84.142.114]
8 220 ms 220 ms 220 ms i-2-6.tlot03.bi.reach.com [202.84.251.150]
9 218 ms 217 ms 218 ms l3-peer.tlot03.pr.reach.com [134.159.62.14]
10 218 ms 218 ms 217 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]
11 219 ms 217 ms 218 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.17]
12 229 ms 230 ms 229 ms ae-6-6.ebr2.SanJose5.Level3.net [4.69.148.202]
13 233 ms 234 ms 234 ms ae-5-5.ebr4.SanJose1.Level3.net [4.69.148.142]
14 230 ms 229 ms 229 ms ae-34-34.ebr2.SanJose1.Level3.net [4.69.153.33]
15 259 ms 251 ms 251 ms ae-7-7.ebr1.Seattle1.Level3.net [4.69.132.50]
16 251 ms 250 ms 251 ms ae-13-51.car3.Seattle1.Level3.net [4.69.147.133]
17 251 ms 252 ms 251 ms metapeer.car3.Seattle1.Level3.net [4.71.152.18]
18 248 ms 248 ms 248 ms 208.99.192.65
19 249 ms 248 ms 248 ms 208.99.192.94
20 248 ms 248 ms 248 ms renbd1-gi-2-1.w-link.net [207.244.149.54]
21 251 ms 251 ms 251 ms botbd1-gi-4-2.w-link.net [207.244.149.33]
22 252 ms 253 ms 251 ms 7206-gi-0-2.w-link.net [207.244.149.46]

Trace complete.

C:\Users\Andrew>

DonGould

3892 posts

Uber Geek

#553531 4-Dec-2011 15:34

AviZ: C:\Users\Andrew>tracert 7206-gi-0-2.w-link.net

Tracing route to 7206-gi-0-2.w-link.net [207.244.149.46]
over a maximum of 30 hops:

1 1 ms 1 ms 2 15 ms 14 ms 15 ms 20.17.69.111.static.snap.net.nz [111.69.17.20]
3 14 ms 13 ms 14 ms 24.17.69.111.static.snap.net.nz [111.69.17.24]
4 * * * Request timed out.
5 29 ms 29 ms 29 ms 111-69-27-66.core.snap.net.nz [111.69.27.66]
6 95 ms 94 ms 94 ms 203.167.233.10
7 219 ms 218 ms 219 ms i-0-6-4-1.tlot-core01.bx.reach.com [202.84.142.114]
8 220 ms 220 ms 220 ms i-2-6.tlot03.bi.reach.com [202.84.251.150]
9 218 ms 217 ms 218 ms l3-peer.tlot03.pr.reach.com [134.159.62.14]
10 218 ms 218 ms 217 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]
11 219 ms 217 ms 218 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.17]
12 229 ms 230 ms 229 ms ae-6-6.ebr2.SanJose5.Level3.net [4.69.148.202]
13 233 ms 234 ms 234 ms ae-5-5.ebr4.SanJose1.Level3.net [4.69.148.142]
14 230 ms 229 ms 229 ms ae-34-34.ebr2.SanJose1.Level3.net [4.69.153.33]
15 259 ms 251 ms 251 ms ae-7-7.ebr1.Seattle1.Level3.net [4.69.132.50]
16 251 ms 250 ms 251 ms ae-13-51.car3.Seattle1.Level3.net [4.69.147.133]
17 251 ms 252 ms 251 ms metapeer.car3.Seattle1.Level3.net [4.71.152.18]
18 248 ms 248 ms 248 ms 208.99.192.65
19 249 ms 248 ms 248 ms 208.99.192.94
20 248 ms 248 ms 248 ms renbd1-gi-2-1.w-link.net [207.244.149.54]
21 251 ms 251 ms 251 ms botbd1-gi-4-2.w-link.net [207.244.149.33]
22 252 ms 253 ms 251 ms 7206-gi-0-2.w-link.net [207.244.149.46]

Trace complete.

C:\Users\Andrew>

mx.8013.yournet.co.nz (0.0.0.0)                                                                                             Sun Dec 4 15:11:54 2011
Keys: Help   Display mode   Restart statistics   Order of fields   quit
                                                                                                            Packets               Pings
Host                                                                                                     Loss%   Snt   Last   Avg Best Wrst StDev
1. router                                                                                                 0.0% 15599    0.5   0.2   0.1   8.4   0.3
2. ???
3. 218.101.61.101                                                                                         0.9% 15599 298.9 68.8   7.1 5257. 196.2
4. ie2-g-0-0-0.telstraclear.net                                                                           0.9% 15599 320.1 78.2 20.9 5228. 191.4
5. ge-0-2-0-1.xcore1.acld.telstraclear.net                                                                2.5% 15599 404.6 78.9 21.0 5184. 190.9
6. 203.167.233.10                                                                                         0.9% 15599 554.5 124.0 20.8 5288. 191.1
7. i-0-6-4-0.tlot-core01.bx.reach.com                                                                     0.8% 15599 526.6 249.3 146.2 5418. 191.8
8. i-1-1.tlot03.bi.reach.com                                                                              0.8% 15599 561.0 250.5 145.6 5546. 195.3
9. l3-peer.tlot03.pr.reach.com                                                                            8.8% 15599 810.2 339.2 149.0 5613. 172.9
10. vlan70.csw2.losangeles1.level3.net                                                                     7.2% 15599 776.2 338.7 147.3 5568. 172.0
11. ae-72-72.ebr2.losangeles1.level3.net                                                                   6.6% 15599 764.0 352.8 151.2 5547. 169.3
12. ae-6-6.ebr2.sanjose5.level3.net                                                                        2.1% 15599 757.3 291.1 155.1 5514. 184.8
13. ae-5-5.ebr4.sanjose1.level3.net                                                                        2.2% 15599 761.3 305.6 160.8 5471. 181.2
14. ae-34-34.ebr2.sanjose1.level3.net                                                                      2.1% 15599 720.3 291.1 155.5 5427. 184.2
15. ae-7-7.ebr1.seattle1.level3.net                                                                        2.1% 15599 717.3 312.5 172.2 5409. 183.7
16. ae-13-51.car3.seattle1.level3.net                                                                      0.8% 15599 687.9 312.4 172.2 5390. 187.4
17. metapeer.car3.seattle1.level3.net                                                                      0.8% 15599 678.1 311.9 172.3 5313. 187.3
18. 208.99.192.65                                                                                          0.9% 15599 645.7 314.2 172.0 5281. 189.1
19. 208.99.192.94                                                                                          2.3% 15599 603.0 313.6 172.2 5429. 189.2
20. renbd1-gi-2-1.w-link.net                                                                               2.3% 15599 559.3 319.2 178.1 5411. 180.9
21. botbd1-gi-4-2.w-link.net                                                                               2.5% 15599 516.3 320.0 182.0 5676. 180.8
22. 7206-gi-0-2.w-link.net                                                                                 2.4% 15599 472.5 309.6 173.7 5633. 183.7

Looks like the same box (or something) and I'm getting averaged 8% packet loss on that link.

So clearly there is a common path in there.

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

AviZ

214 posts

Master Geek
Inactive user

#553532 4-Dec-2011 15:35

speedtest within new Zealand are fine, as soon as you go through the new Zealand international gateway bang the speed is slow,

Telstra free weekend is congesting the international gateway

maxzzz

86 posts

Master Geek

#553536 4-Dec-2011 15:43

I have also noticed a slower throughput lately, even with 10 multiple streams I cannot reach my full speed any more.
Doing some tests I also noticed that the last Telstraclear hop before Reach has a higher ping than usual...

|                       Host              - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                           192.168.1.254 - 0 |   20 |   20 |    0 |    0 |    1 |    0 |
|         16.17.69.111.static.snap.net.nz - 0 |   20 |   20 |   12 |   15 |   20 |   12 |
|        54.32.69.111.dynamic.snap.net.nz -    0 |   20 |   20 |   12 |   19 |   58 |   16 |
|           111-69-27-65.core.snap.net.nz - 0 |   20 |   20 |   12 |   17 |   55 |   17 |
|                      203.167.233.10 -    0 |   20 |   20 |   78 |   80 |   85 |   81 |
|      i-0-0-4-0.sydo-core02.bx.reach.com - 0 |   20 |   20 |   99 | 101 | 110 | 101 |
|TenGigE0-3-0-7.oxf-gw1.Sydney.telstra.net -    0 |   20 |   20 | 102 | 110 | 120 | 110 |
|Bundle-Ether1.ken-core4.Sydney.telstra.net -    0 |   20 |   20 | 102 | 108 | 115 | 106 |
| Bundle-Ether1.ken39.Sydney.telstra.net - 0 |   20 |   20 | 100 | 107 | 115 | 103 |
|                                 72.14.198.54 -    0 |   20 |   20 | 100 | 106 | 160 | 102 |
|                         66.249.95.224 -    0 |   20 |   20 | 100 | 106 | 141 | 106 |
|                             72.14.237.135 -    0 |   20 |   20 | 100 | 104 | 111 | 104 |
|                  syd01s12-in-f16.1e100.net -    0 |   20 |   20 | 103 | 106 | 114 | 104 |

bradstewart

4335 posts

Uber Geek

Retired Mod

Trusted

Lifetime subscriber

#553539 4-Dec-2011 15:50

Far from impressive.

vexxxboy

4244 posts

Uber Geek

#553544 4-Dec-2011 16:02

didnt notice any major problems but after asking my son about his WoW ping he said it has gone from 120 to 240 ping on the Australian server and i can only use You Tube on 1 pc instead of 3 all at once. so something is slightly off.

Common sense is not as common as you think.

SCM

459 posts

Ultimate Geek

#553551 4-Dec-2011 16:10

DonGould: Reach problem? Is this being caused by the Telstra free weekend congesting the Reach ports?

I'd be interested to see a traceroute to 7206-gi-0-2.w-link.net to compare the path.

Is there a common Reach router in there that isn't dealing with the flood of traffic Telstra is throwing at it?

From Snap connection in Dunedin..
Tracing route to 7206-gi-0-2.w-link.net [207.244.149.46]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.10.1
2    23 ms    99 ms   100 ms 192.168.1.253
3    21 ms    24 ms    25 ms 20.17.69.111.static.snap.net.nz [111.69.17.20]
4    14 ms    13 ms    14 ms 24.17.69.111.static.snap.net.nz [111.69.17.24]
5     *        *        *     Request timed out.
6    40 ms    32 ms    31 ms 111-69-27-66.core.snap.net.nz [111.69.27.66]
7    95 ms    94 ms    95 ms 203.167.233.10
8   222 ms   223 ms   222 ms i-0-6-4-1.tlot-core01.bx.reach.com [202.84.142.1
14]
9   229 ms   220 ms   220 ms i-2-5.tlot03.bi.reach.com [202.84.251.242]
10   223 ms   223 ms   223 ms xe-11-2-0.edge1.losangeles6.level3.net [4.68.62.
9]
11   220 ms   220 ms   220 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190
]
12   220 ms   220 ms   220 ms ae-82-82.ebr2.LosAngeles1.Level3.net [4.69.137.2
5]
13   234 ms   244 ms   234 ms ae-6-6.ebr2.SanJose5.Level3.net [4.69.148.202]
14   245 ms   234 ms   234 ms ae-5-5.ebr4.SanJose1.Level3.net [4.69.148.142]
15   232 ms   255 ms   234 ms ae-34-34.ebr2.SanJose1.Level3.net [4.69.153.33]

16   265 ms   252 ms   251 ms ae-7-7.ebr1.Seattle1.Level3.net [4.69.132.50]
17   250 ms   250 ms   250 ms ae-13-51.car3.Seattle1.Level3.net [4.69.147.133]

18   249 ms   249 ms   249 ms metapeer.car3.Seattle1.Level3.net [4.71.152.18]

19   253 ms   253 ms   253 ms 208.99.192.65
20   252 ms   252 ms   252 ms 208.99.192.94
21   250 ms   250 ms   250 ms renbd1-gi-2-1.w-link.net [207.244.149.54]
22   251 ms   250 ms   250 ms botbd1-gi-4-2.w-link.net [207.244.149.33]
23   250 ms   250 ms   250 ms 7206-gi-0-2.w-link.net [207.244.149.46]

While my internet has been slow most of the weekend it seems others have had it much worse..

1 | 2 | 3