Hi Micah! Is the georgetown bridge is flaky as it seems? We have alerts set up for the default bridges and it seems like yours alerts a lot and the others alert rarely. It always comes back after a little while, so this isn't a "hey your bridge is down" mail so much as a "what's up with your bridge" mail.

I wonder if it is an issue with the network it's running on; or if it's an issue with the bridge itself, e.g. maybe there is something in Tor's logs that could help diagnose; or if it's something wonky about our alerts.

(I am cc'ing anti-censorship-team so others can coordinate and stay in sync; note that this is a public list with archives.)

Thanks! --Roger

----- Forwarded message from Monit anti-censorship-monitor@nymity.ch -----

Date: Thu, 19 Jan 2023 12:26:36 GMT From: Monit anti-censorship-monitor@nymity.ch To: anti-censorship-alerts@lists.torproject.org Subject: [anti-censorship-alerts] monit alert -- Connection failed default-bridge-georgetown X-Mailer: Monit 5.26.0

Connection failed Service default-bridge-georgetown

Date: Thu, 19 Jan 2023 13:26:35 Action: alert Host: server01 Description: failed protocol test [DEFAULT] at [209.148.46.65]:443 [TCP/IP] -- Connection timed out _______________________________________________ anti-censorship-alerts mailing list anti-censorship-alerts@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/anti-censorship-alerts

----- End forwarded message -----