Facebook CDN issues on snap vdsl?

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Facebook CDN issues on snap vdsl?

richms

28172 posts

Uber Geek

Trusted

Lifetime subscriber

#179135 28-Aug-2015 07:25

Seeing it across all PCs, even ones that have ipv6 turned off, really slow to load. Progressive JPGs showing as a blocky mess for 20-40 seconds sometimes before slowly getting the added detail added to them.

Same time, speed tests locally and overseas are fine, other stuff is also fine.

Richard rich.ms

Psilan

856 posts

Ultimate Geek

#1375932 28-Aug-2015 22:06

Yeah . Problem here too.
Seems like a reasonably regular issue with Snap / 2Degrees.

Voyager referral - https://refer.voyager.nz/68QKJ8XKK

tardtasticx

3075 posts

Uber Geek

#1375945 28-Aug-2015 23:18

I'm on spark and a friend on another ISP mentioned it also when he was at mine earlier. I just thought it was my machine but he said he's been having the same issue for the last day or 2. I only noticed it properly this morning myself.

Kinda annoying. I'd rather it didn't work at all than be so slow! Haha

grant_k

3539 posts

Uber Geek

Trusted

#1375946 28-Aug-2015 23:23

I'm on Vodafone RBI and had the same issue earlier in the evening. Seems OK now though.

The varied reports above across several ISPs & network connection types point to a FB problem as opposed to an ISP problem.

JamesL

956 posts

Ultimate Geek
Inactive user

#1377853 1-Sep-2015 17:51

Having the same issue, it's been happening randomly in the evenings for the past 2-3 weeks now

Can't get to www.gpforums.co.nz or www.facebook.com for example, both fail to get past the first snap hop:

Tracing route to www.gpforums.co.nz [52.64.62.230]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfsense.local [192.168.1.1]

2 25 ms 26 ms 24 ms 69.7.69.111.static.snap.net.nz [111.69.7.69]

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

Tracing route to star.c10r.facebook.com [179.60.193.3]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfsense.local [192.168.1.1]

2 7 ms 6 ms 6 ms 69.7.69.111.static.snap.net.nz [111.69.7.69]

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

JamesL

956 posts

Ultimate Geek
Inactive user

#1377856 1-Sep-2015 18:00

Can't seem to edit my previous post in Chrome, just seems to sit there and become unresponsive.

I've had this issue the past few weeks, just happened again about 30 minutes ago

Broken:
Tracing route to www.gpforums.co.nz [52.64.62.230]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfsense.local [192.168.1.1]
2 25 ms 26 ms 24 ms 69.7.69.111.static.snap.net.nz [111.69.7.69]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.

Tracing route to star.c10r.facebook.com [179.60.193.3]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfsense.local [192.168.1.1]
2 9 ms 9 ms 8 ms 69.7.69.111.static.snap.net.nz [111.69.7.69]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.

and working

Tracing route to star.c10r.facebook.com [179.60.193.3]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfsense.local [192.168.1.1]
2 5 ms 7 ms 9 ms 69.7.69.111.static.snap.net.nz [111.69.7.69]
3 * * * Request timed out.
4 61 ms 69 ms 62 ms 23655.syd.equinix.com [202.167.228.156]
5 38 ms 37 ms 38 ms 32934.syd.equinix.com [202.167.228.39]
6 49 ms 48 ms 50 ms psw01d.syd1.tfbnw.net [173.252.66.51]
7 61 ms 59 ms 60 ms msw1ab.01.syd1.tfbnw.net [173.252.66.83]
8 62 ms 62 ms 55 ms edge-star-shv-01-syd1.facebook.com [179.60.193.3
]

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

1 1 ms <1 ms <1 ms pfsense.local [192.168.1.1]
2 5 ms 4 ms 4 ms 69.7.69.111.static.snap.net.nz [111.69.7.69]
3 * * * Request timed out.
4 61 ms 64 ms 62 ms 23655.syd.equinix.com [202.167.228.156]
5 39 ms 41 ms 38 ms 16509.syd.equinix.com [202.167.228.131]
6 47 ms 55 ms 52 ms 52.95.36.98
7 59 ms 60 ms 62 ms 52.95.36.105
8 51 ms 49 ms 47 ms 54.240.192.107
9 * * * Request timed out.
10 * * * Request timed out.
11 * * ^C

Wonder if its an upstream routing issue e.g. equinix?