There were 1 uptime checks conducted for rubikrecords.com in the 2 060 days after June 17, 2019. In the 1 out of all conducted checks, including the most recent one on June 17, 2019, which returned a code 200, rubikrecords.com has been reachable. There were no recorded downtime incidents for rubikrecords.com during the inspections conducted as of February 6, 2025. According to the reports, all of the responses that were received as of February 6, 2025, are free of errors. Rubikrecords.com's average response time of 3.570 seconds was different from its June 17, 2019, reply time of 3.570 seconds.