[TelstraClear] Problems accessing Facebook on TelstraClear?

Forums › One NZ (including Farmside) › [TelstraClear] Problems accessing Facebook on TelstraClear?

timmmay

20858 posts

Uber Geek
+1 received by user: 5350

Trusted

Lifetime subscriber

#113582 21-Jan-2013 15:45

In Chrome I'm finding I often have to try two or three times to access facebook, is anyone else finding that? I asked on facebook, a few friends have said yes, fine from mobile devices but not so good from a PC/mac.

ping -t facebook.com

Pinging facebook.com [173.252.100.16] with 32 bytes of data:
Reply from 173.252.100.16: bytes=32 time=203ms TTL=241
Request timed out.
Reply from 173.252.100.16: bytes=32 time=214ms TTL=241
Reply from 173.252.100.16: bytes=32 time=205ms TTL=241
Reply from 173.252.100.16: bytes=32 time=215ms TTL=241
Request timed out.
Reply from 173.252.100.16: bytes=32 time=204ms TTL=241
Reply from 173.252.100.16: bytes=32 time=202ms TTL=241
Reply from 173.252.100.16: bytes=32 time=200ms TTL=241
Reply from 173.252.100.16: bytes=32 time=200ms TTL=241
Reply from 173.252.100.16: bytes=32 time=207ms TTL=241
Reply from 173.252.100.16: bytes=32 time=202ms TTL=241
Reply from 173.252.100.16: bytes=32 time=202ms TTL=241
Reply from 173.252.100.16: bytes=32 time=205ms TTL=241
Reply from 173.252.100.16: bytes=32 time=214ms TTL=241
Reply from 173.252.100.16: bytes=32 time=215ms TTL=241
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.252.100.16: bytes=32 time=207ms TTL=241
Reply from 173.252.100.16: bytes=32 time=205ms TTL=241
Reply from 173.252.100.16: bytes=32 time=204ms TTL=241
Reply from 173.252.100.16: bytes=32 time=201ms TTL=241
Reply from 173.252.100.16: bytes=32 time=208ms TTL=241

Ping statistics for 173.252.100.16:
Packets: Sent = 26, Received = 19, Lost = 7 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 200ms, Maximum = 215ms, Average = 205ms

Interestingly geekzone wasn't 100% either

ping -t www.geekzone.co.nz

Pinging geekzone.co.nz [202.175.128.169] with 32 bytes of data:
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=29ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=34ms TTL=120
Reply from 202.175.128.169: bytes=32 time=24ms TTL=120
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=24ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=25ms TTL=120
Reply from 202.175.128.169: bytes=32 time=26ms TTL=120
Request timed out.
Reply from 202.175.128.169: bytes=32 time=29ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=22ms TTL=120
Reply from 202.175.128.169: bytes=32 time=25ms TTL=120
Reply from 202.175.128.169: bytes=32 time=24ms TTL=120
Request timed out.
Reply from 202.175.128.169: bytes=32 time=20ms TTL=120
Reply from 202.175.128.169: bytes=32 time=26ms TTL=120
Reply from 202.175.128.169: bytes=32 time=22ms TTL=120
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=22ms TTL=120
Reply from 202.175.128.169: bytes=32 time=27ms TTL=120
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=25ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=26ms TTL=120
Reply from 202.175.128.169: bytes=32 time=22ms TTL=120
Reply from 202.175.128.169: bytes=32 time=22ms TTL=120

Ping statistics for 202.175.128.169:
Packets: Sent = 33, Received = 31, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 34ms, Average = 23ms

1 | 2 | 3 | 4

4222 posts

Uber Geek
+1 received by user: 1322

ID Verified

Trusted

Subscriber

#748266 21-Jan-2013 15:51

DSL or Cable?

timmmay

20858 posts

Uber Geek
+1 received by user: 5350

Trusted

Lifetime subscriber

#748267 21-Jan-2013 15:51

Cable.

Poll

346 posts

Ultimate Geek
+1 received by user: 59

#748268 21-Jan-2013 15:52

