Is EasyCron Down Right Now? Check if there is a current outage ongoing.

All of our services were back to work. After the incident, some logs were lost forever (displaying "Executing (xxxx seconds)" or "Log lost"), though they were run normally on time.

Our logging servers are returned to working (from 2024-07-24 15:25 UTC). We will keep monitoring them.

An email received just now (2024-07-24 14:17 UTC) from OVH: =============================== Hello, The data centre team are working on to improve the cooling of this data centre following intense temperature around this sector of the world. We do not have any ETA for now, however stay assure we will finish the intervention as fast as possible. Please note, this ticket is fully managed by our system and not monitored by our technical support. If you need further support after the intervention done, we would recommend reaching out to us via ticket for further assistance. Thank you for your understanding. ===========================

One of the other 2 emails we received from OVH at 11:56 UTC was: =========================================== [TICKET#9951248] Operation Room cooling check start soon Dear Customer, Please note that our technical teams will intervene on your server xxx.ip-xxx-xxx-xxx.net in 15 minutes in order to carry out the following intervention: Room cooling check The OVHcloud Team Need help? Access all our support solutions in the Help centre: https://help.ovhcloud.com/ You will find our Guides, FAQ, Community forum and System status information. OVH LIMITED is a subsidiary of OVH Groupe SAS. Registration number and address: 537 407 926 - 2, rue Kellermann, 59100 Roubaix, France. [ref=1.8fd1cbc6] =========================================== After 25 minutes we received the emails, 2 servers stopped responding at the same time.

The one of the 2 emails we received from OVH 2 hours ago was: ================================= Dear Customer, An intervention has just been scheduled on xxxx.ip-xxx-xxx-xxx.net. This operation is expected to start on 2024-07-24 07:30:00 EDT (UTC -04:00). Here are the details of this operation: Room cooling check The OVHcloud Team Need help? Access all our support solutions in the Help centre: https://help.ovhcloud.com/ You will find our Guides, FAQ, Community forum and System status information. OVH LIMITED is a subsidiary of OVH Groupe SAS. Registration number and address: 537 407 926 - 2, rue Kellermann, 59100 Roubaix, France. [ref=1.8fd1cbc6] ================================= They didn't tell any expected affect to the servers. But actually 2 servers are down at the same time now that have affected parts of our services.

Part of our services (logs saving and viewing) were not available now. Anything related to logs handling cannot be carried out correctly. No any estimated finishing time said from OVH.

Update from OVH: https://bare-metal-servers.status-ovhcloud.com/incidents/dc2yh1024mv3 From our monitoring, starting from 2023-10-21 14:23:00 UTC, all executions are normal again.

Another ticket about the issue on OVH status page: https://status.us.ovhcloud.com/pages/incident/59dd23da8827c804746f1664/6533bd2309467405368c55ba

Our infrastructure provider is having a network perturbation that has caused network performance downgrade on EasyCron: https://bare-metal-servers.status-ovhcloud.com/incidents/dc2yh1024mv3 We will monitor the progress of the issue continuously. The problem has caused some executions of some cron jobs failing unexpectedly from Oct 21, 2023 - 08:15 UTC.

Our bare metal servers provider OVH was replacing their network equipments today during 16/06/2023 01:00 UTC to 16/06/2023 11:00 UTC: https://network.status-ovhcloud.com/incidents/9vzvvwrm69ps (some of our servers located at BHS2) At EasyCron, from 16/06/2023 09:30 UTC to from 16/06/2023 11:00 UTC, some of the cron jobs failed to run, or were delayed for a few minutes to run. After 16/06/2023 11:00 UTC (the network maintenance ended), our service restored to work 100%.

Cron job triggering processes were wrongly identified as “should be cancelled“ by monitoring component, and then were cancelled. We have removed that monitoring component. Same kind of errors should not happen again in the future.

Service is working during the monitoring of 15 minutes. We're working on a patch to fix the intermittent problem.

A fix has been applied, and the service is back online. We're working on a fix to permanently stabilize the service.

We are continuing to investigate this issue.

We are currently investigating this issue.

An incident observed during 11:10 UTC to 11:19 UTC today. We have intervened and the problem was cleared.

The triggering process is working good now, we will work on a fix to handle network issue when using distributed lock in the HA triggering module.

We're monitoring the system now.

multiple triggering processes locked (could be due to temporary network issue) cause freezing processing of cron job triggering. After cancelling frozen processes, and disabling HA triggering module, server is working again.

We're having problem triggering problem currently.

EasyCron experienced a downtime (from 2022-06-21 18:52:00 UTC to 2022-06-22 03:58:00 UTC) due to an issue on one of our servers. The issue prevented our database servers from restarting successfully. We restored an earlier backup of the database on a new physical server to recover the service.