00:13:42 | <nicolas17> | Flashfire42: is there a low TTL? :x |
00:22:43 | | qwertyasdfuiopghjkl quits [Ping timeout: 255 seconds] |
00:25:40 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
01:25:28 | <monika> | IA frontend seems to be responding to requests now but is returning 503s (maintenance page) |
01:25:38 | <monika> | catalogd and item servers are offline though |
01:25:53 | <monika> | everything still being routed thru cloudflare magic transit |
01:42:04 | <nicolas17> | monika: still connection-timeout here |
02:54:49 | | qwertyasdfuiopghjkl quits [Ping timeout: 255 seconds] |
02:57:02 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
04:23:04 | | legoktm quits [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.] |
04:23:42 | | legoktm joins |
04:43:53 | | fartsmella joins |
05:08:28 | | fartsmella quits [Ping timeout: 255 seconds] |
05:24:06 | | sonick (sonick) joins |
06:11:57 | | thalia quits [Quit: Connection closed for inactivity] |
06:21:04 | | KoalaBear84 quits [Read error: Connection reset by peer] |
06:25:30 | | KoalaBear joins |
07:31:01 | <nyuuzyou> | They updated "Temporarily Offline" page. Added bluesky and mastodon accounts |
08:59:36 | | sralracer joins |
09:01:08 | | sralracer is now authenticated as sralracer |
09:15:13 | | nulldata quits [Quit: So long and thanks for all the fish!] |
09:15:18 | | kdy (kdy) joins |
09:16:40 | | nulldata (nulldata) joins |
09:20:45 | | Sidpatchy7 joins |
09:22:25 | | Sidpatchy quits [Ping timeout: 260 seconds] |
09:22:25 | | Sidpatchy7 is now known as Sidpatchy |
09:54:32 | <monika> | i've created an unofficial status page to keep track of the outage https://ia-status.warc.zip/status/main |
09:54:45 | <monika> | feel free to suggest endpoints to track |
09:55:21 | <@arkiver> | that is nice, thanks you monika :) |
09:55:48 | <@arkiver> | thank* |
09:56:59 | <@arkiver> | monika: how often does it check? |
09:58:41 | <monika> | every minute |
09:58:47 | <monika> | is that too often? |
09:59:10 | <@arkiver> | no, i don't think so |
09:59:34 | <@arkiver> | monika: what kind of requests is it? |
09:59:44 | | driib quits [Quit: The Lounge - https://thelounge.chat] |
10:00:05 | | driib (driib) joins |
10:00:19 | <monika> | plain old https requests with a 15 second timeout |
10:00:38 | <monika> | I also have some ICMP monitors pointed at the routers |
10:00:38 | <@arkiver> | monika: can you make sure there's a descriptive user agent? |
10:00:54 | <@arkiver> | just in case people start noticing the minutely pings |
10:01:05 | <@arkiver> | everyone is a bit on edge at the moment |
10:01:12 | <monika> | oh that's going to be a pain for the 100s of monitors |
10:01:16 | <monika> | understood |
10:01:37 | <@arkiver> | monika: well for the HTTP requests at least a user agent may be good |
10:01:43 | <@arkiver> | but if not possible, then can leave that out for now |
10:05:04 | <monika> | user agent will be "ia-status.warc.zip uptime-kuma (+monika@flyingpackets.net)" |
10:59:30 | | nicolas17 quits [Ping timeout: 258 seconds] |
11:03:07 | | nicolas17 joins |
11:03:42 | | sonick quits [Quit: Connection closed for inactivity] |
11:31:09 | <@arkiver> | mikolaj|m: thank you :) |
11:31:18 | <@arkiver> | oops |
11:31:22 | <@arkiver> | monika: thank you :) |
11:31:36 | <@arkiver> | (did "mo<TAB>" and someone not monika popped up...) |
11:36:54 | <katia> | methinks you made mi<TAB> instead |
13:08:45 | | magmaus3 quits [Ping timeout: 260 seconds] |
13:26:52 | | magmaus3 (magmaus3) joins |
13:33:57 | <@JAA> | monika: warc.zip, nice :-) |
13:34:23 | <@JAA> | Requires JS :-( |
13:58:33 | <TheTechRobo> | does it? I get 301 with a proper Location header |
13:59:59 | <@JAA> | TheTechRobo: On the status monitor, I mean. |
14:00:06 | <TheTechRobo> | Ah |
14:21:40 | | magmaus3 quits [Ping timeout: 260 seconds] |
14:23:29 | | magmaus3 (magmaus3) joins |
14:23:46 | | qwertyasdfuiopghjkl quits [Ping timeout: 255 seconds] |
14:30:37 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
14:44:43 | | andrew0 (andrew) joins |
14:46:45 | | andrew quits [Ping timeout: 260 seconds] |
14:46:45 | | andrew0 is now known as andrew |
14:46:56 | | magmaus3 quits [Read error: Connection reset by peer] |
14:47:06 | | magmaus3 (magmaus3) joins |
15:00:16 | | MrMcNuggets (MrMcNuggets) joins |
15:45:04 | <f_> | Any updates? |
16:38:35 | | Xanthon quits [Remote host closed the connection] |
16:53:41 | | Xanthon (Xanthon) joins |
17:07:32 | <nyuuzyou> | not yet |
17:56:55 | | nicolas17 quits [Ping timeout: 260 seconds] |
17:57:43 | | MrMcNuggets quits [Client Quit] |
18:00:53 | | nicolas17 joins |
18:04:38 | <@JAA> | https://mailchi.mp/814e217f37ee/empowering-libraries-17003607 |
18:04:50 | <@JAA> | > Estimated Timeline: days, not weeks. |
18:39:19 | <steering> | <3 for whoever at IA added bluesky and mastodon to the outage page LOL |
18:42:46 | <@JAA> | Still not seeing the outage page here, just timeouts on both archive.org and web.archive.org. |
18:43:57 | <steering> | instant response from archive.org, timeout on web.archive.org |
19:32:06 | | wmyttmlimvty joins |
19:34:13 | <wmyttmlimvty> | Since there has been a data breach of 31 million user accounts and passwords from the archive, do you know if there are there any steps being taken to secure user accounts after the archive comes back online? Like asking the users to verify via email or change their password before logging in? |
19:37:41 | <@JAA> | They haven't said anything yet about what steps they're taking. |
19:37:59 | <wmyttmlimvty> | Mkay ty |
19:40:16 | <@JAA> | Well, Jason did hint at 'change your password' emails, but that was in the very early stages and might as well be considered unofficial. |
20:04:09 | | BornOn420 (BornOn420) joins |
20:37:10 | <nicolas17> | I just tried "curl -v https://archive.org" and got an unknown CA error :| that was just once, trying again I get connection timeout |
20:42:27 | <nicolas17> | managed to catch it again with -vk |
20:43:01 | <nicolas17> | https://paste.kiska.pw/RaftersRoving |
20:47:07 | <@JAA> | Yeah, I get that on every attempt from OVH Canada. |
20:47:43 | <@JAA> | Possibly, ca-certificates on this machine is a bit outdated, but the relevant GoDaddy cert is ancient, so not sure. |
20:47:49 | | DogsRNice joins |
20:47:54 | <@JAA> | This should be the issuer cert: https://crt.sh/?id=548407 |
20:49:15 | <@JAA> | Oh, are they maybe not sending the intermediate cert? |
20:49:25 | <@JAA> | I only have the root CA on my system. |
20:52:14 | <@JAA> | Browsers would be fine with that because they do some black magic prefetching on common intermediates. |
21:28:08 | <IDK> | Turns out their mastodoon instance 208.70.31.113 (or persumably any IA IP under the 208 range) doesnt use magic transit yet |
22:25:04 | | sralracer quits [Client Quit] |
23:16:35 | | tech234a quits [Ping timeout: 615 seconds] |
23:18:36 | | tech234a (tech234a) joins |