TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

UK bank fined £49M over IT system meltdown

139 点作者 shaman1超过 2 年前

13 条评论

azalemeth超过 2 年前
I have a bank account with TSB and got compensation as a result of this mix-up.<p>Some rather personal experiences of the fiasco:<p>– Rather pointlessly, the website changed from being mostly static to entirely written in a very JS-heavy, &quot;dynamic&quot; way. I still can&#x27;t use it in my normal browser (FF) with its extensions because it relies heavily upon CORS requests and referrer information that my somewhat privacy-paranoid extensions block.<p>– This was introduced at the time of the switchover, and until that point the IT system used looked identical between Lloyds, TSB and Halifax &#x2F; BOS systems (I have accounts with some of those)<p>– The online browser-based system was telemetry and JS heavy, replacing a far leaner page<p>– I was unable to log in during the time of the fiasco, mostly due to 403 errors or timeouts. Often the page would just hang as an async request wasn&#x27;t answered.<p>– Once I did manage to log in, I was amazed to see another person&#x27;s account details (!!!), replete with (their) name and statement.<p>– I was unable to use online banking to pay bills or check my balance – I could see someone else&#x27;s account in detail but was too honest to do anything with that knowledge. I can&#x27;t remember if my card stopped working but I was effectively forced to make other arrangements for quite an extended period of time.
评论 #34066485 未加载
评论 #34065506 未加载
评论 #34064928 未加载
评论 #34067518 未加载
评论 #34067401 未加载
评论 #34066836 未加载
arpinum超过 2 年前
The 250+ page analysis of the incident was an excellent insight into how large IT projects fail: <a href="https:&#x2F;&#x2F;www.tsb.co.uk&#x2F;news-releases&#x2F;slaughter-and-may&#x2F;slaughter-and-may-report.pdf" rel="nofollow">https:&#x2F;&#x2F;www.tsb.co.uk&#x2F;news-releases&#x2F;slaughter-and-may&#x2F;slaugh...</a><p>money quote: &gt; This situation has all the hallmarks of business management strong-arming the IT organization into an unrealistic timeline. When business leaders push for overly-aggressive timelines, or regulators ask for multiple competing risk frameworks and excessive after-the-fact incident reporting, this all puts a strain on the delivery organization’s ability to untangle the complexity before ‘go live’.
评论 #34064813 未加载
评论 #34065289 未加载
评论 #34064855 未加载
heurisko超过 2 年前
2008: &quot;The UK-based IT department of the fifth largest bank continues to dwindle as more jobs go overseas... This round of cuts, starting in June and lasting 12 months, involves up to 250 permanent IT roles and 200 contractors from the bank&#x27;s technical delivery division, responsible for software development and design.&quot; [1]<p>2018: &quot;Timeline of trouble: how the TSB IT meltdown unfolded&quot;. [2]<p>It&#x27;s probably more complicated than that, but perhaps not much more complicated.<p>[1] <a href="https:&#x2F;&#x2F;www.itpro.co.uk&#x2F;197982&#x2F;lloyds-tsb-cuts-more-uk-it-jobs" rel="nofollow">https:&#x2F;&#x2F;www.itpro.co.uk&#x2F;197982&#x2F;lloyds-tsb-cuts-more-uk-it-jo...</a> [2] <a href="https:&#x2F;&#x2F;www.theguardian.com&#x2F;business&#x2F;2018&#x2F;jun&#x2F;06&#x2F;timeline-of-trouble-how-the-tsb-it-meltdown-unfolded" rel="nofollow">https:&#x2F;&#x2F;www.theguardian.com&#x2F;business&#x2F;2018&#x2F;jun&#x2F;06&#x2F;timeline-of...</a>
评论 #34064401 未加载
评论 #34066544 未加载
jayceedenton超过 2 年前
I will always remember this incident as the time when the UK general public were exposed, en masse, to Spring error messages.<p>The confusion caused by ordering a member of the general public not to request a bean from a bean factory in a destroy method implementation still makes me laugh, even now.
评论 #34066134 未加载
评论 #34065354 未加载
评论 #34065377 未加载
评论 #34069752 未加载
评论 #34070956 未加载
jesusthatsgreat超过 2 年前
Sounds like classic A type personalities with zero technical chops deciding how long a technical project should take to further their own agenda:<p>&gt; The Migration Programme experienced delays from the outset and fell behind the IMP timings. While progress had been made, on 20 September 2017 the firm decided that the Migration Programme would have to be re-planned. However, nine days after it had resolved to re-plan, and before it had concluded its re-planning exercise, TSB publicly announced it would now migrate in Q1 2018.
UltraViolence超过 2 年前
It&#x27;s not just the CEO who should&#x27;ve been fired. The COO, CTO and CIO also should&#x27;ve left the building with a cardboard box in their hands.<p>This is a shameless indulgence in incompetence and recklessness. They didn&#x27;t even bother to test large swaths of the transitional data or have a fallback plan if things went wrong.<p>Most likely their customers will now simply leave and the bank will be shut down.
VincentEvans超过 2 年前
I sneer at the emphasis on “1.4 billion records!” in the article as if it’s a lot.<p>At a recent place of employment I created and was responsible for a database that had about that many records and in actuality was a single 2tb postgres db and completely unremarkable.<p>I never claimed to have worked with big data.
评论 #34065710 未加载
评论 #34066467 未加载
评论 #34065350 未加载
评论 #34064840 未加载
petepete超过 2 年前
Hopefully Virgin Money will get one too. They broke their Android app earlier this year and since they make you verify web logins using the app I was unable to access any of my business accounts for ~3 weeks.<p>If something really urgent had come up I could have done what I needed via telephone banking or in a branch, but it was a huge pain in the arse because of a single point of failure.<p>Just let me use a Yubikey as my second factor damnit.
评论 #34065904 未加载
orf超过 2 年前
The actual report by the FCA: <a href="https:&#x2F;&#x2F;www.fca.org.uk&#x2F;publication&#x2F;final-notices&#x2F;tsb-bank-plc-2022.pdf" rel="nofollow">https:&#x2F;&#x2F;www.fca.org.uk&#x2F;publication&#x2F;final-notices&#x2F;tsb-bank-pl...</a>
评论 #34064572 未加载
mellosouls超过 2 年前
Discussed variously at the time, eg.<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=16910947" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=16910947</a><p>Others<p><a href="https:&#x2F;&#x2F;hn.algolia.com&#x2F;?dateEnd=1600300800&amp;dateRange=custom&amp;dateStart=1515110400&amp;page=0&amp;prefix=false&amp;query=tsb&amp;sort=byPopularity&amp;type=story" rel="nofollow">https:&#x2F;&#x2F;hn.algolia.com&#x2F;?dateEnd=1600300800&amp;dateRange=custom&amp;...</a>
kmlx超过 2 年前
i remember this. for at least a week people couldn&#x27;t access their money. it was chaos. the bank lost lots of money and customers due to this botched transfer.
评论 #34064498 未加载
评论 #34064534 未加载
sherr超过 2 年前
Not my main bank so this did not affect me badly but their online (web based) banking portal is still glitchy and not very good.
评论 #34072068 未加载
JCM9超过 2 年前
I remember when this all happened. Would be interesting if it was the result of some really interesting technical bug that nobody could have foresaw followed by a fascinating effort to save the migration.<p>In fact it was all quite boring and simply the result of the sheer incompetence of the bank’s leadership in running bank IT.