ayg wrote:

I'm experiencing some of this too within the past week or so. Gmaxwell used me
and a couple of others as guinea pigs in #wikimedia-tech last night, and sent
the results off to mark. His guess was some network congestion on the route
that certain clients were using. I'm sure he wouldn't mind me reposting some
snippets here, for what they're worth to those of us who are suffering.

<NullC> adri: From Simetrical's packet traces it's clear the delay is due to
high packet loss between him and tampa.
<NullC> Lots of retransmits.
<NullC> adri: I had him pull once from AMS and ones from tampa.. The AMS is fast
the tampa moves like a slug in mud.
<NullC> adri: I'm guessing whatever upstream is involved has a saturated peering
link to someone... or the like.. The trace routes they are doing for me now will
tell me more.
<NullC> Hildanknight: I'm not sure yet. My best hyphothesis right now is that
there is a congested connection inside one of Wikimedia Tampa's ISPs. Becuase of
this congested link, some people would see slowness while others would not
depending on where they are on the internet.
<NullC> This many not, however, be correct.
<NullC> I wouldn't bet money on this being the correct solution until I have
identifyed the link which is congested. Because traffic is most likely taking a
different path from Simetrical to Tampa wikimedia than from Tampa wikimedia to
Simetrical, it's a little hard to research.

He gave this as a workaround:

<NullC> Hildanknight: You will be much faster for now as a workaround if you
adjust your browser settings and set your proxy to 145.97.39.155 port 80, but
you will only be able to go to wikimedia sites while it is set that way.

january8888 wrote:

Well, I did the 145.97.39.155 port 80, and three minutes to open. I'm going to
see if I can get the MIS tech folks here to ping the Main Page, and see if that
turns up anything.

Network slowness somewhere on user side. Reopen this bug with
a traceroute if the problem is still around.