On several occasions, Google Search is often out when the users look up information by searching with specific terms such as “How many emojis on iOS?”, “How many emojis on Apple?” and “How many emojis on Windows?”, etc.
Bleeping Computer investigated the concerns and was the first to identify the issue and be able to reproduce the specific issue on both Google search sites and the available mobile app.
When users entered these particular keyboards, many server errors came up that prevented optimal operation or prevented the users from accessing the relevant information related to the terms they entered.
The users, dubbed the “freeze emoji”, found that entering the said phrase brought a lot of server errors.
The server error message says, “We’re sorry, but it looks like an internal server error occurred while processing your request. Our engineers have been notified and are working to resolve the issue. Please try again later.”
While most users thought the issue was likely country-specific, it turned out not to be the case. It was initially reported on google.co.nz.
But a series of events that followed confirmed that the error was not just a country-specific error and affected Google on a global scale, meaning google.com was also showing the same error.
After the issue, user llui85 compiled a list of triggering issues leading to the server errors that were: visible on Google. Some of them include:
- “how many emojis on iOS”
- “how many emojis on apple”
- “how many emojis on windows”
- “how many emojis on Lumia”
- “how many emojis Lumia” and a few others
Since the first server complication and failure, things are now fixed, meaning users don’t have to experience the same problem again. Users believe that a specific webpage that appears in the search results caused the error. However, there are no official reports or confirmations from Google as to why it happened.
Given that the situation was so absurd and out of the blue, it’s not surprising that the same thing quickly became a trend on various social media platforms, especially on Twitter.
Reports also suggest that Bleeping Computer has already contacted Google and is currently waiting to hear from them about the issue and what could be the possible cause of the problem. They haven’t heard from Google yet.