Mine right now is at 38c and 36c so the fans bounce between low and medium speed, most of the time it stays at medium speed though

Low Speed = 1440 and 1080 rpm
Medium Speed = 1680 and 1320 rpm
High speed = 2100 and 1680 rpm

my room temp is currently 72f, but outside its 35f.... its cold tonight.

I originally posted that my B11 were louder then my batch 8 and 9, but since then they have tapered off and run at fairly the same db as my original S3+s.

We are pleased to announce Antpool (antpool.com) which is open for users all around the world. BITMAIN has invested significant resources into developing a bitcoin pool based on the p2pool mining protocol. BITMAIN reaffirms its commitment to help decentralize the Bitcoin network, strengthen the Bitcoin eco-system and put the majority of hashing power into the hands of consumers.

The p2pool protocol prevents hashing power being controlled by one central entity (the pool owner), and has been significantly developed during the development of Antpool. All p2pool code will be open sourced and uploaded on BITMAIN’s Github link this week https://github.com/bitmaintech/p2pool. Antpool supports solo mining as well.

Antpool has been proven to be stable and secure through its long testing period.  From August 22th to November 10th, 295 blocks were found and 7398 Bitcoins were mined. Further stats can be found here link https://www.antpool.com/poolStats.htm.

Antpool can be found at antpool.com, while miners now can connect at stratum.antpool.com:3333 for pooled mining, and will be able to connect at p2p.antpool.com:3333 for p2p mining this week. Pool nodes are deployed around the world to improve performance and provide redundancy. Miners are automatically routed their closest location, including:

• United States
• Germany
• Hong Kong
• Beijing
• Shenzhen
• Qingdao
• Hangzhou and more.

Features

• 0% fees and PPLNS earnings.
• Graphical displays for hashing speeds, income and pool statistics.
• Email warnings for underperforming miners. 
• API and third party application support.
• Support for miner groups, group statistics and management.

Forum & Ticket System
Users are able to access to Antpool with their BITMAIN account. The log in and ticket system is unified across all BITMAIN services, which allows communication and support to be more efficient. Miners now can buy mining rigs from bitmaintech.com and chose hosting service at Umisoo and mine at antpool.com.

Your feedback is important for us to develop and improve our products.
Ticket page: support.bitmain.com
Forum Page: forum.bitmain.com

Hey guys, got a probelm with a S3.  Unit was hashing fine but then it just stopped hashing for no reason.  The red LED stays on all the time even after the unit is powered up and connects to the network.  

After power up, the fans spin and red LED comes on then the fans stop for a bit.  After a few seconds, then green and yellow LAN LEDs start flashing, then the fans start spinning.  Then the green LED next the the RED LED comes on but the RED LED does not go out like expected.  I can log into the miner from web brwoser fine but it never resumes hashing.  Is there a fix for this issue? I have rebooted, cycled power, reinstalled backup program and reinstalled firmware and tried to reset the miner with the little button on the back.  Nothing gets it hashing again.  I even changed pools but no go either.

It the only device on network that is 192.168.1.99.

I have the miner plugged in to the router directly.  I originally had it running on static IP 192.168.1.98.  Router setting is default 192.168.1.1.  I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware.  I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31.  Web interface works great on all three IPs but the thing just wont start hashing.  The Red LED stays red when all my other miners red LED go out once its connected to pool.  I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.

Log into the unit's web UI and change network to DHCP. Remember to apply the settings.
It may change it's address after this, but that is all you have to do.

You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange.
I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does.