Thursday, April 19, 2018

Missing cron executions

Hi there,

We received reports that multiple cronjobs executions were missed without any trace this morning.

It appears that one of our database servers stopped responding some time after our recent reconfiguration, while our health check script failed to detect and kept sending database queries to it. That's why some cronjobs didn't execute.

The problem was fixed and a new reliable health check script was added to prevent it from happening again. Your cronjobs should be working fine from now on.

I'm really sorry for the recent problems.

As a token of our apology, I have added a credit of 5% of your account plan price to your account balance.

If you encounter any problem with SetCronJob, please let us know ASAP.

Best regards,
Nguyen An Thuan.

Friday, April 13, 2018

8 new servers are added

Hello there,

SetCronJob just added 8 new servers and will be using them for processing your cronjobs. Please add their IP addresses to your whitelist as soon as possible.

Here are the new IPv4 addresses:
173.230.130.112
50.116.43.46
192.155.88.39
69.164.214.46
45.33.90.124
72.14.187.212
198.58.119.103
173.255.203.62

And here are new IPv6 addresses
2600:3c02::f03c:91ff:fe30:20bf
2600:3c02::f03c:91ff:fe30:208c
2600:3c03::f03c:91ff:fe30:204a
2600:3c03::f03c:91ff:fe30:20d4
2600:3c03::f03c:91ff:fe30:20ab
2600:3c00::f03c:91ff:fe30:97db
2600:3c00::f03c:91ff:fe30:979e
2600:3c00::f03c:91ff:fe30:97a2

You can view our full list of IP addresses at our Help Center.



If you want to receive email notification every time we add new servers, please subscribe here.

If you need any help, please feel free to create a ticket at the Help Center.

Thursday, April 12, 2018

Service outage on Apr 12, 2018

Hello there,

We had received multiple reports regarding the service outage from 5 AM this morning (UTC time). Unfortunately, we didn't react in time, and it caused our service down until 11 AM.

We checked and fixed our cron dispatching servers, and the service has been working fine since then. We replaced, upgraded and added more dispatching servers with the updated software to make sure this won't happen again. We also had our microservices monitored closely so we can react faster.

We already rerun your missing cron executions to make sure your important tasks are performed at least once today.

We are sorry for the inconvenience that caused.

As a token of our apology, we have added a credit of 10% of your account plan price (e.g. $5 for Platinum accounts) to your account balance.

If you encounter any problem with SetCronJob, please let us know ASAP.

Best regards,
Nguyen An Thuan.