What’s Up With the Decrease in Tink CASC Score?

Most of the Tink endpoints show a sharp rise in overall latency, beginning on about 27 November. We then get a further sharp rise from about 6 December, which won’t get be flagged up in Insights.

tink apis 1

We can see this very clearly on the API.expert heatmap, where we the initial rise on Monday, 28 November and then a further rise on Tuesday, 6 December.

tink apis 2

The cause seems to be mostly SSL Handshake Time. This was pretty stable at around just above 150 ms until it suddenly shot up by about 120 ms from 27 November to 1 December when it stabilized before jumping again to about 320 m from 5 December to 6 December.

Tink’s Processing Time also went up by about 30 ms from 6 to 7 December.

tink apis 4

If we look at the raw data for the Tink endpoints, we can see that it an huge increase in the number of outliers from 28 November that is causing the SSL Handshake Time to increase.

For Processing Time, it’s not really possible to see the trend with either the raw data or the hourly data even though it’s clearly seen in the daily data because of the noise in the signal.
tink apis 6

The decrease in CASC score seen in the week beginning 28 November can be ascribed to a step change in the SSL Handshake Time of about 120 ms.

Sign Up to Our Newsletter

Want to be updated on latest API Metrics Insights? Sign up to our newsletter and receive latest news and blog from us.

Add an API

Related Posts

Join Us Now!

Join the 100s of companies relying on APImetrics.
Share