Wolfram Cloud returns 503 errors as user reports two-day outage
The failure blocks the service's main entry point, while Wolfram's other public websites remain reachable.
By Ryan Merket · Published
Primary source: Hacker News
Why it matters
Wolfram Cloud hosts executable notebooks, APIs and scheduled programs, so a prolonged 503 can interrupt production workloads as well as browser access.
Wolfram Cloud was returning an HTTP 503 error on September 4th, blocking its main web interface as a user reported that the service had been unavailable for more than 48 hours.
The report surfaced in a discussion on Hacker News, where the poster said Wolfram Cloud had displayed the error for two days and appeared to be undergoing an update. RuntimeWire independently received a 503 response from the main Wolfram Cloud address. The reported duration could not be independently established from the error response.…
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.