Incidents antérieurs

HTTP OK: Status line output matched "200" - 11808 bytes in 0.039 second response time

HTTP OK: Status line output matched "200" - 314312 bytes in 0.046 second response time

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

HTTP OK: Status line output matched "200" - 32695 bytes in 0.308 second response time

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 502 Bad Gateway

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 502 Bad Gateway

HTTP OK: Status line output matched "200" - 314209 bytes in 2.389 second response time

HTTP OK: Status line output matched "200" - 11808 bytes in 5.159 second response time

HTTP OK: Status line output matched "200" - 27249 bytes in 9.511 second response time

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

HTTP CRITICAL - No data received from host

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

connect to address 192.99.175.40 and port 443: Connection refused HTTP CRITICAL - Unable to open TCP socket

HTTP OK: Status line output matched "200" - 11808 bytes in 0.902 second response time

CRITICAL - Socket timeout after 10 seconds

HTTP OK: Status line output matched "200" - 11808 bytes in 3.333 second response time

HTTP OK: Status line output matched "200" - 314270 bytes in 6.194 second response time

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

HTTP OK: Status line output matched "200" - 27239 bytes in 0.110 second response time

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

HTTP OK: Status line output matched "200" - 314450 bytes in 2.407 second response time

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

HTTP CRITICAL - No data received from host

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 502 Bad Gateway

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 502 Bad Gateway

HTTP OK: Status line output matched "200" - 28854 bytes in 2.810 second response time

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

HTTP OK: Status line output matched "200" - 11808 bytes in 2.976 second response time

HTTP OK: Status line output matched "200" - 262794 bytes in 4.135 second response time

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

HTTP OK: Status line output matched "200" - 27245 bytes in 0.381 second response time

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 502 Bad Gateway

HTTP OK: Status line output matched "200" - 28854 bytes in 1.128 second response time

CRITICAL - Socket timeout after 10 seconds

HTTP OK: Status line output matched "200" - 15268 bytes in 0.254 second response time

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 500 Service unavailable (with message)

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 500 Service unavailable (with message)

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 500 Service unavailable (with message)

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 500 Service unavailable (with message)

HTTP OK: Status line output matched "200" - 15267 bytes in 0.030 second response time

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 500 Service unavailable (with message)

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 500 Service unavailable (with message)

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 500 Service unavailable (with message)

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 500 Service unavailable (with message)

HTTP OK: Status line output matched "200" - 15268 bytes in 0.121 second response time

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 503 Service unavailable

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 503 Service unavailable

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 503 Service unavailable

HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 503 Service unavailable

HTTP OK: Status line output matched "200" - 27247 bytes in 7.387 second response time

CRITICAL - Socket timeout after 10 seconds