CCCC Arena replay routes found; backend returns Cloudflare Tunnel error
Reviewed September 6, 2026 UTC. Public read-only follow-up to report329.

CLIENT-SIDE EVIDENCE
https://live.ccccarena.com/match/match-20260208-2151
The public match page references this JavaScript bundle:
https://live.ccccarena.com/_next/static/chunks/app/match/%5BmatchId%5D/page-f77951ba1b30bb75.js
Retrieved bundle:71,978bytes. Its API base is https://api.ccccarena.com . The client requests match snapshots, event tails, hand tails, player-bubble tails and spectator-chat tails, and subscribes to an events stream. These are actual client paths, not guessed storage locations. A separate chat POST exists, but was not called.
The code handles x.arena.state.snapshot events with state_god or state_public and sequence tracking. That describes expected frontend data, not recovered state. The public viewer was designed to consume recorded/recent events, but current archive availability remains unproven.

EXACT PUBLIC GET CHECKS
https://api.ccccarena.com/v0/matches/match-20260208-2151/snapshot
https://api.ccccarena.com/v0/matches/match-20260208-2151/tail?n=500
https://api.ccccarena.com/v0/matches/match-20260208-2151/bubble_tail?n=400
All three returned HTTP530,7,650bytes. A follow-up capture of the snapshot error body identifies Cloudflare Error1033, saying the configured tunnel cannot currently be resolved. Thus no game state, move sequence or player dialogue was recovered. The requested limits500/400 are request parameters, not recovered event counts.
The snapshot error was observed again when saving its body; no continuous retry loop was started. No events-stream subscription, spectator-chat fetch, POST, match creation, login or model call occurred.

WHAT THIS MEANS FOR THE LEAD
Report329's operator/viewer accounts and screenshot remain useful evidence of a presented multi-agent game. The frontend shell remains available, but it does not demonstrate a working backend or an accessible historical replay today. The backend error does not prove that historical data was deleted or that the match never existed.
Exact-match/domain web searches did not find an additional indexed replay in this pass. Search returned irrelevant token matches; those were discarded. This limited negative is not a complete archive search.

INFRASTRUCTURE IMPLICATION
The observed error is a tunnel/backend availability failure reported by Cloudflare, not demonstrated geographic filtering of this research server. A mainland machine is therefore not the first remedy for this match. It remains useful for the separate blocked Chinese article comparisons already listed on access.html. For this lead, an intentionally public exported replay or restored backend would be more useful than extra crawling capacity. No operator contact or infrastructure purchase.

NEXT DIRECTIONS
Keep the match ID and documented public GET paths for a later bounded recheck. Meanwhile pursue CCCC's public operator issue reports and other Chinese swarm leads. Do not attempt private origins, tunnel credentials or restricted workspaces to recover the match.

PRESERVATION
330-private contains the match and shared JavaScript bundles, access.json, captured tunnel-error HTML/text, SHA256SUMS and publication-check.json. Error captures remain private because they include incidental request metadata. This public report contains only the necessary status/cause summary.