2024 REPORT NOW AVAILABLE: Review the API quality of cloud service providers See the details >

Going Back In Time

We frequently check general performance data to look for ‘odd’ responses and we found an interesting one today which involved an API call on a test server which took -284,027ms, or just a little under 5 minutes.  We assume that the host had to have a clock reset in the middle of making the API call, but it was an interesting results and one which has led to a small change on our side to error out such platform induced time issues in the future.

Once again, this makes it clear to us that just ‘assuming’ that the cloud is there and working for you is a dangerous assumption that that many, many things can impact end user performance and monitoring and tracking is an essential part of the mix.

If you are not already using us, why not try us out?


Request A Demo

Find A Slot To See A Demo Or Speak To One Of Our Support Specialists

Ready To Start Monitoring?

Want to learn more? Check out our technical knowledge base, or our sector by sector data, or even our starters guide to the API economy. So sign up immediately, without a credit card and be running your first API call in minutes.

Related Posts

Join Us Now!

Join the 100s of companies relying on APIContext.