Gemini something went wrong (13, 1076, 1099): the fix by cause, and how long Google's outages last

How do you fix Gemini's something went wrong error?

Work through these seven steps in order. The first three cost nothing and can't lose your work, and step 4 tells you whether to stop.

1. Copy your prompt out of the box. Gemini often puts a failed prompt back in the text box, but a reload can wipe it.
2. Send it once more. During the 10 June 2026 outage, 9to5Google noted that pressing enter again might get a returned prompt through.
3. Open a new chat and send a short text prompt with no file and no Google Docs link. If that works, the old chat is the problem, and the (1076) and (9) rows below cover it.
4. Check the Gemini row on Google's Workspace Status Dashboard. It covers personal accounts too. If an incident is open, stop and wait.
5. Try a private window, another browser, or the phone app with wifi off. If one works, turn off extensions and your VPN in the one that failed.
6. Sign in with a second Google account on the same device. If that one works, the block sits on your account: age, admin settings or region, covered further down.
7. Report it. On gemini.google.com, click Settings & help, then Send feedback, and include the number in brackets.

Google defines the message in exactly one place, its sign in help page, and that page is about access, not chats. It says: "If you get a 'Something went wrong' message while trying to access or sign in to the Gemini web app, your account can't access the app at the moment. This can be due to a variety of reasons, including location, age, or type of account, among others." The numbers that appear mid chat, like (13) or (1076), aren't on any Google help page. Google's status dashboard is the only Google record that names them, and it has named three: (13) in May 2026, then 1099 and 1076 in June.

We read every incident in the dashboard's history on 11 October 2026, which runs back to 20 October 2025. Gemini had four, open 212 hours in all. Among the Workspace products listed, only Gmail logged more hours: 574 across eight incidents. For both the May and June outages, Google's posted workaround was "None at this time." So when the Gemini row shows an incident, cookies and reinstalls won't help. You wait, or you work somewhere else.

Which Gemini error number are you looking at?

The number in brackets narrows the cause, but Google hasn't published a code list. In a June 2026 Gemini community thread, the answer a volunteer Gold Product Expert marked as recommended put it plainly: Google "doesn't publish a public directory" of the codes. Android Authority found "no official guidance or documentation from Google" on (1099) in July. What Google has done is name three codes on its status dashboard, each tied to a server fault. The table records where each message was first reported, and what fixed it, as of October 2026.

Google's June notes say what 1099 and 1076 meant that day. Its 10 June incident lists the symptom as "'Something went wrong' errors (codes 1099, 1076)" and blames "a performance issue in our backend database which impacted the retrieval of Gemini App tools catalog." So both codes can come from Google's side, on every device at once. That's the first test for any number: if other people report it in the same hour, it's Google's problem. The poster in the (1099) thread says reloads and other devices changed nothing. Posters in the (1037) thread say sign outs and cache clearing didn't help either.

A number stuck to one chat, while new chats work, belongs to that chat. The (1076) thread holds the only rescue that several users confirmed. On 26 July 2026 a poster added the broken conversation to an empty NotebookLM notebook and opened it from there, and others replied on 27 and 28 July that it worked. The (9) fix is even smaller. The recommended answer in that thread, marked in February 2026, is to edit your last message, add a period and send it again. And (1037) is a usage limit wearing an error's clothes: the posters had just run out of Pro. Gemini usage limit reached explains which wall you hit and when it refills.

Is Gemini down, or is it just you?

Gemini is down when its row on Google's Workspace Status Dashboard shows an open incident, and that holds for personal accounts too. Google's final report on the 10 June 2026 outage says "The issue affected both consumer accounts and enterprise Google Workspace customers", across the web app, iOS, Android and Chrome. Here are all four Gemini incidents on the dashboard since October 2025:

The June report puts a number on how bad it got: users "experienced a 50% error rate when attempting to send prompts" between 03:30 and 10:25 Pacific. That's why resending sometimes worked. Half the prompts still went through.

Two lookalikes waste people's time. status.gemini.com is the status page of Gemini Exchange, a crypto exchange, not Google. And if you call Gemini through an API key on Vertex AI, your incidents post on Google Cloud's status page instead, which logged a 118 minute spike in Vertex AI Gemini API errors on 27 February 2026.

Why does Gemini say something went wrong on one account only?

When a second account works on the same device, the block is on your account, and Google's help pages name the rules that cause it. Most are about age, account type and where you are. They're listed below as Google states them in October 2026, with the fix for each:

Admin fixes aren't instant. Google's admin page for the Gemini app says an access change "can take up to 24 hours but typically happen more quickly." So if your admin flipped the switch this morning, give it a day before you report a fault.

The country list deserves a closer look. Google's web app availability page says "over 230 countries and territories", and we counted 242 entries on it on 11 October 2026. Afghanistan, Belarus, Cuba, Iran, North Korea, Russia and Syria aren't among them. The mobile app page is narrower still, at "more than 150 countries".

One rule has no fix you can apply. Google adds that it uses "signals and data to help verify that accounts have a consistent history of abuse-free activity" and works to make sure "there are real users behind accounts". It doesn't say which signals count. If an account meets every rule above and still gets the plain message at sign in, Google's own advice is to try again later, and feedback is the only channel.

What if Gemini is down and the work can't wait?

Use another assistant until the incident closes, because nothing on your side shortens one. ChatGPT and Claude have their own versions of this wall: ChatGPT's something went wrong error and Claude's overloaded error cover them, with their own status pages.

Whizi, which publishes this page, puts Gemini, GPT and Claude models in one picker. Gemini starts on the Pro plan at $29.99 a month, where a Gemini Flash message costs 1 credit and the Gemini Pro row 10, out of 2,500 credits a month (Gemini in Whizi). Where it loses: the $15.99 Starter plan has no Gemini model at all, and Whizi has a generic error of its own, "Something went wrong. Please retry." (every Whizi send error, quoted). It can't import your Gemini history either. Its import takes ChatGPT and Claude exports only.