As said earlier, if you have a lot of websites (200+) we can discuss some longer intervals for your account but otherwise this is unlikely to happen as it doesn't work with updown.io credit pricing and doesn't fit well the current UI. The 1h check interval is already cheap enough for most use-cases (and provides better monitoring).
The reason is that we use updown.io to test our website forms. And with 24 test submissions per day it clutters our database. And the admin screens show the test submissions mostly.
I see, thanks for providing the reason. Unfortunately that's more of a side-track usage so not a priority to optimise for. And filling production database with automated test is indeed not great anyway (be it every 1 or 12 hours) so you'd better find a way to remove those automatically or hide them on your end.
The maintenance window feature if implemented could help you with this (as you could say only one or two hour per day should be active monitoring for example). So you may want to vote for this one too.
That would not really fit with updown.io UI and pricing. As you can use the 1h check which is already plenty cheap. If you do intend to use it for hundreds of websites, we might discuss 2h intervals. I'll merge this suggestion into https://updown.io/features/more-check-periods-2h-and-4h
Are there any plans for additional intervals within the range currently offered? For example, 3 min & 15 min? I'd especially like to see the 15 min option. Thanks!
I will be monitoring 500+ websites, so a 1-hour interval would consume too many credits. A 6-hour check interval would be much more suitable for my use case.
Would you be able to enable a 6-hour interval for my account?
I understand the limitation. However, my monitoring scale is expected to grow to around 2,000+ websites, so a 2-hour interval would still consume a large amount of credits.
Would you please consider offering a 4-hour check interval as a compromise? This would be much more suitable for large-scale monitoring while still maintaining reasonable monitoring frequency.
I would really appreciate it if you could reconsider this option.
You make it sound like it would be expensive but 500 websites at 2h interval (what you currently have) is about 2€ / month, 2000 websites would be ~8€ / month (if you buy credits in bulk of course). Is that what you consider expensive for 2,000 websites?
Is saving a 2-4€ / month — on a service already way cheaper that any other — worth spending your time and my time negociating despite my position being already clear? If so you can ask me again when you have 2,000+ sites and I may give you the 3h interval...
17 Comments
Intervals above 1h may be available on demand depending on how many sites you are monitoring. Please ask support if you want.
I would like to have the choice of a 2h ,4h, 8h ,12h or 1 day interval. I would be glad, if you could add more options.
We would like a 12 hour interval too.
As said earlier, if you have a lot of websites (200+) we can discuss some longer intervals for your account but otherwise this is unlikely to happen as it doesn't work with updown.io credit pricing and doesn't fit well the current UI. The 1h check interval is already cheap enough for most use-cases (and provides better monitoring).
Thank you for the explanation.
We are not looking to save the credits.
The reason is that we use updown.io to test our website forms. And with 24 test submissions per day it clutters our database. And the admin screens show the test submissions mostly.
I see, thanks for providing the reason. Unfortunately that's more of a side-track usage so not a priority to optimise for. And filling production database with automated test is indeed not great anyway (be it every 1 or 12 hours) so you'd better find a way to remove those automatically or hide them on your end.
The maintenance window feature if implemented could help you with this (as you could say only one or two hour per day should be active monitoring for example). So you may want to vote for this one too.
A daily check of a domain for the use case of monitoring low importance domains to confirm SSL cert status would be handy.
That would not really fit with updown.io UI and pricing. As you can use the 1h check which is already plenty cheap. If you do intend to use it for hundreds of websites, we might discuss 2h intervals. I'll merge this suggestion into https://updown.io/features/more-check-periods-2h-and-4h
Makes sense Adrien, I never considered that. I'll put my vote into a 2h interval then.
Are there any plans for additional intervals within the range currently offered? For example, 3 min & 15 min? I'd especially like to see the 15 min option. Thanks!
Those can be added to you account easily, I just added 3 and 15 min to your account.
Could you please add the 15 min interval to our account as well?
Yes, done :)
I will be monitoring 500+ websites, so a 1-hour interval would consume too many credits. A 6-hour check interval would be much more suitable for my use case.
Would you be able to enable a 6-hour interval for my account?
Thanks!
For 500+ websites I can offer you 2h check interval (I just updated your account) but not more.
I understand the limitation. However, my monitoring scale is expected to grow to around 2,000+ websites, so a 2-hour interval would still consume a large amount of credits.
Would you please consider offering a 4-hour check interval as a compromise? This would be much more suitable for large-scale monitoring while still maintaining reasonable monitoring frequency.
I would really appreciate it if you could reconsider this option.
You make it sound like it would be expensive but 500 websites at 2h interval (what you currently have) is about 2€ / month, 2000 websites would be ~8€ / month (if you buy credits in bulk of course). Is that what you consider expensive for 2,000 websites?
Is saving a 2-4€ / month — on a service already way cheaper that any other — worth spending your time and my time negociating despite my position being already clear? If so you can ask me again when you have 2,000+ sites and I may give you the 3h interval...
Sign in to comment