Hey Max,
Great start! Mind if I share a quick idea? I know your team has the talent to pull it off.
Why not build a dedicated status page (ideally, status.elfsight.com) similar to the examples below to do the same thing—plus more? That way, clients can bookmark it or even subscribe to monitor the status of Elfsight’s servers and widgets without getting unwanted comment notifications in their inbox (like this one!).
Cheers!
Hello Petar,
Thanks for the idea and the examples!
A dedicated status page would definitely have its advantages. For now, we’re keeping status updates within the Community, but it’s something we can revisit down the road.
Really appreciate you sharing your thoughts 
Hey @Max,
Just a thought…
Aren’t all other Elfsight widgets affected as well? If so, once my suggestion or similar is implemented, you won’t have to manage so many widget status topics at once.
In my opinion, your IT department or designees should be managing the server/widget status site or pages.
Cheers!
Good question! We started with these five components because they rely more heavily on external services, so some issues can arise outside our direct control. They’re also the areas where we’re more likely to see service-wide disruptions.
Most of our other widgets don’t typically experience issues on that scale, so we don’t see a need for separate status topics for each of them at the moment.
Of course, if a broader issue affects other widgets, we’ll share an update about that too 