FixMyError
Gaming Errors

How to Fix Roblox Error 772 (Teleport Failed: Web Services Offline)

By FixMyError · Updated October 16, 2026 · 6 min read

Error Code 772Plain English: Roblox tried to teleport you to another place, but one of its own web services was offline — the move never happened, and you are still where you started.
Quick answer: Roblox error 772 means a teleport failed because one or more Roblox web services were offline. Check status.roblox.com first — if there's an outage, just wait. If services are fine, restart your router, switch to Google DNS, and allow Roblox through your firewall. Full steps below.

What Error 772 means

Error 772 belongs to Roblox's family of teleport-failure errors — the same family as 769, 770, 771, and 773 — and it shows up at a very specific moment: you click the button to join a sub-place, follow a friend into another experience, or take a portal to a different part of a game, and instead of loading, you get a dialog that reads "Teleport failed. One or more web services used by Roblox are offline. Please try again later. (Error Code: 772)".

What's happening behind that message is straightforward. A Roblox teleport isn't a simple page change — it's a coordinated handoff between several web services that verify your account, reserve a slot on the destination server, and move your session over. If any one of those services is down, under maintenance, or just having a brief hiccup, the handoff can't complete and Roblox aborts the teleport with error 772. You don't lose anything in the process: your avatar, items, and progress are untouched, and you're simply left sitting in the place you tried to leave.

Because the message itself names Roblox's web services, this is one of the few Roblox error codes where the platform is usually the one at fault. Service blips are the single most common cause, which is why the first step below is a server-status check rather than anything on your machine. That said, your own setup can absolutely cause or contribute to 772: if a firewall blocks the Roblox player from reaching those same web services, or your network path to them is broken, the game can't tell the difference — it just reports that the services appear offline. The step-by-step list below is ordered to rule out the most likely cause first, so you don't waste time reinstalling the game when the real problem is a ten-minute outage on Roblox's end.

Common causes

How to fix Error 772 — step by step

Work through these fixes in order. Error 772 is most often a Roblox-side problem, so the list starts with the checks that save you from troubleshooting something you can't fix.

  1. Check Roblox server status first. Before changing anything on your device, open status.roblox.com in a browser and look for active incidents. Error 772's most common trigger is one or more Roblox web services being offline, and when that's the cause, no amount of troubleshooting on your end will help — the teleport machinery simply isn't running. If the status page shows an outage or degraded service, close the game and check back in 15 to 30 minutes. Most web-service hiccups are fixed by Roblox engineers within the hour.
  2. Wait a few minutes, then teleport again. If the status page shows everything green but the error just started, you may have hit a brief service blip. Fully close the Roblox player — don't just minimize it — wait at least two minutes, and relaunch. When you try the teleport again, don't spam the button: repeated rapid attempts during a service wobble can stack up failed requests and make things worse. Make one calm attempt. Many players find error 772 clears on its own within a few minutes, exactly as the message itself suggests.
  3. Restart your router and switch to Google DNS. Teleport requests travel through several Roblox web services, and a stale or flaky network route can make them fail even when those services are healthy. Unplug your router and modem for a full 60 seconds, plug them back in, and wait for the connection lights to stabilize. Then change your DNS to Google's public servers: on Windows, open Settings > Network & Internet > Wi-Fi (or Ethernet) > your network > Edit (under DNS server assignment), set it to Manual, and enter 8.8.8.8 as the preferred DNS and 8.8.4.4 as the alternate. Open Command Prompt as administrator and run ipconfig /flushdns to clear the old resolver cache, then restart your PC and try the teleport again.
  4. Allow Roblox through your firewall and antivirus. Error 772 appears when Roblox can't reach the web services it needs for the teleport, and security software is a frequent silent blocker. Open Windows Security via Settings > Privacy & Security > Windows Security > Firewall & network protection > Allow an app through firewall, click Change settings, and make sure Roblox is allowed on both private and public networks. If you run a third-party antivirus, open its firewall or application-control settings and add the Roblox player folder (%localappdata%\Roblox\Versions) to the exceptions list. Restart the Roblox player afterward and retry the teleport.
  5. Clear the Roblox cache and disable any VPN or proxy. Corrupted cached data and rerouted connections can both break the web-service calls behind a teleport. First, press Windows + R, type %localappdata%\Roblox, and delete the cache folder inside. If you play through a browser, clear the browser's cache and cookies for the Roblox site. Second, turn off any VPN, proxy, or DNS-over-HTTPS service while you test — these tools can route Roblox traffic through servers that the platform's web services reject, producing error 772. After clearing the cache and disabling the VPN, restart your device so the fresh network state takes effect, then try the teleport once more.
  6. Reinstall Roblox with a clean slate. If the error persists, a corrupted install may be failing the web-service calls. Uninstall Roblox from Settings > Apps > Installed apps, then press Windows + R, type %localappdata%\Roblox, and delete the entire Roblox folder to remove leftover files and cached certificates. Restart your PC, download a fresh copy from roblox.com, and install it. Log in and attempt the teleport again. A clean install rules out every client-side cause at once — so if error 772 still appears afterward, the problem is almost certainly on Roblox's servers, and waiting is the only fix left.

Did this fix it? Quick checklist

If error 772 keeps returning, try teleporting to a different destination to rule out a problem with one specific place — the target experience may be under review or having its own server issues. As a last resort, contact Roblox Support from roblox.com/support with the error code and the place you were trying to teleport to; since 772 often involves their web services, they can see outages and account-specific problems you can't. But in most cases, the steps above — or just waiting out the service hiccup — get you back in within the hour.

Frequently asked questions

What does Roblox error code 772 mean?

Error 772 appears when Roblox tries to teleport you from one place to another and the move fails. The full message reads: Teleport failed. One or more web services used by Roblox are offline. Please try again later. (Error Code: 772). In plain terms, the server-side machinery that performs the teleport wasn't reachable when you pressed the button — so nothing moved you, and you're still where you started.

Is error 772 my fault or is it Roblox's problem?

Most of the time it's Roblox's problem. The message itself points at their web services being offline, which happens during outages, maintenance windows, and brief service hiccups. That's why checking status.roblox.com is step one. Your own setup can cause it too — a firewall block, a corrupted install, a VPN rerouting traffic, or bad DNS — but those are the exception rather than the rule. If the status page shows an incident, it's theirs, and waiting is the fix.

How is error 772 different from errors 769, 770, 771, and 773?

All five are teleport-failure errors, but each points at a different reason the teleport failed. Error 769 usually means the teleport failed for an unknown or permissions-related reason, 770 means the target place doesn't exist or its root place is inactive, 771 means the destination server closed or no longer exists, 772 means Roblox's own web services were offline during the teleport, and 773 means the destination place is restricted so you aren't allowed in. The fixes overlap (server status, network, reinstall), but 772 is the one most likely to be purely server-side.

How long does error 772 usually last?

If it's a Roblox-side issue, it typically clears within a few minutes to an hour, once the affected web services come back online — the error message itself says to try again later. During a major outage it can take longer, so keep an eye on status.roblox.com for updates. If the cause is on your side — a firewall block, a corrupted install, or bad DNS — it lasts until you fix the underlying problem, which is what the steps above are for.

Will reinstalling Roblox delete my progress or items?

No. Your avatar, inventory, Robux, friends list, and game progress all live on Roblox's servers under your account, not on your device. Uninstalling and reinstalling the player only replaces the local app files and cached data. As long as you log back into the same account after reinstalling, everything will be exactly where you left it. Backing up isn't necessary, but make sure you remember your login credentials before you start.

Related fixes