oops-as.no

There were 2 uptime checks of oops-as.no conducted throughout the 1 146 day period beginning on October 1, 2021. From the entirety of checks conducted, oops-as.no was operable 2 times, with the most recent occurrence on October 1, 2021, resulting in a code 200 status. No downtime incidents were reported for oops-as.no during inspections conducted as of November 20, 2024. No reply with an erroneous status had been received as of November 20, 2024, according to the records. Recorded on October 1, 2021, was a 0.270 seconds response time for oops-as.no, averaging 0.299 seconds.