More downtime for Salesforce
Users experienced outages or lag in loading for much of today.
Salesforce users complained of an outage, or at least very slow load times, beginning around 8.20 a.m. EST today. The quantity of complaints to Downdetector.com peaked around 10 a.m.
By early this afternoon, Salesforce was reporting that the incident had been mitigated for all customers, save for those using one instance (or server), NA151, which was requiring a manual re-start.
The outage (or long lag) is nothing new for Salesforce customers. On May 11 of this year, a widespread outage affected a number of Salesforce products, and, according to reports, even took down the status page. The May outage was attributed to a DNS issue (Microsoft Azure had reported the same cause for an outage in April).
Salesforce customers also experienced intermittent connectivity problems on June 9.
Why we care. It just makes the whole digital eco-system feel so fragile. We’re always connected — except when we’re not. And Salesforce is a foundational element in the marketing tech stack for so many businesses. But taking a glass half full perspective, maybe this should remind us how lucky we are. If it wasn’t possible to conduct business remotely and digitally almost all the time, what would the solution to the last year and a half have been?
The post More downtime for Salesforce appeared first on MarTech.
About The Author
Kim Davis is the Editorial Director of MarTech. Born in London, but a New Yorker for over two decades, Kim started covering enterprise software ten years ago. His experience encompasses SaaS for the enterprise, digital- ad data-driven urban planning, and applications of SaaS, digital technology, and data in the marketing space. He first wrote about marketing technology as editor of Haymarket’s The Hub, a dedicated marketing tech website, which subsequently became a channel on the established direct marketing brand DMN. Kim joined DMN proper in 2016, as a senior editor, becoming Executive Editor, then Editor-in-Chief a position he held until January 2020. Prior to working in tech journalism, Kim was Associate Editor at a New York Times hyper-local news site, The Local: East Village, and has previously worked as an editor of an academic publication, and as a music journalist. He has written hundreds of New York restaurant reviews for a personal blog, and has been an occasional guest contributor to Eater.
(37)
