You elided if you want to understand what is going on more deeply, which is a rather important part.
I say that precisely because I know that in reality most people aren't that interested. Which feel like I'm insulting people or something, but it's just the reality, we don't all have time to dig into absolutely everything all the time, and if you're not interested that's fine. But if you are, this is the best pathway to understanding this at a deeper level than the playground level.
That’s for full EU members part of the economic union. There is a whole process for that which takes a few years. Britain had a good deal which they threw away (use their own currency but they’re a part of the broader economic union).
There’s already visa free travel from Canada to the EU and trade deals in progress. It’s unclear what specific benefits the associate member deal provides.
One thing I would like to see is how many of those hours are during normal business hours in my country.
Not all hours are created equal when it comes to downtime and my intuition is that most of these 12 landed within my working hours.
In terms of impact that then might mean they were down for 7.5% of the time I needed them, or had business hours uptime of 92.5% which is… both not very good and very disruptive.
On the other hand, downtime at 4AM would be much less impactful even if it happened every day and added up to more overall downtime.
> they were down for 7.5% of the time I needed them, or had business hours uptime of 92.5%
You can obviously compute this for a particular customer, but being a global service, it's pretty much guaranteed that someone somewhere experienced the worse of those numbers
You can compute them for the average. In other words, the total customer impact is the number of business-hours of downtime across all customers divided by the total number of business hours of all customers.
This is important because it's quite possible that the downtime is biased toward the times they have the most active users.
Big systems worth their salt already do this as weighted uptime, considering request successes / total requests rather than wall clock uptime as internal SLOs. But these numbers aren't really ever published because it gives away information about your customer base.
"Failed customer interactions" - if you have a way to actually see requests before they hit your datacenter, e.g. some async third party client libraries.
On this topic, as a service operator, it's really nice when you also own your SDKs, and have client-side telemetry about failed requests. Gives you a much clearer picture of end-to-end reliability (at least for the subset of customers who opt-in to telemetry)
One of the effects of the strike was that white sliced was in short supply and mangled people ended up with weird granary loaves etc as they were all that was left in the shelves. They liked them.
And from that day granary and seeded breads became a lot more popular over the bland spongy white sliced stuff.
I will say that whatever the failings of white sliced, I still prefer it to over-sweetened US bread.
reply