We have restored debug_trace methods.
We appreciate your patience and understanding.

Our team continues working to restore "debug_trace" functionality on Cronos. The effort is active, but at this stage we’re not able to provide a firm ETA for recovery.

The Cronos team has been responsive. Unfortunately, they haven’t been able to offer meaningful assistance that would accelerate a fix.

We appreciate your patience and understanding.

The "debug_trace" methods remain non-functional due to an upstream issue on the Cronos Foundation side.

We remain in contact with the Cronos Foundation and tracking their progress.
We will provide an update as soon as we have more information we can share.

The "debug_trace" methods remain non-functional due to an upstream issue on the Cronos Foundation side. They have acknowledged ongoing internal testing and configuration changes that are impacting these endpoints.

We are tracking their progress closely and will provide further updates as soon as the Foundation deploys a fix.

We continue active work to validate and restore the "debug_trace#" functionality.

Coordination with the Cronos Foundation is ongoing as they investigate the upstream fault and potential recovery path.

We are currently experiencing a Service Degraded incident affecting Cronos (Mainnet).

Methods relying on "debugtrace#" (such as "debugtraceTransaction" and related endpoints) are currently returning errors.

Our engineering team is actively investigating the root cause and working on a fix.
We will provide an update as soon as more information becomes available.