Google has announced that it plans to report Q4 2012 earnings on Jan. 22 at 4:30 p.m. EST. The press release typically goes up a few minutes early, with a conference call taking place over on Google’s investor hub with top executives. As it does every quarter, the report gives us a look into how the folks in Mountain View are performing. Let’s just hope they don’t report earnings a little too early this time. Stay tuned! Read more
We told you yesterday that Google was carrying on the tradition of placing a large monument on the lawn in front of Building 44 at the Googleplex. This time, the statue represented the upcoming new version of Android 4.1 Jelly Bean. The image yesterday showed a transparent jar tipped over with jellybeans spilt out, but today we get a look at the finished sculpture in the video above. The jar is actually the Android mascot’s torso. TechCrunch went behind the scenes to find out how the Android jelly bean jar was made.
The Google’s I/O event is kicking off today, where we are all expecting to see much more of Jelly Bean. We will bring you live updates as they happen when the keynote address kicks off at 12:30 p.m. EST (9:30 a.m. PST). We are also expecting to see some major Google TV announcements.
LATEST UPDATE: Google’s App Status Dashboard, an official website that offers performance information for Google Apps services, claimed earlier today that Gmail’s status went down, but the problem is now resolved less than an hour later.
“Please rest assured that system reliability is a top priority at Google, and we are making continuous improvements to make our systems better,” contended Google.
The service interruption only affected 2 percent of Gmail’s user-base. DownRightNow, a universal monitoring service for the Web that is similar to Google’s Dashboard, described the outage as a “widespread service disruption” that started somewhere between 12:40 p.m. and 12:59 p.m. EST. The service interruption did not seem to affect mail pushing to third-party clients.
Those who tried to access Gmail.com directly found the following “Temporary Error (500)” notice with a “93″ numeric technical code: