#staff | Logs for 2025-10-03
« return
[00:06:13] <sylvester> 2025-10-03 02:06:13 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[00:11:15] <sylvester> 2025-10-03 02:11:15 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 118944 bytes in 1.612 second response time
[01:00:51] -!- devbot has quit [Remote host closed the connection]
[01:00:52] -!- devbot [devbot!devbot@Soylent/BotArmy] has joined #staff
[01:01:51] -!- Loggie [Loggie!Loggie@Soylent/BotArmy] has joined #staff
[02:32:56] <sylvester> 2025-10-03 04:32:56 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[02:37:57] <sylvester> 2025-10-03 04:37:57 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 119043 bytes in 1.474 second response time
[03:15:17] <sylvester> 2025-10-03 05:15:17 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[03:15:23] <sylvester> 2025-10-03 05:15:23 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[03:20:18] <sylvester> 2025-10-03 05:20:18 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 118989 bytes in 1.490 second response time
[03:20:25] <sylvester> 2025-10-03 05:20:25 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 119026 bytes in 1.385 second response time
[04:10:58] <sylvester> 2025-10-03 06:10:58 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[04:11:01] <sylvester> 2025-10-03 06:11:00 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[04:16:06] <sylvester> 2025-10-03 06:16:06 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 118999 bytes in 7.938 second response time
[04:16:07] <sylvester> 2025-10-03 06:16:07 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 119016 bytes in 6.595 second response time
[05:22:38] <sylvester> 2025-10-03 07:22:38 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[05:22:39] <sylvester> 2025-10-03 07:22:39 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[05:27:39] <sylvester> 2025-10-03 07:27:39 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 119639 bytes in 1.460 second response time
[05:27:41] <sylvester> 2025-10-03 07:27:41 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 119582 bytes in 1.649 second response time
[06:03:26] <sylvester> 2025-10-03 08:03:26 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[06:03:27] <sylvester> 2025-10-03 08:03:26 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[06:13:33] <sylvester> 2025-10-03 08:13:33 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 119587 bytes in 6.437 second response time
[06:13:34] <sylvester> 2025-10-03 08:13:34 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 119529 bytes in 7.228 second response time
[06:50:53] <sylvester> 2025-10-03 08:50:53 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[06:50:54] <sylvester> 2025-10-03 08:50:54 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[06:55:54] <sylvester> 2025-10-03 08:55:54 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 119570 bytes in 1.551 second response time
[06:55:56] <sylvester> 2025-10-03 08:55:56 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 119590 bytes in 1.474 second response time
[07:03:14] <sylvester> 2025-10-03 09:03:14 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[07:03:16] <sylvester> 2025-10-03 09:03:16 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[07:08:16] <sylvester> 2025-10-03 09:08:16 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 119551 bytes in 1.660 second response time
[07:08:17] <sylvester> 2025-10-03 09:08:17 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 119593 bytes in 1.496 second response time
[09:09:57] <sylvester> 2025-10-03 11:09:57 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[09:14:59] <sylvester> 2025-10-03 11:14:59 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 116638 bytes in 1.933 second response time
[09:19:16] <sylvester> 2025-10-03 11:19:16 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[09:29:20] <sylvester> 2025-10-03 11:29:20 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116666 bytes in 3.636 second response time
[10:04:53] <sylvester> 2025-10-03 12:04:53 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[10:05:03] <sylvester> 2025-10-03 12:05:03 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[10:09:55] <sylvester> 2025-10-03 12:09:54 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 116589 bytes in 1.548 second response time
[10:10:04] <sylvester> 2025-10-03 12:10:04 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116622 bytes in 1.447 second response time
[10:17:15] <sylvester> 2025-10-03 12:17:14 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[10:17:24] <sylvester> 2025-10-03 12:17:24 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[10:22:30] <sylvester> 2025-10-03 12:22:30 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116623 bytes in 5.913 second response time
[10:29:50] <sylvester> 2025-10-03 12:29:50 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[10:32:16] <sylvester> 2025-10-03 12:32:16 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 116672 bytes in 1.426 second response time
[10:34:52] <sylvester> 2025-10-03 12:34:52 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116676 bytes in 1.477 second response time
[11:08:48] <sylvester> 2025-10-03 13:08:48 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[11:11:25] <sylvester> 2025-10-03 13:11:25 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[11:13:50] <sylvester> 2025-10-03 13:13:49 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 116665 bytes in 1.449 second response time
[11:21:27] <sylvester> 2025-10-03 13:21:27 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116637 bytes in 1.632 second response time
[11:40:21] <sylvester> 2025-10-03 13:40:21 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[11:43:48] <sylvester> 2025-10-03 13:43:47 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[11:45:23] <sylvester> 2025-10-03 13:45:22 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 116620 bytes in 1.775 second response time
[11:47:23] -!- sylvester has quit [Read error: -0x7880: SSL - The peer notified us that the connection is going to be closed]
[11:47:31] -!- sylvester [sylvester!~sylvester@jltedsnzw.home3u.ch] has joined #staff
[11:53:54] <sylvester> 2025-10-03 13:53:54 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116577 bytes in 6.922 second response time
[12:11:55] <sylvester> 2025-10-03 14:11:54 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[12:16:56] <sylvester> 2025-10-03 14:16:56 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 116643 bytes in 1.422 second response time
[12:41:14] <sylvester> 2025-10-03 14:41:14 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[12:46:16] <sylvester> 2025-10-03 14:46:15 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116673 bytes in 1.598 second response time
[13:03:35] <sylvester> 2025-10-03 15:03:35 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[13:04:16] <sylvester> 2025-10-03 15:04:16 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[13:13:42] <sylvester> 2025-10-03 15:13:42 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116676 bytes in 7.302 second response time
[13:19:18] <sylvester> 2025-10-03 15:19:18 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 116598 bytes in 1.480 second response time
[15:04:17] <sylvester> 2025-10-03 17:04:17 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[15:04:18] <sylvester> 2025-10-03 17:04:18 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[15:09:19] <sylvester> 2025-10-03 17:09:19 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 121161 bytes in 1.673 second response time
[15:09:20] <sylvester> 2025-10-03 17:09:20 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 121253 bytes in 1.480 second response time
[15:35:47] <sylvester> 2025-10-03 17:35:47 04www.soylentnews CRITICAL HTTPS IPv400 HTTP CRITICAL: HTTP/1.1 503 Service Unavailable - 536 bytes in 0.973 second response time
[15:35:47] <sylvester> 2025-10-03 17:35:47 04www.soylentnews CRITICAL HTTPS IPv600 HTTP CRITICAL: HTTP/1.1 503 Service Unavailable - 536 bytes in 0.924 second response time
[15:40:51] <sylvester> 2025-10-03 17:40:50 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 121256 bytes in 3.343 second response time
[15:40:51] <sylvester> 2025-10-03 17:40:51 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 121282 bytes in 3.707 second response time
[15:58:10] <sylvester> 2025-10-03 17:58:10 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[15:58:12] <sylvester> 2025-10-03 17:58:11 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[16:03:14] <sylvester> 2025-10-03 18:03:14 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 121438 bytes in 3.139 second response time
[16:03:14] <sylvester> 2025-10-03 18:03:14 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 121381 bytes in 2.225 second response time
[17:03:00] <sylvester> 2025-10-03 19:03:00 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[17:03:07] <sylvester> 2025-10-03 19:03:07 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[17:13:01] <sylvester> 2025-10-03 19:13:01 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 121327 bytes in 1.560 second response time
[17:13:09] <sylvester> 2025-10-03 19:13:09 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 121283 bytes in 1.478 second response time
[18:04:33] <sylvester> 2025-10-03 20:04:33 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[18:04:42] <sylvester> 2025-10-03 20:04:42 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[18:19:34] <sylvester> 2025-10-03 20:19:34 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 121226 bytes in 1.502 second response time
[18:22:08] <sylvester> 2025-10-03 20:22:08 08mail.soylentnews WARNING PING IPv400 PING WARNING - Packet loss = 0%, RTA = 241.45 ms
[18:24:43] <sylvester> 2025-10-03 20:24:43 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 121266 bytes in 1.455 second response time
[18:27:12] <sylvester> 2025-10-03 20:27:12 03mail.soylentnews OK PING IPv400 PING OK - Packet loss = 0%, RTA = 161.84 ms
[19:05:27] <sylvester> 2025-10-03 21:05:27 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[19:10:29] <sylvester> 2025-10-03 21:10:29 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116624 bytes in 1.520 second response time
[21:01:08] <sylvester> 2025-10-03 23:01:08 04www.soylentnews CRITICAL HTTPS IPv600 HTTP CRITICAL: HTTP/1.1 503 Service Unavailable - 534 bytes in 0.915 second response time
[21:02:54] <sylvester> 2025-10-03 23:02:53 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[21:06:10] <sylvester> 2025-10-03 23:06:10 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116734 bytes in 1.504 second response time
[21:07:55] <sylvester> 2025-10-03 23:07:55 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 116744 bytes in 1.492 second response time
[21:09:55] -!- sylvester has quit [Read error: -0x7880: SSL - The peer notified us that the connection is going to be closed]
[21:10:03] -!- sylvester [sylvester!~sylvester@jltedsnzw.home3u.ch] has joined #staff
[21:17:39] <sylvester> 2025-10-03 23:17:39 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[21:22:46] <sylvester> 2025-10-03 23:22:46 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 116633 bytes in 7.447 second response time
[22:27:50] <sylvester> 2025-10-04 00:27:50 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[22:42:52] <sylvester> 2025-10-04 00:42:51 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 116665 bytes in 1.461 second response time
[23:04:23] <sylvester> 2025-10-04 01:04:23 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[23:14:25] <sylvester> 2025-10-04 01:14:25 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 116609 bytes in 1.453 second response time
[23:51:11] <sylvester> 2025-10-04 01:51:11 04www.soylentnews CRITICAL HTTPS IPv600 CRITICAL - Socket timeout after 10 seconds
[23:51:46] <sylvester> 2025-10-04 01:51:45 04www.soylentnews CRITICAL HTTPS IPv400 CRITICAL - Socket timeout after 10 seconds
[23:56:13] <sylvester> 2025-10-04 01:56:13 03www.soylentnews OK HTTPS IPv600 HTTP OK: HTTP/1.1 200 OK - 118916 bytes in 1.495 second response time
[23:56:47] <sylvester> 2025-10-04 01:56:47 03www.soylentnews OK HTTPS IPv400 HTTP OK: HTTP/1.1 200 OK - 118982 bytes in 1.575 second response time