01:53:06Fusl quits [Quit: K-Lined]
01:53:16Fusl (Fusl) joins
01:54:05JAA (JAA) joins
01:54:05@ChanServ sets mode: +o JAA
03:44:06HP_Archivist (HP_Archivist) joins
04:07:15NatTheCat3 (NatTheCat) joins
04:09:07NatTheCat quits [Ping timeout: 268 seconds]
04:09:07NatTheCat3 is now known as NatTheCat
04:41:23DogsRNice_ quits [Read error: Connection reset by peer]
05:48:32unknownsrc quits [Quit: Ping timeout (120 seconds)]
05:48:57unknownsrc (unknownsrc) joins
11:07:27unknownsrc quits [Ping timeout: 248 seconds]
14:11:15<IDK>IA is really unstable recently
14:22:00unknownsrc (unknownsrc) joins
14:31:31dxrt quits [Quit: ZNC - http://znc.sourceforge.net]
14:31:57dxrt joins
14:44:35imer quits [Quit: Oh no]
14:47:53imer (imer) joins
14:48:22DogsRNice joins
15:06:55@JAA quits [Ping timeout: 248 seconds]
15:08:08JAA (JAA) joins
15:08:08@ChanServ sets mode: +o JAA
16:27:31grill_ (grill) joins
16:27:53grill quits [Ping timeout: 268 seconds]
16:50:21<IDK>Wayback machine has been returning 503 for the past 2 days
17:40:01<nicolas17>I wish there was some status page
17:41:19<nicolas17>I have low priority stuff to upload, waiting until there's low load and more stability would be better for IA and for me (my scripts suck at error handling)
17:43:55<that_lurker>you could ask the s3 api for the current load and wait for it to go down.
17:44:20<nicolas17>are these 503s correlated to *that* load or is it a different problem entirely?
17:44:55<that_lurker>503s on the wayback machine side should be different system entirely unless a larger issues is ongoing
17:48:39<that_lurker>the s3 seems to have been stable for a while. I have uptime kuma following it in #IA-monitor but that does not monitor the load
19:57:17Doranwen quits [Remote host closed the connection]
19:57:39Doranwen (Doranwen) joins
20:29:06grill_ is now known as grill
21:06:46katia quits [Remote host closed the connection]
21:11:54katia (katia) joins