What the Gemini outage was and how it unfolded
The Gemini outage was a sudden AI service disruption in which Google’s Gemini assistant returned persistent error messages and codes that blocked people from accessing its core features across devices and apps. Early Wednesday, Gemini users found their usual prompts replaced by “something went wrong” notices tied to error codes 1076 and 1099, leaving them unable to run chats, automations, or Gemini in Google Workspace. Reports appeared soon after 6 a.m. ET, with Downdetector climbing to close to 1,000 complaints, then topping 1,600 as the morning progressed. Most problems came from the Gemini app and web access, with only a small share linked to smart home workflows. Confusing matters, Gemini’s own status page still claimed that “all systems are currently operational,” even as social media filled with screenshots of failures and frustrated posts asking whether Gemini was down for everyone.
The cryptic 1076 and 1099 Gemini error codes
As the Gemini outage spread, two technical signals kept reappearing: Gemini error codes 1076 and 1099. People on Reddit, X, and Google’s own support forums shared screenshots showing those codes under the generic “Something went wrong” message. A platinum product expert on Google Support has described 1076 as “a browser-level conflict or a temporary communication glitch with Gemini” and noted that it is not a usual error, which explains why many daily users had never seen it before. The same expert previously advised those hit by 1099 to switch models, hard refresh the page, or try Gemini in an incognito browser session. During this incident, though, those tips had limited effect because the disruption sat on Google’s side of the connection, turning the error codes into a visible marker of a broader AI service outage rather than isolated user issues.
Scope of impact: apps, web, and Workspace AI tools
The Gemini outage did not stay confined to a single app or platform. Google confirmed that Gemini in Google Workspace was affected, touching people who use Drive, Docs, Sheets, Slides, and the dedicated Gemini app. According to CNET, the disruption hit users on macOS, the web, iOS, Gemini in Chrome, and Android, signalling a cross-platform failure in core Gemini functionality rather than a glitch on one operating system. DownDetector, which tracks service problems, logged more than 1,600 reports for Google Gemini starting around 3 a.m. PT, a number that likely understates the total population affected but still shows the size of the wave. Earlier Android Police reporting noted that 58% of complaints were about the Gemini app and 35% about the website, while only 5% concerned Google Home automations, suggesting front-end chat access took the hardest hit.
Google’s response and resolution timeline
Google’s public response started slowly, but the company did move to confirm the Gemini outage and outline a fix. Around 3 a.m. PT, the Google Workspace Status Dashboard acknowledged issues with Gemini in Workspace and said engineering teams had begun applying “mitigations” to restore service. An update at 1:19 p.m. PT stated that “the majority of Google users shouldn’t be running into issues anymore,” even though the root cause was still under investigation. Separately, Android Police reported that the dashboard promised another update by 3:30 p.m. ET and noted that there was no workaround for affected users while the mitigation was in progress. Later, Google Labs and Gemini vice president Josh Woodward said that a return to normal service was imminent, writing that some fixes were already completed and the rest were “coming very soon” as the rollout continued.
What the Gemini outage reveals about AI reliability
The Gemini outage highlights how tightly many workflows and habits now depend on AI tools and how disruptive an AI service outage can be. People were not only blocked from casual queries but also from productivity features inside Docs, Sheets, and other Workspace apps, amplifying frustration as the morning’s work stalled. It also exposed a communication gap: while Gemini’s consumer-facing status page still claimed all systems were fine, outage reports surged on social platforms and Downdetector, leaving users to crowdsource confirmation that Gemini was down. The rapid move from scattered 1076 and 1099 Gemini error codes to a confirmed incident shows why clear, unified status messaging matters. As AI assistants become more common, users will expect faster acknowledgment, visible Gemini outage timelines, and clearer guidance when cryptic Gemini error codes appear and the system fails to respond.
