Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The announced scope is recently created or modified Cron Trigger schedules. Existing schedules without recent changes are explicitly unaffected by this incident.
- The first announcement was October 13 at 15:18 UTC. The 15:19 UTC update changed the status to Identified and said a fix was being implemented; no recovery announcement appeared in the 19:35 UTC check.
- The announcement does not define the recent-change window or list affected regions, plans or accounts. It does not establish an outage of every Workers scheduled task.
- Match schedule-change times, expected executions and actual results, then follow the same incident. Recovery timing, missed-run replay and compensation remain unknown.
Which schedules match the announced scope?
A Cron Trigger is an arrangement for a Worker to perform a task on a schedule. Cloudflare's October 13 announcement says customers who recently created or modified a schedule may find that it does not execute as expected. That is the specific condition to compare with your records.
The same announcement explicitly excludes existing Cron Trigger schedules that have not recently changed. This does not prove that every older task has no unrelated problem. It does prevent a limited activation incident from becoming a claim that all Workers or all scheduled tasks are unavailable.
Cloudflare does not define recent as a particular number of minutes or days, or provide an account, region, plan or runtime-version list. The evidence supports investigating schedule changes; it does not establish that a particular country or account type must be affected.
Why does Identified still not establish recovery?
The first Investigating announcement was published on October 13, 2026 at 15:18 UTC. The 15:19 UTC Identified update says only that the issue was identified and a fix was being implemented. It does not announce a completed fix or provide a recovery time.
The complete official incident-page read finished on October 13 at 19:35 UTC and still showed those two updates. The contemporaneous official API had null monitoring_at and resolved_at fields. This describes that observation, rather than promising the status will never change afterward.
In the Asia/Shanghai time zone, that check occurred at 03:35 on October 14; the announcement date remains October 13 UTC. Keep announcement times, source-check times and your own missed-execution times separate so you can compare the same period.
Compare schedule changes with actual execution records
In an environment you are authorized to inspect, first record the relevant Worker, the actual schedule configuration and when it was last created or modified. Retain configuration and version records. Do not change a production schedule simply to validate this news report.
Then list expected execution times and check for corresponding start, completion or business-result records. A page opening successfully does not establish that a scheduled task ran. A single missing log entry also does not, by itself, prove that the task never ran.
Consider an unexecuted example: task A has an unchanged schedule, while task B lacks an expected result after a recent schedule change. B better matches the announced investigation condition. If A also fails, its own evidence still needs examination instead of automatic attribution to this incident.
How should missed executions be handled without a confirmed workaround?
The two official updates provide no verified workaround. Repeatedly saving a schedule, recreating a Trigger, changing regions or redeploying a Worker must not be presented as an officially confirmed fix, or a guarantee of immediate activation.
If the business depends on that execution, have the person responsible establish whether the task partly completed and whether repeating it could duplicate notifications, writes or other outcomes. This article has not manually triggered, changed or rerun any task.
Retain the missed-execution interval, actual results and necessary logs so subsequent recovery decisions can follow the application's own rules. The announcement does not promise automatic replay of missed tasks. Do not assume the platform will fill a gap before checking the results.
What evidence should you watch for next?
Follow the same cbvocc87nsne incident page and read official updates to establish a status change. Identified means that the issue has been identified. Even a later Monitoring status should be read with its explanation rather than treated as proof that every task you own has recovered.
If Cloudflare later announces recovery, still compare your next expected execution with its actual result. A platform incident ending and a particular business task completing are separate facts. Retain evidence for each.
Unknowns currently include the specific cause, recovery time, complete affected population, handling of missed executions and compensation. This article offers an investigation sequence based on the announced scope. It has not tested platform recovery or changed a reader's account or network environment.
Sources
Frequently Asked Questions
Does an HTTP 200 from the Worker prove that Cron is working?
No. A successful HTTP response establishes only that this request received a successful response. It does not establish that a separate schedule executed at the expected time and completed its business task. Check records for that schedule's actual execution and result. This article has not called a reader's endpoint.
Will changing the schedule back to its old expression restore it immediately?
The current official incident does not confirm that workaround. A modification is itself among the conditions the announcement says to examine, and reverting does not establish immediate activation. Preserve the actual configuration history and follow subsequent official guidance and the application's recovery rules.
Will missed tasks be replayed automatically or receive fee compensation?
Neither current announcement promises automatic replay or compensation, or lists applicable terms. The existence of an incident does not establish an automatic retry, refund or SLA payment. Actual task results and the terms that apply need separate confirmation.