April 2025 - anti-censorship-alerts

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

07 Apr '25

Total firing alerts: 1 ## Firing Alerts ----- Time: 2025-04-07 13:19: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 -----

2 1

[FIRING:1] number of bridges is not changing in rdsys
by alertmanager＠prometheus2.torproject.org 07 Apr '25

07 Apr '25

Total firing alerts: 1 ## Firing Alerts ----- Time: 2025-04-07 00:50: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 -----

2 1

[FIRING:1] too few new telegram bridges
by alertmanager＠prometheus2.torproject.org 07 Apr '25

07 Apr '25

Total firing alerts: 1 ## Firing Alerts ----- Time: 2025-04-07 00:34:44.934 +0000 UTC Summary: Too few bridges to distribute on the new pool, there might be a problem with the dynamic bridges. Description: There are only 4 bridges on the telegram new pool. playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… title: too few telegram bridges on the new pool -----

1 0

[FIRING:1] HTTPSResponseDelayExceeded -- blackbox
by alertmanager＠prometheus2.torproject.org 06 Apr '25

06 Apr '25

Total firing alerts: 1 ## Firing Alerts ----- Time: 2025-04-06 17:42:40.651 +0000 UTC Summary: Website https://snowflake.torproject.org is too slow. Description: Website https://snowflake.torproject.org has been too slow to respond in the last hour, not achieving our availbility target (95%) in response times (1s), instead having a 1.747s response time. playbook: TODO -----

1 0

[FIRING:1] too few new telegram bridges
by alertmanager＠prometheus2.torproject.org 05 Apr '25

05 Apr '25

Total firing alerts: 1 ## Firing Alerts ----- Time: 2025-04-05 15:32:44.934 +0000 UTC Summary: Too few bridges to distribute on the new pool, there might be a problem with the dynamic bridges. Description: There are only 2 bridges on the telegram new pool. playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… title: too few telegram bridges on the new pool -----

1 0

[FIRING:1] ignoring bridges by functionality -- metrics-standard
by alertmanager＠prometheus2.torproject.org 03 Apr '25

03 Apr '25

Total firing alerts: 1 ## Firing Alerts ----- Time: 2025-04-03 19:21:14.934 +0000 UTC Summary: rdsys is ignoring the restuls from bridgestrap, as less than half of the bridges are functional. This happens sometimes when rdsys is being restarted but if persist there is a problem on bridgestrap. Description: The fraction of functional bridges is too low for rdsys playbook: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… title: rdsys is ignoring the functionality of bridges -----

1 0