4 ms·
I’ve tried it probably a year ago for a couple of weeks. It was very unreliable and slow for me. Change in uptime status were not picked up very fast and someti
by preya2k 4y ago
I’ve tried it probably a year ago for a couple of weeks. It was very unreliable and slow for me. Change in uptime status were not picked up very fast and sometimes not at all. Should I give it another try?
- anandchowdhary 4y agoIn that case, I would say no. Not much has changed in the past few weeks, and GitHub Actions has become increasingly less reliable (i.e., wait times are higher than when we launched Upptime a year ago). We're exploring a new CLI approach [1] which has the benefit of still running on GitHub Actions scheduled workflows and all bells and whistles like Slack notifications and opening issues, but it can be fully self-hosted with just a CLI command, and will always run in the background. Plus, it'll support GitLab and really any git repository and more status website features. When that's ready, perhaps that would be a better fit. [1] https://github.com/upptime/cli https://github.com/upptime/cli