The uptime of cash in my wallet is pretty close to 100%. It's extremely rare that I have to use it, but it's incredibly convenient to have each time it's required
If you look at uptime as discrete set of events when you need to pay for something, my cash uptime is not looking great nowadays. "Sorry I can't break that" or machines accepting coins which you don't have at hand. Just to be clear I despise CC companies the system is broken in many ways.
Thanks, your comment was the first one which linked the two.
Revolut is the biggest private company in all of Europe.
Perhaps it’s me but I still find it kinda wild that a single power outage in London can shut down Google DC and it can lead to Revolut shutting down for some time disrupting much of the economy which depended upon it
Perhaps this could’ve been prevented, which makes me wonder how much of code written at Revolut is ai generated and its ai policy?
If their infrastructure is tightly coupled to a cloud provider in a single region then that's what they need to be work on and not necessarily their AI policy.
My revolut cards (both google pay and actual physical cards) were failing to process payments and had to use my backup card from a traditional bank instead
From what I've seen—personally and from a variety of online sources—there's intermittent availability of basically everything, which means you might be able to access the app, or you might be able to pay by card, but that's going to change potentially from minute to minute, with an average of somewhere around 10% uptime. (Which, of course, means that you, personally, might just be in the 90% of downtime all the time until it's resolved.)
Take with appropriate seasoning, given its anecdotal nature.
Once again, blockchains that use USDC continue to run without any serious outages for years. I just paid for an item with USDC (using Phantom Wallet) right now and there are many other examples of this.
No need to wait for a bank and it doesn't matter the blockchain, as long as it supports USDC and you have a crypto wallet, the payment goes through.
Stripe knows this already and crypto payments will be here for a very very long time as they already are today.
Not saying it's a vibe-coding issue. But I just imagine a scenario where a global service experiences significant disruption due to a vibe-coded release. No person understands how it works or is able to figure out in less than a week because no human has ever glanced at the code for a couple years, so the decision is taken to unleash LLM agents directly on production to fix the issue. Of course, one of these agents has to do some database migration but there is a breaking change, so they launch a sub-agent to deal with that; the sub-agent doesn't have a full context, so it decides that the easiest way would be to drop the database and so it does. The latest _successful_ backup took place a month ago.
I just learned the embarassing way that my ability to pay for groceries depends on the livelyness of europe-west2.
The uptime of cash in my wallet is pretty close to 100%. It's extremely rare that I have to use it, but it's incredibly convenient to have each time it's required
If you look at uptime as discrete set of events when you need to pay for something, my cash uptime is not looking great nowadays. "Sorry I can't break that" or machines accepting coins which you don't have at hand. Just to be clear I despise CC companies the system is broken in many ways.
Good opportunity to share some competitive resilience: https://monzo.com/blog/tolerating-full-cloud-outages-with-mo...
Its a bigger thing https://status.cloud.google.com
Thanks, your comment was the first one which linked the two.
Revolut is the biggest private company in all of Europe.
Perhaps it’s me but I still find it kinda wild that a single power outage in London can shut down Google DC and it can lead to Revolut shutting down for some time disrupting much of the economy which depended upon it
Perhaps this could’ve been prevented, which makes me wonder how much of code written at Revolut is ai generated and its ai policy?
If their infrastructure is tightly coupled to a cloud provider in a single region then that's what they need to be work on and not necessarily their AI policy.
Can we still pay ? I have some shooping to do during my lunch break and I don't want to feel stupid without a way to pay at the checkout.
My revolut cards (both google pay and actual physical cards) were failing to process payments and had to use my backup card from a traditional bank instead
I could not pay via Revolut card on Apple Pay this morning. However, the same physical card worked.
Article mentions app down, which presumably it's not the same part used by MasterCard
From what I've seen—personally and from a variety of online sources—there's intermittent availability of basically everything, which means you might be able to access the app, or you might be able to pay by card, but that's going to change potentially from minute to minute, with an average of somewhere around 10% uptime. (Which, of course, means that you, personally, might just be in the 90% of downtime all the time until it's resolved.)
Take with appropriate seasoning, given its anecdotal nature.
Once again, blockchains that use USDC continue to run without any serious outages for years. I just paid for an item with USDC (using Phantom Wallet) right now and there are many other examples of this.
No need to wait for a bank and it doesn't matter the blockchain, as long as it supports USDC and you have a crypto wallet, the payment goes through.
Stripe knows this already and crypto payments will be here for a very very long time as they already are today.
What on earth are you talking about my guy
Not saying it's a vibe-coding issue. But I just imagine a scenario where a global service experiences significant disruption due to a vibe-coded release. No person understands how it works or is able to figure out in less than a week because no human has ever glanced at the code for a couple years, so the decision is taken to unleash LLM agents directly on production to fix the issue. Of course, one of these agents has to do some database migration but there is a breaking change, so they launch a sub-agent to deal with that; the sub-agent doesn't have a full context, so it decides that the easiest way would be to drop the database and so it does. The latest _successful_ backup took place a month ago.
$100B value down the drain.
Intermittent network failures in europe-west2 region != vibecoding
[citation needed]