Issue affecting the Gateway API on the Braintree platform(paypal-status.com) |
Issue affecting the Gateway API on the Braintree platform(paypal-status.com) |
Massachusetts Bay Transportation Authority
RED LINE
Ashmont/Braintree
4 current alerts
https://dashboard.transitmatters.org/system/slowzones/?chart...
Glad to see this comment to explain it.
BrainTree has been down for more than 7 hours now
This email confirms that you have canceled your payment agreement with ###### No further payments will be made from your PayPal account to this merchant. If you have any further questions about the agreement, or wish to reinstate it, please contact ###### directly.The biggest incidents have the best post mortems.
Is this really "down"?
Anyone who correctly implements ms wouldn't make it depend on other ms or get it shipped to prod anyway.
Edit: /s
https://techcrunch.com/2023/09/11/square-daylong-outage-dns-...
The vagueness is the point, because they want to avoid admitting serious problems.
We had this problem with some devops hires who came from a big company. They’d delay updating the status page as long as possible, then update with the weakest language that was technically correct. “Some customers might experience degraded performance” was their go-to message for nearly complete outages. They’d argue that it was technically correct because some requests were getting through in some logs somewhere.
It was a side effect of working in an environment where their bonuses depended on downtime and the severity of outages. The game was to admit as little as possible to keep those bonus numbers high. We didn’t calculate bonuses that way but they had ingrained the behavior from years of BigCo performance reviews.
Amazon.
All you have to do is look at their status page of green lights when us-east goes down completely to lose complete faith in their status page reflecting anything but wishful thinking.
You still want to notify customers they may be seeing issues even if you aren't confident on the percentage of impacted customers yet.
or
on the Ethereum blockchain, where, yes, the service is not technically down but unavailable to anyone who isn't paying a hundred bucks for a simple transaction.
It's a half-truth which is technically the same or worse than a lie.
Then people just moved to a client/server model hanging off github.
But you're right, local servers are more reliable than big cloud ones.
"Shitting in the woods is never broken."
yes '"Fraudulent Transaction Detected"'
while true; do echo 'HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Server: anti-fraud gateway
"Fraudulent Transaction Detected"'|nc -l 8123;doneAlmost as if uptime isn't the only thing that matters.
I still believe in digital currency as the future.
Remind me when a digital currency actually exists, because I haven't seen one yet. The problem isn't just that the ecosystem is filled with scammers, its that the tech doesn't solve any existing problem but creates new ones instead. Web3 is a joke.
It's much easier to sort out the smaller set of incentives the average Joe has and align them.
In the real world, it doesn't work like that.
There are some instances where that kind of thing is necessary, but...insane amount of clear downsides so your problem statement for doing it had better be pretty compelling.
The premise being high service availability and low latency to serve requests (no need to talk to source of truth) with the tradeoffs of higher storage / processing costs and from my experience higher complexity.
there's an original point, and then your attempt and being clever which is so far off the mark that it clearly was meant in jest...had it be left alone. but you then attempted take it further like you are serious. which is just sad really.