Slow tonight 4th March on Spark fibre

Forums › Spark New Zealand (including Skinny and BigPipe) › Slow tonight 4th March on Spark fibre

jonb

1550 posts

Uber Geek

Trusted

#192283 4-Mar-2016 19:05

Maybe just me (North Shore), on 100/20 is very slow tonight..

C:\Users\admin>tracert www.stuff.co.nz

Tracing route to e1365.dsce2.akamaiedge.net [104.95.170.60]
over a maximum of 30 hops:

1     5 ms   101 ms   101 ms 192.168.1.254
2     *        *        *     Request timed out.
3   120 ms    99 ms   101 ms a104-95-160-1.deploy.static.akamaitechnologies.com [104.95.160.1]
4   218 ms   204 ms   202 ms a104-95-170-60.deploy.static.akamaitechnologies.com [104.95.170.60]

Trace complete.

Tracing route to www.trademe.co.nz [202.162.72.2]
over a maximum of 30 hops:

1     *        *        *     Request timed out.
2     *        *        *     Request timed out.
3     *        *        *     Request timed out.
4     *        *        *     Request timed out.
5     *       95 ms   100 ms TenGigabitEthernet0-2-0-911.wnmur-rt1.fx.net.nz [131.203.246.137]
6    14 ms    98 ms    99 ms trademe-wnmur.fx.net.nz [131.203.246.138]
7   103 ms   100 ms   100 ms 202.21.128.135
8   435 ms   199 ms    99 ms www.trademe.co.nz [202.162.72.2]

C:\Users\admin>tracert www.geekzone.co.nz

Tracing route to geekzone.co.nz [104.25.179.9]
over a maximum of 30 hops:

1    41 ms     1 ms    96 ms 192.168.1.254
2     *        *        *     Request timed out.
3     *        *        *     Request timed out.
4     *        *        *     Request timed out.
5    15 ms     9 ms     5 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.213]
6    71 ms   101 ms   199 ms xe0-0-6.sgbr3.global-gateway.net.nz [202.50.232.190]
7   214 ms   407 ms   263 ms ae7-10.sebr4.global-gateway.net.nz [122.56.127.214]
8    91 ms   207 ms   305 ms 13335.syd.equinix.com [202.167.228.154]
9   118 ms   102 ms    96 ms 104.25.179.9

Will check again later..

johnr

19282 posts

Uber Geek
Inactive user

#1506174 4-Mar-2016 19:18

Show us a speedtest result over Ethernet to the local Spark speedtest.net server

Kraven

627 posts

Ultimate Geek

#1506175 4-Mar-2016 19:27

Pings of around 100ms to your router do point to a local network problem. Tried restarting your router and testing over ethernet?

michaelmurfy

/dev/null
9398 posts

Uber Geek

Moderator

Trusted

Lifetime subscriber

#1506218 4-Mar-2016 20:47

This looks like you're conducting these tests over WiFi due to your first hop having a large ping indicating problems with your WiFi and not with Spark itself.

Test over Ethernet, I guarantee it'll be fine.

Jase2985

9742 posts

Uber Geek

Lifetime subscriber

#1506226 4-Mar-2016 21:10

im guessing some hi download/upload is going on or you have a wifi intensive app like Inssider open

here is an example over wifi:

Nothing else running

C:\Users\USER>tracert www.stuff.co.nz

Tracing route to e1365.dsce2.akamaiedge.net [104.95.170.60]
over a maximum of 30 hops:

1     1 ms     1 ms     1 ms 192.168.1.1
2     *        *        *     Request timed out.
3    16 ms    17 ms    15 ms a104-95-160-1.deploy.static.akamaitechnologies.c
om [104.95.160.1]
4    16 ms    15 ms    15 ms a104-95-170-60.deploy.static.akamaitechnologies.
com [104.95.170.60]

Trace complete.

Inssider open

C:\Users\USER>tracert www.stuff.co.nz

Tracing route to e1365.dsce2.akamaiedge.net [104.95.170.60]
over a maximum of 30 hops:

1   273 ms     1 ms     2 ms 192.168.1.1
2     *        *        *     Request timed out.
3   126 ms    15 ms   193 ms a104-95-160-1.deploy.static.akamaitechnologies.c
om [104.95.160.1]
4    16 ms   187 ms   299 ms a104-95-170-60.deploy.static.akamaitechnologies.
com [104.95.170.60]

Trace complete.

And here is the ping, and you can see when i closed inssider

C:\Users\USER>ping 104.95.170.60 -t

Pinging 104.95.170.60 with 32 bytes of data:
Reply from 104.95.170.60: bytes=32 time=16ms TTL=61
Reply from 104.95.170.60: bytes=32 time=284ms TTL=61
Reply from 104.95.170.60: bytes=32 time=198ms TTL=61
Reply from 104.95.170.60: bytes=32 time=90ms TTL=61
Reply from 104.95.170.60: bytes=32 time=15ms TTL=61
Reply from 104.95.170.60: bytes=32 time=247ms TTL=61
Reply from 104.95.170.60: bytes=32 time=165ms TTL=61
Reply from 104.95.170.60: bytes=32 time=53ms TTL=61
Reply from 104.95.170.60: bytes=32 time=280ms TTL=61
Reply from 104.95.170.60: bytes=32 time=215ms TTL=61
Reply from 104.95.170.60: bytes=32 time=127ms TTL=61
Reply from 104.95.170.60: bytes=32 time=22ms TTL=61
Reply from 104.95.170.60: bytes=32 time=16ms TTL=61
Reply from 104.95.170.60: bytes=32 time=16ms TTL=61
Reply from 104.95.170.60: bytes=32 time=16ms TTL=61
Reply from 104.95.170.60: bytes=32 time=15ms TTL=61
Reply from 104.95.170.60: bytes=32 time=16ms TTL=61
Reply from 104.95.170.60: bytes=32 time=16ms TTL=61
Reply from 104.95.170.60: bytes=32 time=15ms TTL=61
Reply from 104.95.170.60: bytes=32 time=16ms TTL=61

Ping statistics for 104.95.170.60:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 284ms, Average = 91ms
Control-C
^C
C:\Users\USER>

So please make sure you dont have anything else open while you are testing over wifi if you want accurate results

quickymart

5334 posts

Uber Geek

#1506301 4-Mar-2016 23:09

Little slow for me as well, on the Shore too. Few pages timing out (tested over ethernet). Seems okay at the moment though.