Alert subscription on Public Status Page

Akshay Joshi September 25, 2024

How do we restrict someone from running a script and adding spam emails to get subscribed to for alerts and compromising the maximum allowed subscriptions, knowing that there is a limit to total number of subscriptions in a plan (Hobby: 250 allowed subscriptions, Startup: 1000 allowed subscriptions) ?

1 answer

1 accepted

0 votes
Answer accepted
Egor
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 27, 2024

Hey Akshay, 
Thanks for reaching out to Atlassian Community!

Statuspage already has several measures in place to prevent spam subscriptions. First, it uses a double opt-in process, which requires users to confirm their email via a confirmation link before they are added to the subscription list. This ensures that only legitimate email addresses can subscribe.

Additionally, there are rate-limiting mechanisms in place to prevent excessive requests from a single IP, which helps mitigate the impact of automated bots or spam scripts. Finally, CAPTCHA can be enabled on subscription forms, adding an extra layer of protection against bots and malicious scripts.

These measures help minimize the risk of spam without affecting the experience for legitimate users.

In case you're still having issues, please feel free to raise a ticket with us, and we'll check it for you. 

Best Regards,
Egor

Akshay Joshi September 27, 2024

Thank you Egor for your response

Akshay Joshi October 1, 2024

I have a follow up question regarding this @Egor. It's probably not a very specific case, just a generic question. Let's for an example if we have just over a 1000 users in the system, which are valid users. Since it's a public page, I understand that, there can't be any restriction on any user asking to be subscribed to alerts. But there is a chance that we may use up all of the limit for the allowed subscribed users, if each of the system users subscribes to the alerts and completes the 2FA. And this is a possible case, since if we publish the public status page, there is no restriction on anyone going and subscribing to alerts, as all we need is a valid email address. How from an admin standpoint, can we control the subscribed users if we don't want the maximum allowed limit to be crossed ?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events