FATHOM’s current official experience is FATHOM [HORROR] by 「The Crimson Crusaders」. Roblox’s public Games API showed the experience updated on October 30, 2026 at 12:32 UTC when checked, and an official FATHOM: Chapter 2 Roblox event page exists. A scheduled event is not the same as a chapter being playable in every server, so verify the live experience before following a new route.
This page keeps three states separate: announced means a first-party page exists, live means the current experience exposes the content, and completed or historical means the event window or version has passed. That prevents a countdown mirror or old server from being mistaken for the active build.
Current status snapshot
The experience identity is Root Place ID 106632886527873 and Universe ID 10770101026. Use those IDs when the title changes or a search result shows another Fathom. The official event uses Event ID 6307202007602168591.
Official Chapter 2 event
Roblox hosts a first-party event entry titled for FATHOM: Chapter 2. That establishes a real developer-associated event destination. It does not by itself prove that a new chapter is already present in the server you joined.
Third-party event listings have displayed an October 31 to November 2 window and have differed slightly in time-zone presentation. Because those mirrors can convert or cache times differently, open the official Roblox event in your own session for the current countdown or status. Do not hard-code a converted hour into your play plan without checking the first-party page.
When the event begins, confirm three things: the official experience description has changed, the current server exposes Chapter 2, and the objective or chapter selector identifies the new content. Older Roblox servers may not update at the same moment. Rejoin only after the official surface indicates the update is live.
Timeline of verified public milestones
2026-10-30 — Current experience status checked
The Games API returned the title FATHOM [HORROR], creator group 「The Crimson Crusaders」, Root Place ID 106632886527873, and an update timestamp of 2026-10-30T12:32:40.165Z. The description continued to name Story Mode, Chase Mode, automatic saving, sound detection, grapple, camera flash, lockers, and solo or up-to-four-player play.
The badge API returned five enabled badges. The pass API returned nine product records, eight on sale and one off sale. Those catalogs are dynamic and should be rechecked after a major update.
2026-10-30 — Chapter 2 remains an official event handoff
The official Roblox event URL exists and is the correct first-party place to check timing. At this snapshot, this guide does not claim a complete Chapter 2 walkthrough, new map, new objective list, or new badge set. Those details need the live build or a creator-owned announcement.
2026-10-15 — Badge records created
Roblox’s public badge metadata shows Welcome, Chapter 1 Complete, Go Home, Go Deeper, and Untouchable created on October 15, 2026. Creation dates help establish the Chapter 1 progression record, but current award totals should always be treated as live.
2026-10-10 — Roblox universe created
The public Games API lists the experience creation timestamp as October 10, 2026. This is a platform record, not a promise about when every mode, badge, or pass became available.
What to check after an update
Start with the experience description. Confirm whether Story and Chase wording, player range, automatic saving, or survival-tool descriptions changed. Then inspect the mode selector and current objective. A new title or event banner does not guarantee that old route assumptions still apply.
Open the badge catalog and look for new enabled records. A Chapter 2 release may add badges, but no new badge should be invented before Roblox exposes it. Check the pass catalog for changed prices, sale status, description, or mode limits, especially Radar and Night Vision’s Nightmare restriction.
For Story progress, inspect the saved objective after joining. Do not assume Chapter 1 completion automatically unlocks or transfers every future choice. For Chase, read the current win condition instead of relying on an old round description.
How this affects existing guides
The Chapter 1 guide remains the route for the currently documented first chapter. It uses objective-led guidance rather than claiming fixed room positions, so small updates should not invalidate the survival plan.
The Modes hub keeps Story, Chase, solo, multiplayer, and the limited public facts about Nightmare separate. A new chapter does not automatically create a new mode. The Badges hub lists only records returned by the official API, while the Passes hub attaches a check date to dynamic prices.
Codes remain their own status. An update event does not prove that a promo-code system exists. The Codes page should change only when an official source or live UI provides a real redemption path.
Avoid stale-server and countdown mistakes
If the official page says an update is live but your server still shows old content, leave the run safely and rejoin. Do not repeatedly reconnect while an ending or badge award is processing. Confirm the event state before assuming a bug.
Time-zone mirrors may show an hour difference because they convert an event into local time or cache an earlier value. Use the timestamp displayed by Roblox for your account. Screenshots of a countdown can become stale immediately.
Do not treat player count, visits, favorites, badge award totals, or game-pass price as version numbers. They change independently and do not identify which content build a server is running.
Update acceptance checklist
An update is ready for a player-facing route when the official experience or creator confirms it, the current server exposes it, its objectives can be reproduced, and any new badge or pass has a first-party record. A video title alone can show player interest but cannot establish every step.
For Chapter 2, the next useful checks are the live selector, start objective, save behavior, new areas, Grinsworth changes, badge additions, and whether existing passes keep the same restrictions. Until those are current and repeatable, use the event link as an announcement rather than a completed walkthrough.