render ads.js . test domain.js . expansion embed.js . osd.js

appearing in error logs

[Lame_Wolf]

Just looked at my error logs. This is something I rarely do as I know my site doesn't have any broken links.

I am seeing an increasing amount of errors appearing. These are...

/pagead/render_ads.js
/pagead/test_domain.js
/pagead/expansion_embed.js
/pagead/osd.js

I have tried googling it, but most of the time I come across pages that have the above embedded onto the page, so I see it as a human. I do not see it on my site (using the same browser).

I did notice the other day that my browser wouldn't display image adverts. All that appeared were white boxes. They were working, and the niche is huge, so no reason not to show something. Anyway, it was a short test and these have been coverted back to text only adverts, so that is ruled out as well.

Are others seeing it in their logs ? It may explain why people are seeing less money.

Any idea if a bug on Google's side, or my server set up ? (which hasn't altered since it was set up).

[icedowl]

Yes, I see those in my 404 section in Awstats. I have no idea what causes it. Personally, I haven't encountered any white boxes anywhere.

[Lame_Wolf]

Thanks for replying Icebowl.
Those white boxes were removed days ago, but these errors are on todays logs, so it rules out the problem being image adverts.

It looks like a error/bug/feature at Google's end of things, but what ?

ASA... Any ideas ?

[robho]

I've been getting a similar thing, mostly with "pagead" not found, sometimes "__utm.gif" not found. Hundreds of them a day. (I rewrite urls so /pagead/osd.js would look for a script named pagead on my system).

Looking at the IP's, a high proportion of them come from direcway.com and direcpc.com - Hughes satellite internet in the US.

And with a bit of hunting around I've found a message on Google Ad Manager forums from September that mentions a similar problem, and they also see a pattern of mostly satellite internet ISPs (who usually have very aggressive caching).

Like him, I suspect it's a faulty caching system on the satellite ISP, that is incorrectly changing the domain from Google to our domain.