The myth is that an “is Gemini down” error is an Alphabet earnings event. GOOGL closed Thursday 8 October 2026 at $348.29, down $2.21, or 0.63 percent, from Wednesday’s $350.50, the last official cash close. Friday’s session had not opened when these prices were pulled. Users posted error 1155, including “Something went wrong. Please try again. (1155).” Error 1099, with 1076, is what Google listed on the 10 June Workspace incident. An 8 October Windows Report headline also names 1099, but the body records “Something Went Wrong (1).”
The outage blogs miss the threshold. Google Cloud revenue for the quarter ended 30 June 2026 was $24.768 billion, or $272.2 million a day over 91 days. At a 35.59 percent cloud margin, a full-day credit is about $96.9 million, 0.24 percent of Alphabet’s $40.770 billion of operating income. About 4.21 such days equal 1 percent of that profit, and only if the whole cloud book goes dark. Friday’s Workspace file has no October Gemini incident.
Key facts
- Nasdaq, Thursday 8 October 2026: GOOGL closed at $348.29, down $2.21, or 0.63 percent, from $350.50, on 23,511,140 shares. A Friday premarket print of $351.00 at 8:18 a.m. Eastern, up 0.78 percent, is not a close. Source: Nasdaq.
- Alphabet Q2 2026, filed 22 July: revenue $119.796 billion, up 24 percent. Google Cloud $24.768 billion, up 82 percent from $13.624 billion. Cloud operating income $8.814 billion. Company operating income $40.770 billion. Property and equipment purchases $44.924 billion. Source: Exhibit 99.1.
- Sundar Pichai, in that release: nearly 90 percent of the Fortune 100 were using Gemini Enterprise, models were processing 22 billion API tokens a minute, and the Gemini App had 950 million monthly active users.
- Workspace incident, 10 June 2026, 10:20 to 17:30 UTC, medium severity: codes 1099 and 1076, a 50 percent prompt error rate, and a backend database failure. Source: the incident.
- Tom’s Guide, 8 October, 16:20 to 17:26 UTC: Downdetector moved from about 1,700 to over 5,000, then 4,811, then about 2,000, then 355. The code was 1155. The status line read “All systems operational.” Source: Tom’s Guide.
- Windows Report, 8 October: 4,412 reports at 16:07 UTC, and a screen that said “Something Went Wrong (1).” The headline also lists 1155 and 1099. The dashboard showed no Gemini issue. Source: Windows Report.
- Ascendants, citing GV Wire: nearly 10,000 reports by 9:40 a.m. Pacific, codes 13 and 1155, and a split of 69 percent AI generation, 13 percent website, 12 percent app. That peak does not match Tom’s Guide. Source: Ascendants.
What just happened, and why the obvious reading is wrong
The obvious reading is that Gemini went down and Alphabet should wear it. The notices are real. The earnings inference is not. Tom’s Guide opened its blog near 1,700 Downdetector reports, watched them clear 5,000, and later logged 4,811 while Google’s status line still said the systems were operational. The last update put reports at 355. On that account the spike lasted about an hour and never reached the dashboard.
Windows Report timed 4,412 reports at 16:07 UTC across several countries. The writer typed a greeting and got “Something Went Wrong (1).” The headline pairs 1155 with 1099. The body does not quote a 1099 screen. Use the headline as the publication’s label, not as a second capture of the code.
@BuildWithNK posted at 16:35 UTC, “Is Gemini down right now?” and “Something went wrong. Please try again. (1155).” At 17:00 UTC the same account said Gemini looked “back to normal.” @instatusnow wrote that chats would not start, “error 1155 included,” a post that had drawn 11,327 impressions. A paid Gemini Advanced user told @sundarpichai that a storage warning was followed by 1155. None of those posts is a Google statement. They fix the code consumers saw.
Do not import June’s 1099 and call Thursday a rerun. On 10 June Google posted a medium Workspace incident. Users “may have seen ‘Something went wrong’ errors (codes 1099, 1076).” The company later wrote: “From preliminary analysis, the issue was triggered by a performance issue in our backend database which impacted the retrieval of Gemini App tools catalog.” The same page records a 50 percent prompt error rate and read contention in the tool-metadata database. The incident clock runs 10:20 to 17:30 UTC. Friday’s download of the same list has no October twin.
Ascendants, citing GV Wire, put the same afternoon near 10,000 reports, with a 69 percent share on AI generation. That peak disagrees with Tom’s Guide, and neither count is a credit exhibit. Google had not acknowledged Thursday in the pages fetched here.
Who is exposed
Two groups share the product name. One group types “is Gemini down” and refreshes a chat. Pichai said on 22 July that the app had 950 million monthly active users, enough for a tracker to fill in an afternoon. The other is the enterprise book: nearly 90 percent of the Fortune 100 on Gemini Enterprise. Only a Workspace failure has a public incident template.
Allocators are exposed through the equity. Class A, B, and C shares outstanding were 12,230 million at 30 June. Applying Thursday’s Class A close to all 12,230 million shares is $4.260 trillion. Class C does not print the Class A price every day, and the count is a quarter old, so this is a scale sketch, not a published market cap. A $96.9 million operating-income hole is noise against that equity unless the market treats the outage as a signal about the $44.924 billion of property and equipment bought in the June quarter, or the $49.6 billion equity raise and $20.3 billion of notes issued to fund AI infrastructure.
FinanceFeeds has reported Google’s 890 megawatt, $4.3 billion nuclear arrangement with Constellation. The Super Micro note is the hardware side, including a Google TPU test. A multi-day Workspace failure would matter, because those customers are the Fortune 100 cohort Pichai cited.
What the tape and the filings show
The closes are Nasdaq official daily prints saved for this piece. Thursday is the last bar. Friday’s premarket print is not drawn. June and September are the last two Gemini incidents on the public list. October is the absence of one.
| Session | What Google posted | Codes | Outside reports | GOOGL close |
|---|---|---|---|---|
| 10 June 2026 | Medium Workspace incident, 10:20 to 17:30 UTC. Database load on the tools catalog. | 1099 and 1076. Google: 50 percent of prompts failed. | Posted by Google. | $356.38, down 2.16 percent from $364.26. |
| 11 Sept 2026 | Low severity. Gemini 3.1 Pro, 6:00 to 13:22 Pacific. A rollout, then a code change. | No numeric code in the text. | Google said a subset of users. | $338.50, up 1.77 percent from $332.60. |
| 8 Oct 2026 | No October Gemini row. Newest item in Friday’s file begins 25 September. | 1155 in user posts and Tom’s Guide. 1099 in a Windows Report headline only. | About 1,700 to above 5,000. 4,412 at 16:07 UTC. Near 10,000 via GV Wire. | $348.29, down 0.63 percent, volume 23,511,140. |
Thursday’s volume is ordinary: 23.5 million shares, against 20.9 million on Wednesday. The session that looked like a scare was 23 July, the day after the Q2 release, when the close was $317.69 on 69.4 million shares. From the 21 July close of $347.15 that is 8.49 percent. Other income included about $98.0 billion of gains, mostly unrealized, which is why diluted EPS printed $9.11, up 294 percent. Operating income rose 30 percent, to $40.770 billion. Using $9.11 as the run-rate reads the securities book, not the cloud.
The file’s highest close is $402.62 on 13 May 2026. Nasdaq’s quote page lists a 52-week range of $235.84 to $408.61. The $408.61 figure is above every close in the saved file, so it is not used as a close. From the 31 December 2025 close of $313.00, Thursday is up 11.27 percent. The 20-session average is $345.26, so the stock is 0.87 percent above its recent mean.
FinanceFeeds’ 4 October note put a $2 price on Gemini 4 Argon against an Alphabet close of $343.50. The saved series has that close on 2 October. Thursday’s $348.29 is $4.79, or 1.39 percent, above it. The product got a posted price. Thursday’s outage did not get a posted incident.
What Alphabet has said, and what it has not
Pichai’s last full-quarter statement on this product is the 22 July release, not a Thursday post. He said: “Q2 was an amazing quarter, with Alphabet revenues growing 24% year-over-year and Google Cloud revenues accelerating to 82% growth, driven by demand for AI infrastructure and AI solutions. It’s great to see wide adoption of Gemini Enterprise, with nearly 90% of the Fortune 100 using it.” The sentences are in Exhibit 99.1. He also said models process 22 billion API tokens a minute. It is not a comment on 1155.
The last named comment on a real Gemini outage is from June. Josh Woodward, whom CNET identified as vice president of the Gemini app, said on 10 June, as quoted by 9to5Google: “Gemini is currently experiencing an outage. We’re on it and will get everything back up ASAP. Some of the fixes are in, the rest coming very soon.” 9to5Google timestamped that at 10:31 a.m. Pacific. CNET wrote that Google declined further comment on prevention. The pattern is a named executive during a dashboard incident, then silence.
Thursday and Friday do not match it. Tom’s Guide wrote that Google never acknowledged the outage. Windows Report wrote that Google had not confirmed a cause. The incidents file’s newest begin-time is 25 September. The last Gemini rows are 11 September and 10 June. No fetched post adds a new sentence from Pichai or Woodward on 1155. @umairabowath was still asking “is gemini down” at 12:20 UTC on Friday.
On 11 September Google posted a low-severity Gemini 3.1 Pro error, blamed a rollout, and closed it the same day. GOOGL closed up 1.77 percent. A posted model error did not become an earnings story. An unposted afternoon of 1155 has less behind it, unless it starts a series.
Where the liability actually sits
The June page is frank. Google apologized to business customers, said it knew how much they rely on Google Cloud, and described a one-minute cache, a hot database shard, and a query spike that amplified load more than tenfold when the cache missed. Fixes were rate limits, a 20-minute cache, shorter deadlines, and a promise to rebuild the index. Customers can point at that document.
Thursday has no equivalent. Credits in a cloud contract usually key off the vendor’s incident, its duration, and the named service, not a third-party complaint count. This piece does not have any customer’s order form, so it invents no credit percentage. The narrower point is that without an incident row there is no public number to attach to a request. Readings of 4,412 and “nearly 10,000” do not agree, and neither is a substitute.
Even the June page disagrees with itself on the clock: one passage says 14 hours and 49 minutes, and the incident object runs 7 hours 10 minutes. A buyer will not find one duration. No fetched regulator page opened an October case. The exposure is Fortune 100 workflows that stop, and a status system that did not trip.
Bull, base, and bear
The spot is Thursday’s close, $348.29. The horizon is 31 October 2026, this desk’s window, not a date Alphabet has announced. The September-quarter release time was not in the documents fetched here. The three prices are not street targets.
| Case | Price | Versus $348.29 | What has to be true |
|---|---|---|---|
| Bull | $375.46 | up 7.80 percent | No multi-day Workspace incident is posted before 31 October, and the close retraces halfway to the 13 May high close of $402.62. |
| Base | $345.26 | down 0.87 percent | Error 1155 stays off the dashboard, and the price sits on the 20-session average of the saved closes. |
| Bear | $318.73 | down 8.49 percent | A posted Workspace outage lasts on the order of 4.21 full cloud-days of credits, or the market applies the 21 July to 23 July drawdown anyway. |
The bull is two saved closes. Halfway from $348.29 back to $402.62 is (348.29 + 402.62) / 2 = $375.455, rounded to $375.46. The gap is $27.17, and $27.17 / $348.29 is 7.80 percent. Buyers would be paying halfway back to a high not printed since May. The 82 percent cloud growth is already in the June print.
The base is the recent mean. The last 20 closes sum to $6,905.28. Divided by 20 that is $345.264, rounded to $345.26. Thursday is $3.03 above it, or 0.87 percent. It does not book a cloud credit, because Google has not said the cloud book was down.
The bear borrows a move the market has made and applies it only if the outage crosses the earnings line. From $347.15 on 21 July to $317.69 on 23 July is $29.46, and $29.46 / $347.15 is 8.49 percent. That was the post-earnings session, on 69.4 million shares, not an outage. Applied to Thursday, 348.29 x 317.69 / 347.15 = $318.73, also 8.49 percent under the spot. The template is an 8.49 percent drawdown, not a trip to the 52-week low.
The duration link is the 4.21 days. Cloud revenue of $24,768 million over 91 days is $272.2 million a day. The margin is $8,814 / $24,768 = 35.59 percent, so a fully credited day is about $96.9 million. One percent of $40,770 million of operating income is $407.7 million, and $407.7 / $96.9 = 4.21 days. The bound pretends every cloud dollar goes dark, which a Gemini app error does not do. An earnings problem needs the dashboard open for days, with the Fortune 100 cohort down. An hour does not get there.
What happens next
Through Monday 12 October, watch the Workspace incident list, not another tracker screenshot. Google posted June and September because its monitoring tripped. Friday’s file had no October row. If that is still true on Monday, there is no incident number, and 1155 stays a support ticket. A new row, with a begin time and a service name, would replace the file this piece used.
By 31 October the base at $345.26 is the path if the dashboard does not change and the stock does what the last 20 sessions did. The bull at $375.46 needs a 7.80 percent retrace without a multi-day incident.
The bear at $318.73 is the path if a posted Workspace outage runs toward the 4.21-day bound, or if the market applies the July drawdown before the duration is known. A repeat of Thursday, an hour of 1155 with the status page still green, does not get there. The tell is a named Google executive, as Woodward was on 10 June, or a new incident with a service name and a clock.
Frequently asked questions
Is Gemini down?
Not on Google’s incident list. The Workspace file downloaded Friday 9 October has no October Gemini entry, and Tom’s Guide quoted a Thursday status line of “All systems operational.” Users did post error 1155, and one X account was still asking at 12:20 UTC on Friday. An afternoon of failed chats is a real complaint. It is not the 10 June Workspace outage. GOOGL’s last official close was $348.29 on Thursday, down 0.63 percent.
What is Gemini error 1155?
Tom’s Guide wrote on 8 October that 1155 “simply says ‘Something went wrong.'” A user post the same afternoon quoted “Something went wrong. Please try again. (1155).” Google has not defined 1155 on the incident pages used here. Windows Report’s writer got “Something Went Wrong (1)” instead. Treat 1155 as Thursday’s user-reported failure code, not as a published root cause, and not as the June codes.
What is Gemini error 1099?
On 10 June, Google wrote that Workspace users may have seen “Something went wrong” with codes 1099 and 1076. That incident is on the dashboard and ran about seven hours on the incident clock. The 8 October Windows Report headline also names 1099, but the body describes “Something Went Wrong (1),” not a quoted 1099 screen. June’s code and Thursday’s headline are not one outage. The code with a cause attached is the June code.
Did GOOGL fall because Gemini was down?
The stock closed at $348.29, down 0.63 percent, on 23.5 million shares. That volume matches recent sessions, not the 69.4 million shares on 23 July, when the close was $317.69 after earnings. The 10 June incident fell on a 2.16 percent down close, to $356.38. Neither print proves the outage set the price. Thursday did not trade like an earnings problem. Friday’s $351.00 premarket print was a bounce, not a close.
When does a Gemini outage hit cloud earnings?
When it is long enough, and wide enough, to credit cloud use. One day of the Q2 cloud run-rate is $272.2 million. At a 35.59 percent margin that is about $96.9 million, or 0.24 percent of quarterly operating income of $40.770 billion. About 4.21 such days equal 1 percent, and that assumes the entire cloud book is credited. A Gemini app error is a slice. An hour that never reaches the status page is not the 4.21-day case.
Who is exposed if Gemini fails at work?
Pichai said on 22 July that nearly 90 percent of the Fortune 100 used Gemini Enterprise, and that the app had 950 million monthly users. June’s incident hit Workspace and said so. The October pages fetched here do not. Until a dashboard row says enterprise tenants were down, the exposure is a support queue, not a credit.
This is not financial advice.