Early this morning we planned to release a central server update that would allow Camfrog for iPhone users to receive push notifications to their phones. Unfortunately we ended up having unexpected problems and we had a two hour downtime.
After the unexpected problems we found yet another problem where some users could not see videos from other users. We just now disconnected all Camfrog rooms to solve this problem. If you are seeing the message that you can’t see another user due to an old version please try signing your client on and off again.
If you are still having problems please let us know. Sorry for the inconvenience and thanks for your patience.
Update 5/18 – The internal video chat room list and room locator service will be offline until tonight sometime between 9PM and midnight CST. Sorry for any inconvenience. We could reboot the entire system to solve this immediately, but we would prefer to fix this tonight instead and avoid a reboot. Please note that you can join any rooms manually as usual from your contact list or you can visit http://videochat.camfrog.com to view the list of rooms.
Update 5/29 – There seem to be some network problems for some users in the US, EU, and Asia. Hopefully they will clear up soon, sorry for any inconvenience. If you are already on Camfrog you will not see any problems however if you try to sign on now you may see a long delay. Just be patient and your client will eventually sign on again.
Update 5/30 – It appears the logon problem has returned. It will probably continue to happen intermittently until our network provider finds the cause. If they do not find the cause soon we will plan to switch providers.
Update 5/31 – Our team has been working for over 40 hours now during the US Holiday while trying to determine a way to solve this problem. When they find a solution I will update you. Any downtime is unacceptable and we spend major time and money to make sure it never happens, but this situation is unique and unexpected in a way we could never prepare for in advance.
Update 5/31 (2nd Update) – Our team is still trying to solve the problem. I will probably not update again until we have made some progress. Thanks for your patience.
Update 6/2 – We think we have determined the cause of the problem. Changes have been made to avoid the problem in the future, but we cannot promise the problem will not resurface. Ribbit.