- anti-censorship-alerts - lists.torproject.org

[FIRING:1] Snowflake drop of client polls
by alertmanager＠prometheus2.torproject.org 10 Feb '26

10 Feb '26

Total firing alerts: 1 ## Firing Alerts ----- Time: 2026-02-10 08:58:15.286 +0000 UTC Summary: There is a considerable drop on snowflake client polls Description: This might mean a problem in our signaling channels, or some other thing blocking clients to reach the broker playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/161 title: Snowflake drop of client polls -----

2 1

[FIRING:1] Snowflake drop of client polls
by alertmanager＠prometheus2.torproject.org 10 Feb '26

10 Feb '26

Total firing alerts: 1 ## Firing Alerts ----- Time: 2026-02-10 08:31:00.286 +0000 UTC Summary: There is a considerable drop on snowflake client polls Description: This might mean a problem in our signaling channels, or some other thing blocking clients to reach the broker playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/161 title: Snowflake drop of client polls -----

1 0

[FIRING:1] China Vantage Point Offline for 100 hours -- metrics-standard
by alertmanager＠prometheus2.torproject.org 09 Feb '26

09 Feb '26

Total firing alerts: 1 ## Firing Alerts ----- Time: 2026-02-06 19:06:37.258 +0000 UTC Summary: China Vantage Point Offline Description: China Vantage Point probetelemetry-01.torproject.org:443 was Offline for at least 100 hours playbook: TODO -----

2 1

[FIRING:1] builtin bridge unreachable -- blackbox_tcp
by alertmanager＠prometheus2.torproject.org 02 Feb '26

02 Feb '26

Total firing alerts: 1 ## Firing Alerts ----- Time: 2026-01-30 12:38:59.934 +0000 UTC Summary: The builtin bridge 51.222.13.177:80 is unreachable Description: Unable to connect to the builtin bridge TCP port 51.222.13.177:80 playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… -----

3 3

Re: [FIRING:1] builtin bridge unreachable --blackbox_tcp
by Katharina Farke-Rämer 02 Feb '26

02 Feb '26

Sorry, I had to install it again, because it didn't work. Am 02.02.2026, 11:05 Uhr schrieb meskio via anti-censorship-alerts<anti-censorship-alerts(a)lists.torproject.org>: Hello Luis-Philippe, Looks like your builtin bridge is down. I see the IP responds to ping, but looks like port 80 is not responding. I hope is nothing serious. Let me know if I can help. Thank you for this bridge that is very much used. Quoting alertmanager--- via anti-censorship-alerts (2026-01-30 13:39:30) > > Total firing alerts: 1 > > > ## Firing Alerts > > ----- > Time: 2026-01-30 12:38:59.934 +0000 UTC > Summary: The builtin bridge 51.222.13.177:80 is unreachable > Description: Unable to connect to the builtin bridge TCP port 51.222.13.177:80 > playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… > ----- > -- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan. _______________________________________________ anti-censorship-alerts mailing list -- anti-censorship-alerts(a)lists.torproject.org To unsubscribe send an email to anti-censorship-alerts-leave(a)lists.torproject.org

1 0

[FIRING:1] http service unreachable -- blackbox
by alertmanager＠prometheus2.torproject.org 02 Feb '26

02 Feb '26

Total firing alerts: 1 ## Firing Alerts ----- Time: 2026-01-31 14:26:14.934 +0000 UTC Summary: HTTP for https://bridges.torproject.org/status?id=5EDAC3B810E12B01F6FD8050D2FD3E277B… is unreachable Description: Unable to connect to HTTP port or response code is not the expected for https://bridges.torproject.org/status?id=5EDAC3B810E12B01F6FD8050D2FD3E277B… playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… -----

2 1

[FIRING:1] number of bridges is not changing in rdsys
by alertmanager＠prometheus2.torproject.org 11 Jan '26

11 Jan '26

Total firing alerts: 1 ## Firing Alerts ----- Time: 2026-01-11 04:21:14.934 +0000 UTC Summary: Last time this happen there was an issue on the communication between rdsys and bridgestrap rdsys#249 Description: For the last 3h we have the same number of bridges in rdsys, this usually fluctuates playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… title: number of bridges is not changing in rdsys -----

1 0

[FIRING:1] email silence
by alertmanager＠prometheus2.torproject.org 04 Jan '26

04 Jan '26

Total firing alerts: 1 ## Firing Alerts ----- Time: 2026-01-04 21:29:59.934 +0000 UTC Summary: There might be a problem with the email delivery. Description: No email has been sent from the email distributor for the last 12 hours playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… title: email distributor is silent -----

1 0

[FIRING:1] Snowflake drop of client polls
by alertmanager＠prometheus2.torproject.org 26 Dec '25

26 Dec '25

Total firing alerts: 1 ## Firing Alerts ----- Time: 2025-12-26 19:18:15.286 +0000 UTC Summary: There is a considerable drop on snowflake client polls Description: This might mean a problem in our signaling channels, or some other thing blocking clients to reach the broker playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/161 title: Snowflake drop of client polls -----

1 0

[FIRING:1] gettor silence
by alertmanager＠prometheus2.torproject.org 25 Dec '25

25 Dec '25

Total firing alerts: 1 ## Firing Alerts ----- Time: 2025-12-25 02:02:29.934 +0000 UTC Summary: There might be a problem with the email delivery. Description: No email has arrived to gettor for the last 12 hours playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… title: gettor is silent -----

1 0