Gemini error codes: what “Something went wrong” 9, 13, 1095, 1097, 1099, 1152 and 1185 mean
The message
Something went wrongWhat it means
Google doesn't publish what the numbers mean. Going by the threads, they fall into three groups: one chat that's stuck, one account that's blocked, or an outage hitting everyone.
What to do
Open a new chat and send a short prompt. If that fails, try another Google account. If nothing works on any account, check Google's status page and wait.
When the Gemini app can't answer, it shows a short message with a number in brackets at the end:
Something went wrong (1097)Google doesn't say what any of the numbers mean. There's no list in the Gemini Apps Help Center as of October 8, 2026, and the only official advice is to send feedback. So we've read the community threads code by code, along with what Google's volunteer Product Experts and, in one case, Google Workspace support said. Each code below has its own page with the sources.
The codes, what they point to, and what to try
| Code | What the reports point to | Try first |
|---|---|---|
| 1097 | Google Workspace (work or school) accounts. Workspace support called it a global issue in May 2026. | Test a personal account. If that works, your admin checks Gemini is on and opens a Workspace ticket. |
| 1095 | Every prompt refused, often after a long session. Product Experts treat it as a stuck sign-in. | Sign out of every Google account in the browser, sign back in, start a new chat. |
| 13 | Follows one Google account on every device, often on one kind of request such as a photo upload. | Same prompt from another account; if it works, send feedback with logs from the failing one. |
| 1185 | One conversation stops answering while new chats work. A Product Expert says Google is aware. | Edit the last prompt that got a good answer and resend it, or branch a new chat from it. |
| 1099, 1076, 1096 | Either an outage (June 10, 2026 was a big one) or a single stuck chat. | New chat with a short prompt. If nothing works on any account, it's an incident: wait. |
| 1152, 11 | The reply couldn't finish, mostly in long or heavy chats. | Retry once, then branch from the last good reply or move to a new chat. |
| 1155 | A burst of reports on October 8, 2026, when Reddit filled with “Gemini down” threads. One poster wrote that Google called it a known issue. | Treat it as an outage: check another account, then wait. No status-page entry for it when we looked. |
| 9 | A chat that broke after a Google Docs or Drive link or attachment. | Edit the last prompt (take the Docs link out) and resend, or start a new chat. |
| no number | “Something went wrong. Try again later.” on the web for one account, while the mobile app works. | Check the account against Google's sign-in requirements and fill in your first and last name. |
Sorting yours in two minutes
The numbers matter less than where the failure lives. Three quick tests narrow it down, and they work for a code that isn't on the list too.
- Open a new chat and send something short. If that answers, the problem is the old conversation (9, 1152, 1185 and some 1099 reports work like this). Branching from the last good reply usually rescues it.
- If new chats fail too, sign in with a different Google account in a private window. If that one works, it's your account: 13, 1095, 1097 and the no-number line all behave this way. On a work or school account, that usually means your admin.
- If every account fails, it's probably Google. On June 10, 2026 the app showed 1076 and 1099 to a lot of people at once, in several languages, and waiting was the only fix. Google posts Workspace incidents on its status dashboard.
Whatever you find, send feedback from the failing account (Settings & help, then Send feedback). It's the one route Google itself offers.
The same errors in German, Spanish and Italian
The number stays the same in other languages, so a search like "Gemini Fehler 1097" or "errore 1097 Gemini" lands on the same code. During the June outage, heise saw the German app show „Ein Fehler ist aufgetreten, – versuche es noch einmal (1076)“, and a Spanish site quoted "Se ha producido un error (1076)" and "(1099)". Google's Italian status page called them errors of the type "Si è verificato un errore". We haven't found the translated screen for every code, but nothing suggests the numbers change.
Codes we looked for and couldn't explain
We also searched for 1013, 1089, 1098, 1100, 1125, 1151, 1153, 1154 and 1184, in September and again in October. None of them turned up a thread with enough detail to say what was going on, so they don't get pages (we'd rather leave a gap than guess). If yours is one of these, the three tests above are still the quickest way to find out whose problem it is.
Other lines the same feature prints
Match yours against these if the one at the top of the page is not quite it. They come from the same code and mean related things.
Something went wrong (1097)Something went wrong (1095)Something went wrong (13)Something went wrong (1185)Something went wrong (1099)Something went wrong (1076)Something went wrong (1152)Something went wrong (9)Something went wrong (1155)Something went wrong. Try again later.