1.25K subscribers
4 photos
5 links
Antispam service for Telegram.

Think your ban is wrong ? Ask in
Download Telegram
Even though I post the ban list here, I strongly discourage importing it if you are a User of Rose. When using Rose, you can subscribe to a Federation and you will receive the Federation bans and unbans aswell. If you don't use Rose, I suggest diffing the list with the previous list to see if anyone was removed.

You can subscribe to the SpamWatch Federation using /subfed 1c2221d9-aa27-4baf-b77c-8822b36254d2

If you're not part of a Federation you can join the SpamWatch Federation using /joinfed 1c2221d9-aa27-4baf-b77c-8822b36254d2
SpamWatch Support Chat

There's now a Support chat in case you have trouble setting up Rose to join the Fed or subscribing to the Fed.
In this chat, you may also ask for a unban if you think you were banned wrongfully. Once the API is done, the chat will also serve as a place to get help with the API and the Bot.

Should a JSON based RSS Feed be provided next to a regular XML RSS Feed ?
Final Results
No (specify why in the Chat if you want)
SpamWatch API
The API is currently in a testing phase. If you want to help with testing send a message to @SitiSchu to get your API Token. A bot to generate a token will be done soon. Incase you need help using it join and someone will help you.

SpamWatch Feed
The Feed has been deprecated in favor of the API.

Telegram Feature Suggestion
Since Telegram doesn't seem to do anything about spam adding members I suggested a way they could fix it on Twitter. If you agree with my suggestion feel free to like the tweet in the hope that Telegram finally does something about it:
Bots with SpamWatch Support
If your Bot supports SpamWatch and isn't listed below just ask for it to be added in @SpamWatchSupport.

Bots with a Star(*) have Global Bans by the Bot Owners. Consult the corresponding Bots help to see if and how they can be disabled if needed.

Administration Bots
Federation Support
To join use /joinfed <Fed ID>
- matticate
Fed ID: spamwatch
- Rose
Fed ID: 1c2221d9-aa27-4baf-b77c-8822b36254d2
- Sophie
Fed ID: e47eb95f-a93a-4afb-8059-fe3fa3ab4042

General Support
Enabled by default
- Aigis
- JoinCaptcha
- SpamBlockers*
- ZiZi*

Enabled by default (Marie Forks)
- Haruka Aya*
- Hitsuki*
- Kigyō*
- Natalie*
- Saitama*

Enable with a command
/antispam on
- MetaButlerBot*
Misc Bots
- RSS Bot

Self-hosted Bots
- The Guard
SpamWatch API
To use the API, you can now get an API token here. This token is required to access the API and is used to rate-limit specific requests.

To add the API to your bot, you can use one of the official libraries for Python, NodeJS, Crystal and C# or implement it yourself using the documentation at

When adding the API to a userbot, please avoid mentioning the group admins for banned users since that gets annoying quick. Instead, don't do anything if you are not admin in the group.

In case you notice any issues with the API or have some questions join
The API and Token Bot should both work again after a small (unplanned) downtime.
Quick reminder that @SpamWatchSupport is the only support group for SpamWatch. Any other group claiming to be SpamWatch Support is fraudulent.
Should Admins of spam adding Chats be banned too or just the Group Owner?
Final Results
Yes they should be banned.
No. Just the owner.
Answer for bots.
Fake Rose Federation
Since there have been some fake SpamWatch Federations in Rose please run /chatfed in your group and double check these:
- FedID is 1c2221d9-aa27-4baf-b77c-8822b36254d2
- Owner is @SitiSchu (172811422)
- Number of admins is 1

If any of these don't match up run /leavefed and then /joinfed 1c2221d9-aa27-4baf-b77c-8822b36254d2 to join the real SpamWatch Federation.
Bot Downtime
@SpamWatchBot will be down for maintenance for ~30 minutes
Bot Downtime
@SpamWatchBot is back up again and running open source code now: SpamWatchBot
API Failing
Hetzner is currently having issues with their nodes and one of the affected Nodes happens to be the database server for the SpamWatch API.
Check Hetzner's Status Page for updates.
Issue should be resolved.
API Down
Hetzner is having issues again so the API is still unavailable.
Issue has been resolved.
Server Upgrade
The server running the API will be upgraded from Debian 9 to Debian 12 so in case any issues arise, this might be why.
API is back up again. It's running on a new server so both IPv4 and v6 changed.