Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
US retailer Target faced issues with its online presence yesterday, Tuesday 24th September 2019, when its website experienced an outage. The downtime not only impacted Target’s sales website but also its mobile application as well as payment processing in-store.
Responding to CNBC the retailer told the news channel that “as the result of a payment processing issue, some Target guests were temporarily unable to make purchases at Target stores and at Target.com, [but that] within an hour, technology teams identified and began to remedy the issue to limit the impact on our guests. This was not a security-related issue. We apologize for the inconvenience and appreciate our guests’ patience.”
Target has experienced several issues with its systems this year. Earlier in June, its in-store registers were offline for two hours following an “internal technology issue”. After that incident Target’s shares listed on the New York Stock Exchange fell almost 2% with industry experts suggesting that the inability to take payments could have cost the company as much as USD $100m in lost sales.
With 7.3% of all Target’s US$ 76.4bn revenue originating online the retailer will want to ensure that as Black Friday and the holiday season approaches that its systems are robust and not going to experience similar issues at such an important time for sales. For Target not only will the downtime have hurt sales, but longer term it will also be concerned about the reputational fallout, with it being reported that around 1,100 tweets on social media about Target’s issues during yesterday’s outage.
See Also:
StatusCake Team
Share this
More from StatusCake
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026