Goldman Sachs outages and problems
User reports, last 24 hours
40 reports in total, counted in 15-minute windows
In the last hour, 1 problem report came in for Goldman Sachs, and at this time of day there are usually almost none. Over the last 24 hours there were 40 reports. Most recent reports were about login (50%) and website (25%). The last spike in reports was 3 h ago and lasted 19 min. These are user reports from the US, where most people report Goldman Sachs problems.
- NormalClose to the usual level24 h · 40 reports
- ElevatedMore than 1.5 times the usual levelNone in this chart
- OutageMore than twice the usual level and far above the day's averageNone in this chart
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 40 user reports came in for Goldman Sachs. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 9 reports, about 3 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Goldman Sachs in November 2026
- Problem reports in November (since 5 November)
- 40
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for Goldman Sachs.
Share of 8 recent reports that said what was wrong.
Goldman Sachs problem spikes, last 30 days
Since 5 November, Goldman Sachs had no outage spikes, but 1 period of elevated reports.
-
Elevated reports
Thu 5 Nov, 16:47–17:06Lasted 19 min10peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 5 November 2026. Monthly reports for all services
How to fix Goldman Sachs not working
Goldman Sachs is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach goldmansachs.com over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not Goldman Sachs.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
Problems at the same time as Goldman Sachs
Since 5 November, Goldman Sachs's only spike in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
During the latest spike
Goldman Sachs: Thu 5 Nov, 16:47 to 17:06
- Facebook, outage,4 Nov 13:47 to 19:51
- Reddit, outage,4 Nov 21:17 to 20:02
- Odido, outage,01:17 to 16:47
- NTT Docomo, outage,03:17 to 19:17
- Klarmobil, outage,05:32 to 20:02
- Sainsbury’s, outage,07:33 to 20:03
- Aruba, outage,09:17 to 17:02
- GOV.BR, outage,10:32 to 20:02
93 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
Goldman Sachs IP address, servers and network
Checking goldmansachs.com from our server…
Contact Goldman Sachs support
Tip: Goldman Sachs doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
How we track Goldman Sachs
The status on this page comes from user-submitted problem reports for Goldman Sachs, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Goldman Sachs, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Goldman Sachs doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.