Slow Twitter image downloads on 2degrees?

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Slow Twitter image downloads on 2degrees?

1 | 2 | 3

1537 posts

Uber Geek

Trusted

2degrees

#1965249 27-Feb-2018 16:57

Hi guys

If anyone is still experiencing this issue please can you PM us the following info -

2degrees Account number
Type of connectivity
Time / Date when you noticed the issue started

Many thanks

^POB

TheHoss

36 posts

Geek

#1966132 28-Feb-2018 20:56

Yes, have noticed the issue on 2D Fibre for a while now but haven't done much troubleshooting investigating to be honest. Will PM 2D when I have some info.

Lovebug

16 posts

Geek
Inactive user

#1968257 5-Mar-2018 13:18

I've been having this issue also, slow downloads from gyfcat, for a long time.

I'll PM details, tonight when I get home.

freitasm

BDFL - Memuneh
79250 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1979060 17-Mar-2018 16:28

Any news on this @2degreescare?

More than 20 seconds to download a photo on Twitter, on a fibre connection? Funny it's only this service.

2degreesCare

1537 posts

Uber Geek

Trusted

2degrees

#1979609 19-Mar-2018 10:15

Hi,

We'll need more info on this to properly troubleshoot this. The issue doesn’t seem to be present when our Network team tested this from their work machine which suggests it isn’t a routing issue. Also we don’t have direct control of routing once it leaves our network so the fault could lie anywhere on the upstream path or in the Twitter environment.

At this stage our team could not identify any fault on our network, there is no congestion, latency is good to the addresses Twitter.com resolves to and no packet loss. Those are the only variables we have visibility of, if there is something wrong on the Twitter end, or upstream we cannot do anything to directly fix that.

First we need to try simulate the issues the customer is experiencing on our network. We need to know most importantly times the slowness is occurring, if it is not constant.

If possible can anyone experiencing this issue please PM us with the above details plus the following info -

What times specifically is this happening or is it constant?

Are you connecting via Ethernet or wireless?

Thanks

^POB

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1979653 19-Mar-2018 10:42

2degreesCare:

At this stage our team could not identify any fault on our network, there is no congestion, latency is good to the addresses Twitter.com resolves to and no packet loss. Those are the only variables we have visibility of, if there is something wrong on the Twitter end, or upstream we cannot do anything to directly fix that.

If you're only testing to twitter.com you're not going to see anything because that's nothing to do with the issue.

Twitter hosts images on pbs.twimg.com which is hosted on an Edgecast CDN and resolves back to an IP of 117.18.237.70 in this part of the world. This seems to be served from two locations depending on the upstream - an Edgecast CDN node in Auckland an an Edgecast CDN node in Sydney. Those having issues seem to be peering with the Edgecast CDN in Auckland and any RSP with upstream peering with the CDN node in Sydney does not suffer from any issues.

mdf

3512 posts

Uber Geek

Trusted

#1979657 19-Mar-2018 10:49

2degreesCare: Are you connecting via Ethernet or wireless?

Just superb trolling of the BDFL there!

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

freitasm

BDFL - Memuneh
79250 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1979662 19-Mar-2018 10:54

sbiddle:

@2degreesCare:

At this stage our team could not identify any fault on our network, there is no congestion, latency is good to the addresses Twitter.com resolves to and no packet loss. Those are the only variables we have visibility of, if there is something wrong on the Twitter end, or upstream we cannot do anything to directly fix that.

If you're only testing to twitter.com you're not going to see anything because that's nothing to do with the issue.

Twitter hosts images on pbs.twimg.com which is hosted on an Edgecast CDN and resolves back to an IP of 117.18.237.70 in this part of the world. This seems to be served from two locations depending on the upstream - an Edgecast CDN node in Auckland an an Edgecast CDN node in Sydney. Those having issues seem to be peering with the Edgecast CDN in Auckland and any RSP with upstream peering with the CDN node in Sydney does not suffer from any issues.

Quoted just so I can tag @2degreesCare...

muppet

2566 posts

Uber Geek

Trusted

#1979692 19-Mar-2018 11:19

Guys & girls, this is a "known problem"

The problem is Edgecast CDN node with IP of 117.18.237.70 (pbs.twimg.com - where all Twitter images come from) is very very slow to load images, initially. Once it's cached them, it seems very fast.

I experience the problem too on NowNZ.

There was a thread of Twitter people (I can't understand why Steve Biddle hasn't chimed in on this thread yet) having the same problem.

This started for exactly the same time as I swapped out my old home router for a new virtualised pfSense box, so I spend a good week doing MTU and all sorts of other tests, convienced it was my problem.

It's not.

@2degreesCare you need to contact Verizon and moan about their Edgecast CDN node with IP of 117.18.237.70 - it's not a 2degrees fault as such, it's affecting other ISPs in NZ.

A fix, if you're able to do it, is to override the IP of pbs.twimg.com with 72.21.91.70
I did on my home router and now our Twitter is fast again.

That IP is hosted in the US somewhere, but damn it's much faster to pull images than the broken POS that is 117.18.237.70

Edit: By the time I submitted this I note that Sir Biddle has already replied with exactly what I said :-)

yitz

2074 posts

Uber Geek

#1979715 19-Mar-2018 11:29

I just redirect pbs.twimg.com to wildcard.twimg.com which ends up being served by the main Twitter/Fastly CDN which is how it worked before they appear to have added Edgecast to the mix at the beginning of February.

But agree it is not a 2degrees problem.

freitasm

BDFL - Memuneh
79250 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1979738 19-Mar-2018 11:33

Good workaround suggestions folks, thanks.

hio77

12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

#1979747 19-Mar-2018 11:45

muppet:

@2degreesCare you need to contact Verizon and moan about their Edgecast CDN node with IP of 117.18.237.70 - it's not a 2degrees fault as such, it's affecting other ISPs in NZ.

now if only verizon wouldn't be asking for billions to actually fix something on their network ;)

this is totally just their attempt to Americanize us!

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1979895 19-Mar-2018 14:56

muppet:

Edit: By the time I submitted this I note that Sir Biddle has already replied with exactly what I said :-)

You were sooooooooooooo slow.

michaelmurfy

meow
13240 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1980049 19-Mar-2018 18:07

But @muppet is the true legend with the DNS suggestion - applied to my DNS server and boom, fixed.

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

hio77

12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

#1980052 19-Mar-2018 18:13

michaelmurfy:

But @muppet is the true legend with the DNS suggestion - applied to my DNS server and boom, fixed.

Now just to find a fix for all the other services hosted off edgecast....

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

1 | 2 | 3