Use the exact Icecream link, retry a fresh Roblox session, and verify general Roblox status before treating one empty endpoint as a game outage. Then identify whether the problem affects the main, AFK, or 1v1 place.
Availability answer: the collected endpoints disagreed. This page does not claim Icecream is down; it gives checks that separate a wrong link, a Roblox incident, a local session problem, and a mode-specific failure.
Stop when the game opens. Changing several things at once makes it harder to tell whether the destination, Roblox, the local session, or one mode caused the problem.
Step 1
Use place 128084046148047 from the confirmed Roblox URL. Do not diagnose a similarly named simulator, shop, tycoon, or item page.
Open exact gameStep 2
Review the official Roblox status page for an active platform incident. If one is listed, wait for the affected service to recover before changing local settings.
Open Roblox statusStep 3
Close and reopen the Roblox app or browser, sign in through Roblox, and retry. If available, compare another supported device or network without sharing credentials.
Step 4
Test the main destination first, then AFK place 88074104800259 and 1v1 place 140418400629532. Record which exact place fails and the visible error.
A discovery result may show activity while a public-server request returns no rows, fails by region, or times out. That conflict does not prove an outage, a private-only game, or a zero-player state. Retry later and rely on the visible Roblox error plus official platform status before drawing a conclusion.
Keep the endpoint caveat next to every availability conclusion.
Return to the main place before retrying the mode. Note the exact place ID, device or browser, operating system, network type, timestamp with timezone, and exact error text. Send only diagnostic details through the contact page. Never send a password, cookie, two-factor code, recovery code, browser profile, or payment information.
A matching name is not enough. Compare the place ID before following advice.
Restart first. Do not erase unrelated browser or app data without a specific reason.
No legitimate diagnosis requires Roblox credentials, cookies, or recovery codes.
The checked official endpoints conflicted, so this site cannot responsibly call the game down from that snapshot. Run the four checks and review Roblox platform status.
Confirm place ID 128084046148047, then open the canonical Roblox destination in a clean supported app or browser session.
Return through the main place, retry AFK place 88074104800259, and record the device, time, and exact visible error if it persists.
Return through the main place, retry 1v1 place 140418400629532, and avoid treating a mode-specific failure as a full-game outage.
