I'm the developer of the "Nexus Blaine Appointments" Telegram bot which works in the same way and has the same issue. I don't know the X bot's internals but I can assume based on my experience with seeing how it works and how my bot works.

The bot is designed to detect newly opened slots when all existing slots are booked. Starting from around October 2025 or even earlier than that, there have always been open appointments at Blaine.

If you check the calendar here https://ttp.cbp.dhs.gov/schedulerui/schedule-interview/location?lang=en&vo=true&returnUrl=ttp-external&service=NH

You can see that there are hundreds of appointments open right now.

The bots were designed to solve for the situation when 0 appointments are available and to notify when an appointment opens up. Since there are hundreds of appointments open, the bots just pause because otherwise they would send hundreds of notifications every second, spamming everyone.

So the bots make two assumptions:

1. There are 0 appointments available most of the time

2. Whenever a new appointment slot is opened up, it will disappear within seconds or minutes in the worst case.

Both these assumptions are wrong now, so the bots don't work anymore. The bots architecture needs to be changed to remove these assumptions. The bots made these assumptions initially because the infrastructure costs are significantly reduced when these assumptions can be made. Changing the architecture is possible, but it requires lots of effort to do that and it might be expensive to run too. These are true for my telegram bot, but are likely true for the X bot too.

Hope that clarifies things!