On Telstra cable at home and I find I need to specifically connect to the https site else it will fail half the time. So long as I choose https it works fine though, slightly annoying seeing as I would like it to always load the https site without me having to specify but I suspect that is more my needing to tidy up an old bookmark or something.

timmmay

20858 posts

Uber Geek
+1 received by user: 5350

Trusted

Lifetime subscriber

#748269 21-Jan-2013 15:54

That seems to help, thanks Poll :)

Ropata

318 posts

Ultimate Geek
+1 received by user: 33
Inactive user

#748271 21-Jan-2013 15:55

Yeah, have been slow as on Wgtn cable for a while now.

phantomdb

585 posts

Ultimate Geek
+1 received by user: 103

Lifetime subscriber

#748274 21-Jan-2013 15:58

Christchurch Cable, and finding simalar issues here.
Hope that helps

[ SIGNATURE HERE ]

Lenovo

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

Regs

4066 posts

Uber Geek
+1 received by user: 206

Trusted

Snowflake

#748279 21-Jan-2013 16:11

related to http://www.geekzone.co.nz/forums.asp?ForumId=44&topicid=113582 "TCL Blacklisted by Microsoft Domains"?

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

networkn

Networkn
32862 posts

Uber Geek
+1 received by user: 15453

ID Verified

Trusted

Lifetime subscriber

#748281 21-Jan-2013 16:14

No I don't think so, as it's a) Not a MS Domain, B) Not a TCL Cable Customer.

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#748350 21-Jan-2013 18:28

I have commented on this Facebook thing last week. It seems If you go to http it will fail a few times before working, but if you use https directly it works.

It sounds like the TelstraClear cache farm is at it again.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Goosey

3014 posts

Uber Geek
+1 received by user: 867

Subscriber

#748352 21-Jan-2013 18:31

freitasm: I have commented on this Facebook thing last week. It seems If you go to http it will fail a few times before working, but if you use https directly it works.

It sounds like the TelstraClear cache farm is at it again.

Im on Vodafone/Ihug and I've had the odd slowdown to zero nothing zlich when using facebook in the past couple weeks as well.

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#748353 21-Jan-2013 18:33

I was leaning to think it could be something related to the broken Perth - Asia cable, but seeing it always work on HTTPS but almost never on HTTP pretty much excluded that...

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Geekzone support

Support Geekzone with one-off or recurring donations Donate via PressPatron.

TelstraClear

566 posts

Ultimate Geek
+1 received by user: 2

Trusted

TelstraClear

#748682 22-Jan-2013 10:46

Hi everyone. We’ve looked into this and the network is operating to spec, and traceroutes don’t show any issues. We’ve also checked Facebook ourselves and have not experienced problems with load times on either Internet Explorer or Firefox. I've personally not noticed any issues at home on cable either, across three Windows devices and two Andriod.

Cheers, Gary

chevrolux

4962 posts

Uber Geek
+1 received by user: 2638
Inactive user

#748703 22-Jan-2013 11:22

It is most definitely these 4 customer's local set ups - especially Mauricio's...lol

Seriously though, we see these sorts of things happen on TCL connections all the time. It is amazes me this issue is still apparent! You would really think TCL would get on to their caches and fix things up.

D1023319

527 posts

Ultimate Geek
+1 received by user: 90

ID Verified

#748727 22-Jan-2013 12:29

FYI - we are wellington home cable for TCL and like others facebook has been real bad recently.

it hangs at a redirect screen for "facebook static.ak.fbcdn.net" which seems to be management of static content.

interesting as seems to be a issue for lots of facebook users overseas.

my family members are also reporting there are a few international sites such as Amazon that they say are slowing down recently so I wonder if this is linked.

FYI - not a PC issue as is new and I regularly check for TSR bloat and trogans.

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#748761 22-Jan-2013 13:23

Gary thanks for looking, but this is intermittent and it may be working for you now, but give some time and it will stop working again - as it happened to D1023319.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

1 | 2 | 3 | 4