Data analysis shows that 1 uptime tests were conducted for run3.run throughout the 1 182 day period starting on August 28, 2021. Returning a 200 code on the last instance of August 28, 2021, run3.run was accessible 1 times among all the tests done. Based on checks carried out as of November 22, 2024, run3.run did not experience any instances of unavailability. The responses received confirm that, as of November 22, 2024, no error status was detected. On August 28, 2021, in contrast to the average of 0.221 seconds, for run3.run recorded a response time of 0.221 seconds.