Another external server related foulup - yui.yahooapis.com

vbimport

#1

Pages here taking an AGE to load, and yui.yahooapis.com was featuring large in my firewall logs.

Blocked it, and now SNAP, everything is fast again.

I guess it’s related to ads, search or something, but why the hell can they not keep all these flaming externals from fouling up all the time.

Since things work ok with it blocked I guess I can add it permanently to my garbage server list!


#2

YUI is Yahoo User Interface and has nothing to do with advertising. It’s used for many parts of the site that use a combination of Javascript, XML and PHP/MySQL. We use the external Yahoo libraries as this ensures we always use the latest (and possibly securest versions) and to save bandwidth.

More information about YUI can be found here: http://developer.yahoo.com/yui/.

We are in the process of adding new servers (I added two new ones last week) which could help. Could you do a tracert (run -> cmd, then tracert club.cdfreaks.com - copy/paste results here, and do a tracert on yui.yahoo.com and copy/paste the results here too)? That way I can determine where the bottleneck is.


#3

Done…, I’ll cancel the blocking and see if it’s still fouled
Seems to have cleared up now - Aha, and EBUYER is now working too, it was feeling like there could have been a bit of a routing snarl-up

Tracing route to cdfreaks.com [212.204.237.148]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Sweex-Router [192.168.2.1]
2 14 ms 16 ms 10 ms 10.3.48.1
3 16 ms 14 ms 13 ms wapk-t2cam1-a-v107.network.virginmedia.net [80.1
.170.29]
4 13 ms 10 ms 12 ms popl-t3core-1a-ge-019-0.network.virginmedia.net
[195.182.180.85]
5 14 ms 15 ms 17 ms pop-bb-a-as2-0.network.virginmedia.net [213.105.
174.234]
6 23 ms 16 ms 19 ms lee-bb-b-as0-0.network.virginmedia.net [213.105.
175.129]
7 39 ms 40 ms 40 ms Tengigabitethernet7-1.401ar4.LON3.gblx.net [64.2
14.128.37]
8 35 ms 49 ms 44 ms ION-IP-B-VAmsterdam.ge-3-0-0.420.ar2.AMS2.gblx.n
et [208.51.86.150]
9 39 ms 40 ms 37 ms te-4-2-15.nl-ams2-bb-r1.widexs.net [212.204.248.
89]
10 33 ms 36 ms 36 ms te-1-49-14.nl-ams1-bb-r1.widexs.net [212.204.248
.81]
11 34 ms 34 ms 36 ms ge-10-1.nl-ams1-ph-core.widexs.net [212.204.214.
5]
12 36 ms 36 ms 37 ms 212.204.237.148

Trace complete.


C:\Documents and Settings\Matthew>tracert yui.yahooapis.com

Tracing route to euycs-l.yahoo-eu1.akadns.net [77.238.187.39]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Sweex-Router [192.168.2.1]
2 11 ms 12 ms 14 ms 10.3.48.1
3 15 ms 18 ms 9 ms wapk-t2cam1-a-v107.network.virginmedia.net [80.1
.170.29]
4 32 ms 18 ms 12 ms popl-t3core-1b-ge-012-0.network.virginmedia.net
[62.255.80.169]
5 14 ms 30 ms 17 ms pop-bb-a-as2-0.network.virginmedia.net [213.105.
174.234]
6 17 ms 19 ms 20 ms nth-bb-b-so-010-0.network.virginmedia.net [213.1
05.172.13]
7 19 ms 18 ms 29 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
8 20 ms 17 ms 17 ms 193.159.225.237
9 18 ms 17 ms 22 ms 62.159.199.202
10 17 ms 20 ms 32 ms te-8-1.bas-a1.uls.yahoo.com [66.196.65.5]
11 20 ms 27 ms 19 ms l1.ycs.vip.uls.yahoo.com [77.238.187.39]

Trace complete.


#4

Good to see it has cleared up now!


#5

And back again, trouble with external servers, when they have a bad day, so do you!

Once again, adding it to my firewall block seems to get the speed back with no apparent loss of functionality.

Current trace to Yahooapis server:

C:\Documents and Settings\Matthew>tracert yui.yahooapis.com

Tracing route to euycs-l.yahoo-eu1.akadns.net [77.238.187.39]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms Sweex-Router [192.168.2.1]
2 11 ms 9 ms 11 ms 10.3.48.1
3 11 ms 12 ms 10 ms wapk-t2cam1-a-v107.network.virginmedia.net [80.1
.170.29]
4 11 ms 13 ms 10 ms popl-t3core-1a-ae1-0.network.virginmedia.net [19
5.182.175.225]
5 14 ms 10 ms 12 ms pop-bb-a-as2-0.network.virginmedia.net [213.105.
174.234]
6 14 ms 15 ms 15 ms nth-bb-b-as3-0.network.virginmedia.net [213.105.
172.13]
7 17 ms 16 ms 16 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
8 18 ms 17 ms 16 ms 193.159.225.237
9 19 ms 15 ms 19 ms 62.159.199.202
10 20 ms 17 ms 21 ms te-8-1.bas-a2.uls.yahoo.com [66.196.65.7]
11 30 ms 20 ms 17 ms l1.ycs.vip.uls.yahoo.com [77.238.187.39]

Trace complete.

Trace looks ok, but then I’ve seen good traces to sites that are choked before.

Other thing, maybe something is wrong with the cachability - as it uses a ? parameter, that may screw up caching altogether.


#6

And cleared up again - looks like I’m getting the same server, was beginning to think there was a bad one in their server pool.