# Measuring meaningful availability / uptime of Wise

DevFeed: [Measuring meaningful availability / uptime of Wise](<https://devfeed.tech/articles/measuring-meaningful-availability-uptime-of-wise-15457.md>)

Original publisher: [Read original article](<https://medium.com/wise-engineering/meaningful-availability-uptime-of-wise-b1439ddc6270?source=rss----f2565bbe9c46---4>)

Author: Dániel Élő

Published: 2024-08-30T08:24:13Z

Content type: article

Language: en

Sources: [Wise Engineering - Medium](<https://devfeed.tech/sources/wise-engineering-medium.md>)

Topics: [Availability](<https://devfeed.tech/topics/availability.md>), [systems](<https://devfeed.tech/topics/systems.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [availability](<https://devfeed.tech/tags/availability.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [http](<https://devfeed.tech/tags/http.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [platform](<https://devfeed.tech/tags/platform.md>), [systems](<https://devfeed.tech/tags/systems.md>), [uptime](<https://devfeed.tech/tags/uptime.md>)

## AI overview

Wise explains how it is developing a meaningful way to measure and report product availability and uptime based on user-experienced business flows, while acknowledging that a single aggregate figure is an approximation.

## Source excerpt

At Wise we're building the best way to move and manage the world's money -- making it faster, cheaper, convenient and transparent. Product uptime and availability is contributing to three parts of our mission: An honest and meaningful uptime report is key to drive transparency of our systems. High availability is one of the greatest factors in making our product convenient. It is very hard to be convenient if the product is not working as designed. High availability means less retries and less waiting, driving us closer to instant too. In this post we will talk about the reporting aspect of uptime and availability, focusing on transparency. We would like to share our journey and various technical considerations towards measuring meaningful availability/uptime for Wise. Wise has a wide range of product offerings, condensing the availability or uptime of our business flows is not trivial. These flows consist of multiple business operations with various branches depending on user intent or group. Providing a single number as business flow availability or uptime is always going to be an approximation, but we can and should be transparent about how we aggregate and what that represents. Our goal is to have a meaningful measurement we can get behind as representative of user-experienced uptime/availability. Definitions First things first, let's define some terms we'll use: Business flow: A high level, complex use-case of the Wise product, e.g. "send money" (we aim to measure the availability of this, as this is the most meaningful for the end-users) Business operation: an individual operation a user can perform as part of one use case or business flow. A high level piece of functionality e.g. get a quote, set up a transfer, pay in for the transfer API endpoint: a technical term. Which HTTP(S) API to invoke in order to perform a Business operation. Not a service or a series of calls, a single HTTP(S) endpoint to perform a (part or whole) of Business operation. Availability: