Roblox Forum

Posted: **Thu Oct 22, 2026 9:59 pm**

Quick Summary

Teleport Failed error codes 769, 770, 772 and 773 all mean the jump between places never started. The player is left in the current server, not banned and not kicked.[1][2]
769 and 770 are the generic ones. 769 covers a failed teleport request and a failed reconnect attempt. 770 means the destination place does not exist, was deleted, or its start place is not active.[1][2]
772 means the target server is full. 773 means the destination is not approved, under review, or restricted.[1][2]
The documented developer response is to wrap the call in pcall(), retry a limited number of times, and listen to TeleportService.TeleportInitFailed for the failure that arrives after a call returned success.[3]
Roblox's own support pages do not document any of these four codes. Their published error code index covers 264, 266, 267, 268, 270, 277, 279, 280, 403, 524, 600 and Failed to Load Library, and points everyone else to support.[4]

What Teleporting Actually Is

Roblox games are usually not one map. A single experience is split into multiple places, each with its own servers, and TeleportService is the class that moves a Player between those places and servers.[3]

Three things make teleporting a different problem from joining a game normally. The service does not work while you playtest in Studio, so you have to publish and test in the Roblox client before you can see what your code does.[3] Only server scripts are allowed to call TeleportAsync(), because client-side teleport calls are an exploit surface, and the older client-side Teleport() method is deprecated for new work.[3] And a successful call is not the same as a completed teleport, which is the part that causes most of the confusion around these error codes.[3]

What Each Code Means

The four codes are grouped because they look similar on screen, but they point at four different problems.

Code	Message you see	What it means
769	Teleport Failed: Unknown exception, or Reconnect was unsuccessful. Please try again.	The teleport request failed, or a reconnect button press failed. The wiki records that it also shows up when a user who was warned, banned or terminated tries to reconnect.
770	Teleport Failed: Unknown error, or the root place message.	The destination place does not exist or has been deleted, or the game's root place is not active.
772	Teleport failed: server is full.	You tried to join a server that has no free slot.
773	Teleport Failed: This game has not been approved, yet, or Attempted to teleport to a place that is restricted.	The destination is under review, not approved, or restricted to you.

The 769 entry has a second meaning worth separating out, because it is the one players run into most. Roblox's creator docs describe a failure mode where the TeleportAsync() call returns without error and the teleport still does not happen at the last moment, leaving the player in their current server. When that happens, the TeleportInitFailed event fires instead of throwing, carrying the player, the TeleportResult enum, the error message, the place ID and the teleport options.[3]

That is the documented reason to listen for the event rather than relying on the return value of the call. A player who gets a 769 and sees it as a mystery error is usually hitting one of two paths: the call failed outright, or the call succeeded and the teleport was rejected later.

The Engine's Own Failure Names

Roblox does not hand developers the player-facing codes. It hands them an enum, and the mapping between the enum and the numbers on screen comes from the wiki rather than from Roblox. The TeleportResult enum has eight items:[5]

Success (0), the teleport went through.[5]
Failure (1), the teleport failed for an unknown reason.[5]
GameNotFound (2), the game the player tried to reach could not be found.[5]
GameEnded (3), the game has ended.[5]
GameFull (4), the game is full.[5]
Unauthorized (5), the player is not authorized to complete this teleport.[5]
Flooded (6), too many teleport requests have been made recently.[5]
IsTeleporting (7), the player is currently being teleported.[5]

That list is what you can actually branch on in code, and it is the reason the documented retry logic distinguishes between failure types. Roblox's own SafeTeleport example waits 15 seconds after a Flooded result and 1 second after a generic Failure, then retries, and it raises an error for anything else rather than retrying an invalid call:[3]

Code: Select all

local ATTEMPT_LIMIT = 5
local RETRY_DELAY = 1
local FLOOD_DELAY = 15

repeat
    success, result = pcall(function()
        return TeleportService:TeleportAsync(placeId, players, options)
    end)
    attemptIndex += 1
    if not success then
        task.wait(RETRY_DELAY)
    end
until success or attemptIndex == ATTEMPT_LIMIT

The exact timings in that snippet are Roblox's example values, not requirements. The structural point is what matters: retry Flooded and Failure, treat everything else as invalid, and do not retry forever.

The Settings That Cause 769, 770 and 773

A lot of these errors are not network problems. They are configuration. Three settings control whether a teleport is allowed to start at all.[3]

Creator Dashboard, Audience, Access Settings, Access Control for Places. This decides whether players can join any place in your game or must first join the start place. Roblox calls it the most critical setting for preventing teleport based exploits.[3]
Creator Dashboard, Place, Access, Direct Access Control. This overrides the game level setting for a single non-start place.[3]
Studio, File, Experience Settings, Security, Allow Third Party Teleports. This controls teleports from your game to games you do not own. Roblox notes you can leave this disabled and still teleport players between published games you own.[3]

The three Access Control for Places values are worth knowing by name, because they explain a whole class of player reports:[3]

Fully open, players can join any place through teleports from any game, including deep links, game invites and joining a friend.[3]
Limited to same universe, players can only join non-start places through teleports within your own games. Roblox recommends this for legacy games that are not moving to secure teleports.[3]
Secure within universe only, players can only join non-start places through server-initiated teleports within the game. Roblox recommends this for games with a strict progression system, for test places, and for places that exclusively use reserved servers.[3]

If your game is set to Secure within universe only and a player is sent by a client script, the request is refused. That is a configuration rejection, not a network fault, and no amount of reconnecting will fix it.

There is also a data conflict worth checking if a teleport fails for no visible reason. TeleportOptions lists three combinations that are not allowed together and cause an error when passed to TeleportAsync(): ReservedServerAccessCode with ServerInstanceId, ShouldReserveServer with ServerInstanceId, and ShouldReserveServer with ReservedServerAccessCode.[6]

Fixing It, In Order

Roblox's published error code index does not cover these four codes, so there is no official troubleshooting page to follow. Their published guidance for code 524, which is the closest relative, is ordered from cheapest to most disruptive: check private server settings, check server permissions, restart the app and device, check for server availability, then troubleshoot the network.[7] That order is a sensible template for these codes too.

Check the destination before blaming your connection. Confirm the place still exists and is approved, and that you are allowed in. A 770 on a deleted or unpublished place is not a network problem.[1][2]
Check whether the target server is full. If it is, 772 is the correct answer and waiting is the only fix.[1][2]
Check status.roblox.com before changing anything on your machine. If Roblox is reporting a service disruption, waiting is the correct action and a reinstall will not help.[8]
Make sure you are teleporting as an individual rather than as a group. Roblox's own guidance is to move teleport logic into server scripts, and teleporting one player at a time sidesteps party size limits.[3]
Look at your access settings. If the destination is a non-start place and your game is set to Limited to same universe or Secure within universe only, confirm the teleport is server-initiated and that the player is allowed into that place.[3]
Verify the teleport is not being called from Studio. The service does not work during playtesting, so testing has to happen in the published game in the Roblox client.[3]
Wrap the call in pcall() and retry, and connect to TeleportInitFailed so a late rejection does not pass silently.[3]
Only then touch the network. Restart the router, switch from Wi-Fi to mobile data, and reinstall Roblox if the error is isolated to your machine.[7]
[/list=1]

The one thing that genuinely does not help is a VPN. A VPN changes where your traffic appears to come from, and it does nothing about a full server, an unapproved game, a deleted place or a rejected teleport request. Roblox's own guidance for teleport errors is about permissions, review status, server availability and network stability, not about your apparent location.[7]

What Happens to Player Data

Teleporting a player between places discards any local data tied to that player, which is why a lost teleport often feels worse than the error message suggests.[3]

Roblox's guidance splits the solution by how sensitive the data is. Use data stores or memory stores for anything secure like in-game currency or inventory. Use TeleportOptions:SetTeleportData() only for basic non-secure data, because that data is visible to the client and unencrypted.[3]

Two limits on teleport data are easy to trip over. It can only contain value types, so it cannot hold an Instance, a connection, a signal, a function or a SharedTable, and Roblox strips disallowed values and writes an error to the developer console. And teleport settings, which are a separate client-side mechanism, are not preserved after the user leaves the game universe, unlike data store values.[3]

FAQ

Is error 769 a ban?

No. It is a failed teleport or a failed reconnect. The wiki records a separate path where the code appears when a user who was warned, banned or terminated tries to reconnect, but the code itself is not a ban notice and it is not the ban code. Roblox's own support documentation for error code 267 is the one that covers a kick from an experience.[1][2]

Why does 769 happen in Studio?

Because TeleportService does not work during playtesting in Studio. Roblox states this directly in the teleport documentation, and the fix is to publish the game and test in the Roblox client.[3]

What is the difference between 772 and 773?

772 is capacity. The server you tried to reach is full. 773 is permission. The game is under review, not approved, or restricted to you. A 772 clears on its own when a slot opens. A 773 does not clear by waiting.[1][2]

Can I teleport to a game I do not own?

Only if Allow Third Party Teleports is enabled in your place's security settings. Roblox's documentation states you can leave that setting disabled and still teleport players between published games you own.[3]

Is the enum number the same as the error code on screen?

The TeleportResult enum values run from 0 to 7 and are the documented API surface. The player-facing codes 769, 770, 772 and 773 are documented by the Roblox Wiki rather than by Roblox. Treat the enum as your code contract and the numbered codes as the player-facing labels.[5][1]

What about error 610?

It is a different class of error. The wiki records 610 as appearing when a DNS resolution fails while connecting to a server, or when a user tries to join a paid access game from the server list before buying it. The wiki also notes that error code 524 can appear if it was the last place the user joined.[1][2]

Sources

Roblox Forum

Roblox Teleport Failed Error Codes 769 770 772 773 Explained: What Each One Means and the Fix Order (October 2026)

Roblox Teleport Failed Error Codes 769 770 772 773 Explained: What Each One Means and the Fix Order (October 2026)