Thanks to a email from Tim about getting thousands of requests to his CRON page when using the service because of a invalid and page timeout error we needed to make some changes. Today from the beta panel you will get better info about what is going on with the CRON including the last 20 reports. The reports include HTTP status code, time take to run in seconds, and even a bit of the content returned (256 characters).
We also improved the CRON service in the backend, it should timeout but not cause the script to keep running. We also flag the CRON so it will not run again while still processing as we run many CRON agents at the same time.