i'd like to resolve whatever is causing this, a few questions if you don't mind: do you have any UA spoofing plugins enabled? IPv4 or IPv6 endpoint? VPN? HTTP/3 (QUIC)? (you'll need to check the session log in the browser console for this).
those are the only things that I can think of that may be causing this issue... as i said in my other comment, i've had to take a defensive position from bots hammering kbin.run, so i'm leaning towards something i did that's interfering with legit traffic.
kbin.run admin here, in addition to the other good suggestions (up-to-date browser, date/time check), also check to see if you have any UA spoofing/mangling plugins enabled. i've had to crack down on the number of bots hitting the site that refuse to identify themselves, so it might be related.
i can sort of understand at&t being at&t as they continue to piss hundreds of millions away on subpar investments while continuing to bitch about being poor and needing government handouts to make the boo-boos hurt less, but what does google have to gain from this? and i could have swore that at some point it was mentioned starlink is/was going to use google data centers as PoPs for their ground stations, but maybe i'm miss remembering...
though i'll be honest, the several months of dialing-in the initial dosage were an absolute hell, but once it starts working... like hot damn, a whole new person. i can't function without it, but everyone reacts differently to SSRIs... so YMMV and it's definitely something to consult a physician about if you're serious.
i fixed a problem with the the oauth cert permissions on kbin.run that was preventing user logins, fwiw. i tested out the latest AppImage of Interstellar and it seems to auth just fine now!
I agree, I'm not into outright censorship based on my own personal opinions or beliefs. Our users have the ability to block instances/domains if they wish. Really the only reason I would defederate from other instances is if there were highly illegal activities taking place (as dictated by US law) or if an actor is being technically disruptive (spam and other malicious payloads).
Now that said, I will monitor this closely because Threads is going to be a beast in size by comparison to us and other small instances... it could very well end up heavily taxing my server/bandwidth/storage requirements. I may be forced to defederate and/or limit Threads AP activity if I find that it's overloading my infrastructure/$$$ on storage fees, but I guess we'll have to wait and see.