Topical, given the clocks are going back tonight, so I thought it might be useful to have a place where we can see what the various current account providers deal with the clock change.
Monzo - no shut down
Starling - no shut down
Dozens - no shut down
Nationwide - Closed 12:01am (BST) to 6am (GMT) - card payments, ATMs and internet banking still work, but no transfers / faster payments
If you did mean Monzo, then no mainframes included: I think it’s mostly micro-services written in Go and hosted on AWS (I’m hoping that someone like @bee will correct me if I’m wrong!).
If we take the jargon out if it, yes, Starling provides a BaaS (banking as a service) product. And has its own direct connections to things like faster payments (which are referenced in @bee’s link).
They do, though, consume other services which are BaaS-like, if not BaaS. For example, I think they use a third party for payment processing (it was GPS - it might still be).
If you look at Dozens, they provide an aggregated BaaS service - basically orchestrating existing BaaS-like components into something that looks a bit like a bank (Clear Bank, Marqueta…).
So basically these things aren’t quite as clear cut as they sometimes seem.
Hopefully, we don’t get a bunch of people here trying to make this a massive issue with the high street banks despite the fact most people won’t notice anything.
Worst banks ever when they do this, years and years back Halifax would take its ATM network offline at around 2am on a Saturday night / Sunday morning. No chance of getting money out when you needed a taxi back home, steaming with a doner kebab in one hand.
Edit - wouldn’t affect me these days, if I do go out I don’t tend to leave the pubs and clubs until 6am 🤦
In the past Lloyds Bank Cashpoints™ would go offline every night for about half an hour just after midnight, with something like a four hour outage EVERY Sunday morning.
I agree with @Peter_G, it’s less the inconvenience for me (as I’m usually asleep, though I did used to work nights in my current job) but more the fact that in the modern world, this is just a signal that the tech side of most banks is just an unstable pile of shit bolted on top of decades–old COBOL mainframe. At some point, most high street banks are going to have to bite the bullet and upgrade, yet seem to be constrained by traditional thinking in the boardroom.
6 Likes
phildawson
(Sorry, I will have to escalate this.)
15
Due to essential maintenance faster payments made in Santander between 11pm and 2pm may not show in the recipient account until after this window
AIB bank always make internet banking unavailable at 3am uk time for a short while think that’s when they do updates to their system every night and after that outgoing payments like standing orders direct debits show up
NatWest, RBS, Ulster Bank (and the rest of the group) also do this every night at around 1:30am.
A longer outage during the clock change does make sense, though, for banks with older systems. Both because of the potential that the “same hour” occurring twice could cause problems on some of their more simplistic old systems and because of the need to keep everything in sync. If the clocks need to be manually changed, then they have to take everything offline to change the clocks on every system at once. Otherwise everything would be out of sync which would risk things not working properly.
Computers also usually calculate time in seconds from midnight on the 1st of January 1970 (for historical reasons) so a jump probably has to be manually programmed in on the very old mainframes - some of which run code written in COBALT and use ticker-tape emulation software to produce the “expected” output.
Raise a complaint with Monzo specifically about this being caused by clock-change issues and they should refund the interest and alter what they report to CRAs to show that you haven’t actually used your overdraft.
Hopefully it will also prompt them to consider actually moving their clocks in the future to match real U.K. time year-round instead of “fixing” them at GMT.