Thursday, September 22, 2016

SetCronJob is now operated by Develover

On August 20, 2016, I registered my own company named Develover Company Limited, based in Vietnam. From now own, SetCronJob will be owned and operated by my company.

If you have any question, please feel free to email me.

Best regards,

Nguyen An Thuan.

Wednesday, August 24, 2016

SetCronJob is updated

Hello all,

I've just rewritten SetCronJob code base with a new framework. There are some minor changes, while most core features and settings are kept intact. If you encounter any problem, please try reload the page (hit Ctrl - F5), or contact me if that doesn't work.

New cronjob editing form

New cronjob editing form
I simplified and categorized all the fields into subsections demonstrating how SetCronJob works: Basic settings (cronjob URL and time settings), Connect to your server, Send HTTP request (HTTP method and post data), Detect failure and notify you, Name and group, and Advanced settings (just for me doing some special stuff with specified cronjobs).

One address (contact information) for one account

Since I don't see the actual needs with multiple addresses, I just simplified it. You can update your contact information at Account > Update info. The contact information will be included in the PDF invoice too.

URL parameter in API requests is deprecated

Now you should only send POST (recommended) or GET request directly to our API functions e.g. like this******
The URL parameters e.g.******
will not be supported. For backward compatibility, it will be redirected to GET requests.

Updated pricing and plans

Currently I've only increased the max execution logs for Platinum and Diamond plans. More good changes will be coming soon :-)

Help center is coming

I removed the FAQ (frequently asked questions) page, and added the Help Center at If you have any question, just ask me, and if it's a common problem, I'll add it to the Help Center.

Sunday, March 20, 2016

SetCronJob now supports RubyID

To prevent the continuing service abusing, SetCronJob now only offers a very limited trial account with 24 daily executions in 5 days. To fully tested our service, you can just connect your account to a RubyID account, and we'll upgrade your account to trial Gold account with 7,200 daily executions in 15 days for free.

This applies to new accounts and existing account that still in trial period only. All other existing account will be added $1 bonus to your account balance when connecting to a RubyID account. The bonus credit will be used when you upgrade/renew your account.

RubyID requires users to add and verify their phone number before they can connect to SetCronJob. You can create a RubyID account here.

 If you need any help, please feel free to email me.

Monday, March 14, 2016

HostGator blocked our IP addresses

UPDATED on Mar 27, 2016: Well, 4 out of 5 new servers have been blocked by HostGator again. That is it. SetCronJob now stops supporting HostGator users. If your website is hosted at HostGator, you should either move to other hosting providers, or use other online cronjob services. You can always request a refund of your payment at Billing > Payments.

UPDATED on Mar 26, 2016: We added 5 new servers and moved all blocked cronjobs there. They're all working fine now. Our 3 old IP addresses are also unblocked.

SetCronJob's IP addresses have been being blocked by HostGator's firewall for days. If your sites are hosted at HostGator, you can see this error message
Access denied.  Your IP address is blacklisted.  If you feel this is in error please contact your hosting provider's abuse department.
in cronjobs' execution results.

A client has confirmed that HostGator blocked us because we exceeded their PHP request rate limit. And they won't unblock until the requests stop.

So, currently we'll disable all cronjobs for sites hosted at HostGator. I'll update when they unblock our IP addresses.

To prevent this from happening again, please lower your cronjob's execution interval, especially when your websites are hosted at shared hosting providers. Most cronjobs don't require cronjob every minute to work. You can set it to run every 10 minutes instead, or contact me for advice.

You should also contact HostGator and ask them if they can whitelist our IP addresses:
We also consider adding more servers / IP addresses later to spread the load.

Tuesday, February 2, 2016

SetCronJob is high availability now!

After 3 servers are added, there were several issues that caused SetCronJob unstable. We were working really hard to fix, improve and upgrade our servers and application.

The service is stabilized after a few days, and we're still monitoring and working on it. Until now, we can proudly announce that SetCronJob is high availability. We removed all single point of failure, including:
- Web server: we're using round robin DNS, so if one web server is down, your browser will retry the request at another server. There will be some delay time (e.g. 30 seconds, tested on my browser), but it's not a big problem. As long as you can access our website, and the cronjobs are executed properly, it's no big deal.
- Cronjob processor: all cronjobs are distributed to all servers to be processed. If one server is down, the other cronjob processor can still handle all the cronjobs properly. Actually just one server is powerful enough to handle all cronjobs. Network failure is automatically detected, so any server has any network problem, it'll be temporarily removed until everything is fine and it can process cronjob properly again.
- Database server: we have synchronous database replication, automatic failure detection and failover, load balancer. No more database down!

With this set up, SetCronJob is now the most reliable online cronjob service. We're processing 3.8 millions cronjobs a day, or 2,600 cronjobs per minute, or 44 cronjobs per second. And the service is already scaled up and out so that it can handle up to x3 times than those numbers :-)

Happy setting up cronjobs!