00:00:09PredatorIWD2 joins
00:26:47Naruyoko quits [Quit: Leaving]
00:26:51etnguyen03 quits [Client Quit]
00:31:04angenieux (angenieux) joins
00:46:14lorwp quits [Remote host closed the connection]
00:50:14sralracer quits [Quit: Ooops, wrong browser tab.]
01:06:59Sluggs quits [Excess Flood]
01:12:33etnguyen03 (etnguyen03) joins
01:13:19Sluggs joins
01:47:20lorwp (lorwp) joins
01:57:53Froxcey quits [Remote host closed the connection]
02:07:16etnguyen03 quits [Client Quit]
02:07:23Froxcey (Froxcey) joins
02:12:17Froxcey quits [Ping timeout: 260 seconds]
02:14:48nicolas17 joins
02:14:53<nicolas17>JAA: http://status.digitalocean.com/incidents/jm44h02t22ck
02:15:44<nicolas17>they had to get Verisign (as the administrator of .com) involved to get the clientHold cleared in a timely manner o.O
02:17:22<@imer>darn, the juciest part is still missing
02:17:22<@imer>> DigitalOcean is working with Network Solutions to understand what happened on their end that resulted in the clientHold being applied to our domain incorrectly.
02:17:38<nicolas17>ikr
02:17:49<nicolas17>imer: back in July: https://x.com/henet/status/1808953880404787288
02:17:51<eggdrop>nitter: https://nitter.lucabased.xyz/henet/status/1808953880404787288
02:18:22<@imer>yeah, wouldn't be a bad guess if this one was similar
02:18:53<nicolas17>idk if the HE one had a proper postmortem either
02:20:18Froxcey (Froxcey) joins
02:21:27<@JAA>80 minutes to figure out the whois was updated, then another 70 minutes to confirm that it was the clientHold causing issues? Seems kind of long.
02:21:57Naruyoko joins
02:24:25etnguyen03 (etnguyen03) joins
02:24:50<@JAA>I think the HE case was about a phishing thing because Network Solutions didn't understand the purpose of bgp.he.net, or something along those lines?
02:25:22<nicolas17>ah yes I remember now
02:42:09etnguyen03 quits [Client Quit]
02:49:59etnguyen03 (etnguyen03) joins
02:53:42Aoede quits [Quit: ZNC - https://znc.in]
02:54:04Aoede (Aoede) joins
03:11:06etnguyen03 quits [Remote host closed the connection]
03:13:15Froxcey quits [Remote host closed the connection]
03:13:21Froxcey (Froxcey) joins
04:13:13Naruyoko quits [Client Quit]
04:24:05Naruyoko joins
04:41:02benjins3 quits [Ping timeout: 260 seconds]
04:43:45pixel leaves [Error from remote client]
04:53:52masterX244 quits [Ping timeout: 260 seconds]
05:01:24<monoxane>it seems like Network Solutions should be avoided
05:14:04Froxcey quits [Remote host closed the connection]
05:14:58Froxcey (Froxcey) joins
05:19:32Froxcey quits [Ping timeout: 260 seconds]
05:44:21Froxcey (Froxcey) joins
06:38:12pixel (pixel) joins
07:02:29BlueMaxima quits [Read error: Connection reset by peer]
08:13:48Froxcey quits [Remote host closed the connection]
08:13:54Froxcey (Froxcey) joins
09:13:27Gadelhas5628 quits [Read error: Connection reset by peer]
09:13:51Gadelhas56287 joins
09:27:27Froxcey quits [Remote host closed the connection]
09:28:22Froxcey (Froxcey) joins
09:37:22Froxcey quits [Ping timeout: 260 seconds]
09:39:47Froxcey (Froxcey) joins
10:01:33Froxcey quits [Remote host closed the connection]
10:56:07sralracer (sralracer) joins
10:57:59Froxcey_ joins
11:00:33Froxcey (Froxcey) joins
11:00:45Froxcey_ quits [Read error: Connection reset by peer]
11:05:27Froxcey quits [Ping timeout: 260 seconds]
11:09:54<immibis>malicious compliance: identify all network solutions domains, and report every "phishing" page following network solutions's criteria
11:10:28Froxcey (Froxcey) joins
11:21:25benjins3 joins
11:40:11<joepie91>lmfao network solutions again
11:40:30<joepie91>why is it that every time some big internet thing breaks, it's them
11:55:27Froxcey quits [Remote host closed the connection]
11:55:52<qwertyasdfuiopghjkl2>Might need to rebrand to Network Problems at some point
12:00:03Bleo182600722719623 quits [Quit: The Lounge - https://thelounge.chat]
12:02:24Froxcey (Froxcey) joins
12:02:48Bleo182600722719623 joins
12:37:53Froxcey quits [Remote host closed the connection]
12:55:29Froxcey (Froxcey) joins
12:59:02Froxcey quits [Remote host closed the connection]
12:59:09Froxcey (Froxcey) joins
13:10:17G4te_Keep3r3492415 quits [Quit: The Lounge - https://thelounge.chat]
13:10:44G4te_Keep3r3492415 joins
13:49:36Froxcey quits [Remote host closed the connection]
13:53:15Froxcey (Froxcey) joins
13:55:12th3z0l4 quits [Ping timeout: 260 seconds]
13:59:32Froxcey quits [Read error: Connection reset by peer]
14:31:03<@imer>you see - theres no solutions without problems to solve
14:31:25<f_>well :p
15:06:00<nulldata>https://walzr.com/IMG_0001/
15:26:56<kiska>lol https://server8.kiska.pw/uploads/26048516e0305a26/image.png
15:28:52colla__ joins
15:39:28riteo quits [Remote host closed the connection]
15:40:30riteo (riteo) joins
15:51:26Froxcey (Froxcey) joins
15:58:17Froxcey quits [Ping timeout: 260 seconds]
16:07:16<steering>>01:30 - Reached out to Verisign executives to assistance
16:07:30<steering>lol
16:13:31ducky quits [Read error: Connection reset by peer]
16:14:11ducky (ducky) joins
16:26:00eroc1990 quits [Quit: The Lounge - https://thelounge.chat]
17:07:49Froxcey (Froxcey) joins
17:12:29Froxcey quits [Ping timeout: 265 seconds]
17:15:17xarph_ quits [Ping timeout: 260 seconds]
17:15:19xarph joins
17:27:41eroc1990 (eroc1990) joins
18:15:03Froxcey (Froxcey) joins
18:16:44PredatorIWD2 quits [Read error: Connection reset by peer]
18:19:40Froxcey quits [Ping timeout: 265 seconds]
18:20:06PredatorIWD2 joins
19:02:25PredatorIWD2 quits [Read error: Connection reset by peer]
19:05:15PredatorIWD2 joins
22:15:07Czechball quits [Ping timeout: 260 seconds]
22:17:01etnguyen03 (etnguyen03) joins
22:18:26i_have_n0_idea quits [Ping timeout: 265 seconds]
22:33:15Czechball joins
22:39:25<nicolas17>https://support.apple.com/en-us/101555 does this work from DigitalOcean? I'm curious if they banned my IP or all of the DO network
22:39:49<nicolas17>(just curl it, I tried it from home and it works, doesn't care about UA)
23:01:10i_have_n0_idea (i_have_n0_idea) joins
23:28:53Sluggs quits [Excess Flood]
23:30:03Sluggs joins
23:30:14etnguyen03 quits [Client Quit]
23:35:30etnguyen03 (etnguyen03) joins
23:42:46Froxcey (Froxcey) joins
23:50:20etnguyen03 quits [Client Quit]