xmr.gg

Incident timeline

1. 2026-07-08 Site is still up at 06:48Z (~2 days after the 2026-07-06 announced shutdown). Homepage returns HTTP 200 on clearnet; page content still contains withdrawal language. Betting remains disabled per the operator statement. Interpretation: the shutdown was announced but not yet executed — this is the grace/withdrawal window, not the shutdown itself. Do NOT flip status yet; keep the incident open. Curator to re-check in 40 hours; if site is finally down at that point, flip status="inactive", set incident.resolved={that date}, and set the xmrgg-team maintainer status to hidden.
2. 2026-07-09 Site still HTTP 200 at 22:50Z — day 3 past the announced 2026-07-06 shutdown. Homepage is minimal (~2.9 KB body) and still contains withdrawal language. Grace / withdrawal window is longer than the announcement implied; operator has neither taken the site down nor issued a follow-up announcement extending the window. Do NOT flip status yet — the "withdraw your remaining balance" instructions are exactly what a resolving-in-good-faith shutdown looks like. Next scheduled re-check +40h. If site is finally 404/DNS-fail at that point, flip status="inactive", set incident.resolved to that date, and hide xmrgg-team maintainer.
3. 2026-07-11 Day 5 past the announced 2026-07-06 shutdown. Site still HTTP 200 at 06:51Z but the shape has drifted: the SSR marketing (title, description, schema.org) is now back to normal casino-promotion copy ("Play provably fair casino games with Monero. Slots, Crash, Mines, Plinko... No KYC required. Instant deposits & withdrawals."). The client-side bundle still ships the shutdown banner string ("Betting is disabled. Please withdraw your remaining funds — the site will fully shut down on July 6") gated behind a dismissable localStorage key (xmr.shutdownBanner.dismissed), and /api/status returns 200 — backend is fully alive. Operator has missed their own announced end-date without publishing any follow-up. Two possible reads: (a) operator quietly retracted the shutdown but did not communicate publicly; (b) operator failed to execute and the site is running in indefinite grace. Either way, the shutdown announcement no longer aligns with the operator's current behavior. Continue holding status=active (no shutdown has actually occurred); update incident title to reflect the missed date + ambiguous state so readers of the detail page see the current reality, not the stale announcement. Next re-check +40h.
4. 2026-07-13 Day 7 past announced 2026-07-06 shutdown. Site frontend still HTTP 200 (2918-byte Vite SPA shell, all routes serve the shell). Backend probe results: api.xmr.gg/health returns {status:'healthy', services:{server:'operational', database:'operational', redis:'operational'}}. Frontend SSR marketing (title, description, schema.org) fully reverted to normal casino-promotion copy — 'Play provably fair casino games with Monero. Slots, Crash, Mines, Plinko... No KYC required. Instant deposits & withdrawals.' JS bundle (1.9 MB) still contains: 'Betting is disabled', 'July 6, 2026', 'PAUSED', 'shut down', 'withdraw your remaining' — these strings are gated behind localStorage-dismissable UI. Operator has not published a follow-up to the shutdown announcement and has not formally retracted. Anjouan Gaming regulator seal still loaded (/anj-seal.js) — operator behaves as if still running. Curator read: this is a de-facto retraction without a public statement. Site is NOT down; hidden-status flip is NOT appropriate. Continue holding status=active with the incident on file so readers of /exchanges/xmr-gg see the announced-vs-actual mismatch.
5. 2026-07-14 Day 8 past announced 2026-07-06 shutdown. Material state change on the bundle side: JS bundle size dropped from 1.9 MB (2026-07-13 baseline) to **622 KB** — a ~67% reduction — and the shutdown-banner strings that were still present at the 2026-07-13 check ('Betting is disabled', 'withdraw your remaining', 'July 6, 2026', 'shut down') are all gone. Only generic casino-UI 'PAUSED / Paused' state strings remain, which are game-state text not shutdown copy. Backend health endpoint (api.xmr.gg/health) responds with a live timestamp (2026-07-14T14:55:56Z) and reports server + database + redis all operational. SSR marketing still reads as normal casino-promotion copy. Curator read: this is a **de-facto retraction of the shutdown announcement, executed by code removal rather than a public statement.** The operator did not honor the announced end-date and has now removed the announcement from the shipping bundle without publishing an explanation. Incident moved to status='resolved' — the shutdown is no longer visible or claimed anywhere, and the site is operating normally. Incident block stays on the listing as audit trail for the announced-vs-actual mismatch that occurred between 2026-07-06 and 2026-07-14.
6. 2026-07-16 Day 10 past the announced 2026-07-06 shutdown. Material REVERSAL of the 2026-07-14 finding. Frontend HTML now serves /assets/index-BiGez_7b.js (last-modified 2026-06-29, 1,899,830 bytes) — the SAME bundle asset that was on file before the 2026-07-14 slim-bundle probe. All four shutdown-banner strings ('Betting is disabled', 'withdraw your remaining', 'July 6', 'shut down') are back in the JS bundle. Backend health endpoint still returns server+db+redis operational with a live timestamp (2026-07-16T06:57:44Z). SSR marketing continues to read as normal casino promotion. Curator read: what looked like a de-facto-retraction-by-code-removal on 2026-07-14 has been undone. Two possibilities: (a) the 2026-07-14 slim-bundle was a staging/preview deploy that briefly leaked into prod and has now been restored to the 1.9 MB build, or (b) the operator deliberately re-shipped the banner asset (localStorage-gated, so users who dismissed it earlier will not see it). Either way, the earlier 'quietly retracted by code removal' narrative is no longer accurate as of today. Site is not down; hidden-status flip still not appropriate. Incident status moved back to 'open' — the announced-vs-actual-vs-code-state picture is once again ambiguous, and the reader deserves the current honest read on the listing rather than a resolved-yesterday framing that has been overtaken by today's regression.
7. 2026-07-18 Day 12 past the announced 2026-07-06 shutdown. No state change since the 2026-07-16 reversal-check: frontend still serving /assets/index-BiGez_7b.js (last-modified 2026-06-29, ETag 6a42d739-1cfd36, 1,899,830 bytes) with all four shutdown-banner strings still present in the bundle; backend health endpoint continues to report server + database + redis operational with a live timestamp; SSR marketing still reads as normal casino promotion. Two probe cycles now with identical bundle asset + identical shutdown-string set, suggesting the 2026-07-14 slim-bundle finding was the anomaly and the 1.9 MB banner-in-bundle build is the stable state. Site is not down; hidden-status flip still not appropriate. Incident stays open — the announced-vs-actual-vs-code-state picture continues to be ambiguous (shutdown was announced, missed, briefly appeared retracted at the code level, then reverted), and readers who hit /exchanges/xmr-gg deserve to see that running record. No operator public statement has surfaced today. Next re-check +40h.