[varispeed]

Did you have access to the entire source code and understanding of all services running the system? Capping could have been done by a service created by a team you wouldn't have access to and without knowledge something like that even exist (and rightfully so, as it would take one whistleblower to harm the business). So I am not surprised you would write that there was no such facility.

[londons_explore]

> Did you have access to the entire source code and understanding of all services running the system?

Near enough, yes. Sure, there are millions of lines of code, and I did not read every one, but I debugged enough issues that I'm sure I would have come across this capping effect if it existed and affected more than some dormant/test accounts.

[varispeed]

It's possible to implement something like this and you wouldn't be able to find out, as a service sitting between the network and ad servers, it could even be embedded in an innocent looking load balancer. Why would you think something like that wouldn't exist?

[nucleardog]

Why would Google, internally, implement a feature as if they were maliciously attacking their own systems?

[varispeed]

They could use that to suppress funding to websites that are not in line with Google world views and boost funding to websites aligning with their views. They could also use this to help website competitors who pay for ad words. My traffic also got down once I stopped paying for ad words, but the increase of traffic I was getting from ads, was nowhere near the size of the drop after I stopped using it. Then they capped the ad sense.

[brokenmachine]

So they can not pay the content providers and pocket the advertising money?

Not saying that's what happened but there's definitely motive.