Forum Moderators: martinibuster

Message Too Old, No Replies

Adsense Serving Issue?

         

rogerd

10:05 pm on Sep 6, 2006 (gmt 0)

WebmasterWorld Administrator 10+ Year Member



I've not run into this before, but a major site of mine was running very slowly, with the pages sometimes not loading at all. After a couple of server reboots, I started playing with page content. I finally narrowed it down to my ad serving code. I removed it, and the pages loaded fine. I plugged in straight Adsense code, and the pages wouldn't load worth a darn. Removed the code, and all was snappy.

Is this just some weird thing affecting me? What's the best practice to code the insertion so that an external problem doesn't take my site down?

youfoundjake

10:12 pm on Sep 6, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



were there any changes to the server? what os? could something be blocking javascript? Can you try from a different machine with the same results? Is it just your site, or are you able to go to other sites and have the same page load issue?

fredw

10:58 pm on Sep 6, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



We have seen something like this happen in the past, but there don't seem to be any problems with Google globally at the momemt.

Is perhaps your own internet connection having trouble resolving pagead2.googlesyndication.com?

Gian04

11:42 pm on Sep 6, 2006 (gmt 0)

10+ Year Member



Im experiencing the same problem since yesterday.

rogerd

1:51 am on Sep 7, 2006 (gmt 0)

WebmasterWorld Administrator 10+ Year Member



When I had narrowed the problem down, I jumped on Technorati to see if anyone was blogging about an Adsense problem. I found a post from a few minutes earlier, and tried to reach it. Oddly, or perhaps appropriately, the site hung up after loading the page header - pretty much the same thing I was seeing. Perhaps it's something that affected only a few accounts, as there doesn't seem to be any widespread problem reporting.

I don't think it was a browser or local DNS issue. The site runs on two dedicated servers in a different state, and the issue apparently kicked the front-end server into a major overload situation. The database server was unaffected.

It seemed to clear up on its own, and all is fine now.