
Anyone from Discord monitor here? Please contact me. Thanks, -Drew

Hey Drew, To clarify, are you referring to NANOG Discord folks, or Discord Inc? Kind regards, Ryan Hamel ________________________________ From: NANOG <nanog-bounces+ryan=rkhtech.org@nanog.org> on behalf of Drew Weaver <drew.weaver@thenap.com> Sent: Wednesday, February 12, 2025 5:31:04 AM To: nanog@nanog.org <nanog@nanog.org> Subject: Discord folks? Caution: This is an external email and may be malicious. Please take care when clicking links or opening attachments. Anyone from Discord monitor here? Please contact me. Thanks, -Drew

Sorry, I am trying to find someone at the company Discord as nobody on our entire ASN can connect to the web version of their product anymore. Thanks, -Drew From: Ryan Hamel <ryan@rkhtech.org> Sent: Wednesday, February 12, 2025 3:32 PM To: Drew Weaver <drew.weaver@thenap.com>; nanog@nanog.org Subject: Re: Discord folks? Hey Drew, To clarify, are you referring to NANOG Discord folks, or Discord Inc? Kind regards, Ryan Hamel ________________________________ From: NANOG <nanog-bounces+ryan=rkhtech.org@nanog.org<mailto:nanog-bounces+ryan=rkhtech.org@nanog.org>> on behalf of Drew Weaver <drew.weaver@thenap.com<mailto:drew.weaver@thenap.com>> Sent: Wednesday, February 12, 2025 5:31:04 AM To: nanog@nanog.org<mailto:nanog@nanog.org> <nanog@nanog.org<mailto:nanog@nanog.org>> Subject: Discord folks? Caution: This is an external email and may be malicious. Please take care when clicking links or opening attachments. Anyone from Discord monitor here? Please contact me. Thanks, -Drew

Just replying to myself. I figured out why nobody can get to it. If I go to https://discord.com it returns a 304 not modified [guessing a problem with their cloudflare that they are unaware of] but if I go to https://discord.com/login?redirect_to=%2Fchannels%2F%40me it works fine... so if anyone else notices this or gets complaints from users.. here you go. It seems to do the 304 issue on hosts all over the world not connected to our network as well. Thanks, -Drew From: NANOG <nanog-bounces+drew.weaver=thenap.com@nanog.org> On Behalf Of Drew Weaver Sent: Thursday, February 13, 2025 9:19 AM To: 'Ryan Hamel' <ryan@rkhtech.org>; 'nanog@nanog.org' <nanog@nanog.org> Subject: RE: Discord folks? Sorry, I am trying to find someone at the company Discord as nobody on our entire ASN can connect to the web version of their product anymore. Thanks, -Drew From: Ryan Hamel <ryan@rkhtech.org<mailto:ryan@rkhtech.org>> Sent: Wednesday, February 12, 2025 3:32 PM To: Drew Weaver <drew.weaver@thenap.com<mailto:drew.weaver@thenap.com>>; nanog@nanog.org<mailto:nanog@nanog.org> Subject: Re: Discord folks? Hey Drew, To clarify, are you referring to NANOG Discord folks, or Discord Inc? Kind regards, Ryan Hamel ________________________________ From: NANOG <nanog-bounces+ryan=rkhtech.org@nanog.org<mailto:nanog-bounces+ryan=rkhtech.org@nanog.org>> on behalf of Drew Weaver <drew.weaver@thenap.com<mailto:drew.weaver@thenap.com>> Sent: Wednesday, February 12, 2025 5:31:04 AM To: nanog@nanog.org<mailto:nanog@nanog.org> <nanog@nanog.org<mailto:nanog@nanog.org>> Subject: Discord folks? Caution: This is an external email and may be malicious. Please take care when clicking links or opening attachments. Anyone from Discord monitor here? Please contact me. Thanks, -Drew

On 2/13/25 12:17, Drew Weaver wrote:
Just replying to myself.
I figured out why nobody can get to it. If I go tohttps://discord.com it returns a 304 not modified [guessing a problem with their cloudflare that they are unaware of] but if I go tohttps://discord.com/login? redirect_to=%2Fchannels%2F%40me it works fine... so if anyone else notices this or gets complaints from users.. here you go. It seems to do the 304 issue on hosts all over the world not connected to our network as well.
I rewrapped this, plz throw a CRLF in there from time to time. I pinged someone who knows someone there. They should be reaching out. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

I pinged someone who knows someone there. They should be reaching out.
Just to throw this on the list for searchability -- I run infrastructure at Discord. I have our traffic team taking a look now and we're corroborating that 304s have increased, but aren't sure yet. Happy to have folks reach out (to my first name @ discord.com) if things like this come up, or I'm reachable on Discord @zorkian or (now!) in the NANOG server. -- Mark Smith mark@qq.is (mark@plogs.net)

Tried to visit new Nanog channels, went to login, it sent me an email verification, and can't connect to click.discord.com. Any ideas? ---------- Forwarded message --------- From: Mark Smith <mark@plogs.net> Date: Thu, Feb 13, 2025 at 4:29 PM Subject: Re: Discord folks? To: nanog@nanog.org <nanog@nanog.org>
I pinged someone who knows someone there. They should be reaching out.
Just to throw this on the list for searchability -- I run infrastructure at Discord. I have our traffic team taking a look now and we're corroborating that 304s have increased, but aren't sure yet. Happy to have folks reach out (to my first name @ discord.com) if things like this come up, or I'm reachable on Discord @zorkian or (now!) in the NANOG server. -- Mark Smith mark@qq.is (mark@plogs.net)

Worked for me just a second ago. Try this? https://discord.nanog.org/ On Sat, Feb 22, 2025 at 5:20 PM Mike Lieman <mikelieman@gmail.com> wrote:
Tried to visit new Nanog channels, went to login, it sent me an email verification, and can't connect to click.discord.com. Any ideas?
---------- Forwarded message --------- From: Mark Smith <mark@plogs.net> Date: Thu, Feb 13, 2025 at 4:29 PM Subject: Re: Discord folks? To: nanog@nanog.org <nanog@nanog.org>
I pinged someone who knows someone there. They should be reaching out.
Just to throw this on the list for searchability --
I run infrastructure at Discord. I have our traffic team taking a look now and we're corroborating that 304s have increased, but aren't sure yet.
Happy to have folks reach out (to my first name @ discord.com) if things like this come up, or I'm reachable on Discord @zorkian or (now!) in the NANOG server.
-- Mark Smith mark@qq.is (mark@plogs.net)
participants (6)
-
Bryan Fields
-
Drew Weaver
-
Josh Luthman
-
Mark Smith
-
Mike Lieman
-
Ryan Hamel