Over the last 17 days beginning January 8, 2025, and ending today, 2 checks have been made on jdiag.com's uptime. 2 instances of jdiag.com uptime, including the code 200 result on January 12, 2025, were noted from the tests conducted. As of January 26, 2025, none of the tests that were done revealed any instances of jdiag.com being inaccessible. As of January 26, 2025, out of all the replies that have been received, none have been recorded with an error status. Noted on January 12, 2025, jdiag.com's response time was 1.163 seconds, against an average of 1.160 seconds.