Google are losing millions of dollars how much are you losing?

  • Post category:News

Google is quite large, so they do not miss the hundreds of millions of dollars they are losing each year. In fact, they either do not know or they simply do not care.

Do you care if you are losing us$100 000? or maybe you are only losing us$10000? How much are you really losing?

Maybe it is a secret? and, nobody is writing or reporting it because not many people know? AND, it is in the best interest of your competitors, if your competitors did not know they are BLEEDING OUT cash money?

This is how this works:

let me use a REAL WORLD loss of over us$4000 at GOOGLE (just for today) to illustrate.

So, IP numbers: 34.76.148.0 to 34.76.148.255 are assigned to GOOGLE (Whois shows: Google LLC, Address: 1600 Amphitheatre Parkway, City:Mountain View, StateProv:CA, PostalCode:94043,Country:US)

If this was a CLEAN ip range it could be worth upwards of us$5000. As it is now, today, it is listed as dynamic range and some IP numbers in the range has over twenty different data publishers, publishing data. So, imnsho, the probable value of this IP range is less than us$25 (for the whole range, hmm, some desperate idiot may pay $250? or even $500?) as it is useless as servers, hosting or much else.

This LOSS is entirely preventable if only GOOGLE dropped all new outgoing port 25 TCP traffic…

Actually, ALL CONNECTIVITY providers can stop losing thousands upon thousands of dollars each day by using this simple trick. -> You are a connectivity provider so ALL of your conenctivity IP numbers should not originate new TCP traffic to port 25. (only your email and server ranges originate new port 25 TCP connections) – so, simply DROP all new outgoing destination port 25 TCP traffic!

How much money are you losing each day? If you are a standard size Internet connectivity provider and you are losing us$5000 per day, you could be losing us$1,8M per year. That is more than us$ 1 800 000 per year, just because you do not have a simple and easy rule on your outgoing TCP traffic firewall.

You’re welcome!