← Back to EasyCron.com

Feb 1, 2013

Cron job server upgrade finished

During a few past days, our server have some stability problem when handling peak workload. In order to fix the problem, we decided to move to a new server which has much better hardware specifications.

Now we're proud to say that the migration from old server to the new one has been completed, and all figures of the site running on the new server come out are much better than they're on the old server. I believe most of our users will experience these changes too and be happy about this.

After migration, we're quite confident that:

  • All cron jobs will be run more quickly (thanks to the network connection upgrade of the server) and more reliably (we have a mass RAM now);
  • Page load will be much faster (hardware + network upgrade, and we use the world's fastest web server -- nginx);
  • We can offer users some plans of higher configuration (we're planning to store more cron job execution logs in the the future so that our users can have a clear view of longer time span on how their cron jobs had run).

If you have any other suggestions, you may drop us a line.

Thanks for the patience on waiting. Enjoy a vigorous easyCron!

Jan 26, 2013

Cron job number limit removed

After deep investigation, we found that abuse mainly came from API, so we decide to remove the number limit on cron job, and keep the limit on API request, but adjust the quota to:

Free: Max 100 daily API requests
Starter: Max 1000 daily API requests
Plus: Max 2000 daily API requests
Max: Max 5000 daily API requests

Hope that our users will enjoy the change, you can set up unlimited cron job again now!

Jan 25, 2013

User account can be safely cancelled from user panel.

From now on, users who don't need our cron job service anymore can safely cancel their accounts on user panel: http://www.easycron.com/user/edit.

After cancellation, your account information/data will be permanently cleared from our system, and the action is irreversible. So please do it with caution.

You're welcome to tell us why you're going away via our feedback form though.

Jan 9, 2013

Service plans updated

We recently updated our service plans for the purpose of optimizing our system performance, improving stability and fighting abuse.

Two main updates to our service plans are:

1. Adding cron job quota to each plan as following:

Free: Max 5 active cron jobs
Starter: Max 50 active cron jobs
Plus: Max 200 active cron jobs
Max: Max 500 active cron jobs

2. Adding API request daily quota to plans as following:

Free: Max 10 daily API requests
Starter: Max 200 daily API requests
Plus: Max 400 daily API requests
Max: Max 1000 daily API requests

You may see details of these updates at https://www.easycron.com/pricing.

Aug 13, 2012

Cron Job API Launched

Just now, EasyCron proudly launched Cron Job API to the public.

This API allows members of EasyCron easily integrate our services into their applications.

Currently it has following methods:
For more information, please check the API Document Page.
Enjoy it!

Jul 23, 2012

Good bye reCAPTCHA!

Since reCAPTCHA is becoming harder and harder to distinguish (actually sometimes it's ridiculously over blurred), so we take it down from the sign up page.

Now we have a cleaner and enough safe CAPTCHA at https://www.easycron.com/user/register.

Haven't use webcron yet? Try our free cron jobs service!

Jun 8, 2012

Cron job can be run manually

We just added a feature to EasyCron.com. This feature allows user to run cron job manually by clicking on the URL link in the cron job list .

Manually triggered cron job is run from EasyCron's server, so in your website's log, you will still see the IP/agent of EasyCron.com.

In the popped up page of manually-run cron job, you can see statistics information such as start time, connect Time, done time, total execution time, HTTP status code and the output of the cron job. These information will help you check if everything is good with your cron job.

In order to prevent abuse, every user only has a quota of 20 times to manually run the cron jobs in one day.