0 functioning checks were performed for james.cridland.net during the 0 day time frame beginning January 27, 2025. It was noted in every test performed as of January 27, 2025, that james.cridland.net was either inaccessible or experiencing issues. As of January 27, 2025, checks of james.cridland.net revealed no instances of inaccessibility. Every response as of January 27, 2025, shows that no error status code has been received. On January 27, 2025, the reported response time for james.cridland.net was 0 seconds, compared to an average of 0.000 seconds.