Roblox Error Code 267: Why You Were Kicked and What You Can Do
Error 267 means a script inside the experience removed you. It could be an idle timer, a moderator, a ban list or an anti-exploit rule. Here is how to tell which one, and what actually helps.
The short answer
Error 267 means a script inside the Roblox experience you were playing kicked you out. The kick comes from the game's developer, not from Roblox moderation. Common triggers are idle or AFK timeouts, a game-specific ban list, a moderator using an admin command, an anti-exploit rule, or the game restarting. Because the kick originates in the game, there is no client-side fix — the useful steps are identifying the trigger and, where it is a false positive, reporting it to the developer.
Verified and last updated August 6, 2026.
- Time needed
- 10 min
- Difficulty
- Beginner
- Read time
- 5 min
Error 267 is the code that generates the most unnecessary panic, because the message sounds like discipline and people assume Roblox has taken action against them.
It has not. Roblox did not kick you. The game did.
Where 267 comes from
Every Roblox experience can call a function that removes a player from the server with a message. Developers use it for all sorts of things — idle timers, admin commands, ban lists, anti-exploit rules, orderly shutdowns before an update. When a game does this, the client shows error 267 and whatever message the developer attached. Roblox is only the messenger, and it keeps no record of it against your account.
That changes the whole approach. There is no cache to clear and no firewall setting to tick, because nothing on your computer is broken. What matters is working out which of five triggers fired.
Read the message first
Most developers attach a reason to the kick, and it appears right underneath the error. Read it before anything else, because it usually tells you exactly what happened:
- "You have been idle for too long" — an AFK timeout. Rejoin and stay active.
- "You have been banned from this game" — a game-level ban list.
- "Kicked by an admin" or a moderator's username — a manual kick.
- "Server restarting" or "Game updating" — routine maintenance.
- "Unexpected client behavior" — this is actually a 268-class event; read the 268 guide.
- No message at all — a script called the kick without one, which is most often an anti-exploit rule or an unhandled error in the game's code.
The five triggers, and what each one means for you
If you can rejoin, it was not a ban
The fastest test in the world: try to join again.
- You get in and play normally — it was an idle timeout, a server restart, or a one-off moderator action. Nothing to fix.
- You are kicked again within seconds, every time — it is a ban list or a persistent anti-exploit rule.
- You get in but are kicked again after a few minutes — it is behavioural. Something you are doing, or something running on your machine, is tripping a check.
The anti-exploit false positives worth knowing about
Developers write their own detection, and the thresholds are often tighter than they should be. These are the ones we have reproduced or seen reported repeatedly:
Connection stalls that look like teleporting. If your connection freezes for a second and then delivers a burst of queued position updates, a movement check sees you cross a large distance instantly. Strict scripts kick for that. It is by far the most common false positive, and it is why 267 sometimes tracks perfectly with rubber-banding. Fixing it means fixing the jitter — our ping and jitter guide covers the queue-management change that eliminates the burst pattern.
Overlays and memory-reading software. MSI Afterburner, RivaTuner, Cheat Engine open in the background for another game, aggressive antivirus exploit-protection modules. All can look like tampering.
Unusual but legitimate play. Very high click rates, a movement exploit in the game's own physics that you found accidentally, or being out of bounds after a glitch.
Rejoining too fast. Some games rate-limit joins per user and kick on a rapid rejoin. Waiting thirty seconds is the entire fix.
A quick way to separate client from game
Join a completely different, popular experience and play for ten minutes. If you are never kicked there, your client is fine and the issue is specific to the original game. If you get kicked everywhere, it is your machine or your connection — start with the 268 guide, which covers the client-side causes properly.
If it is a game-level ban you think is wrong
Game ban lists are managed by developers using their own tooling, and that tooling is frequently homemade. Bans applied to the wrong user ID, bans inherited from a shared device, and bans left over from a mass action against a raid are all genuinely common.
Roblox support cannot help. They have no visibility into a developer's ban list and no authority over it. What works:
- Find the game's official Discord — the link is usually on the experience page or in the group description.
- Look for an appeals channel. Larger games have a form.
- Give them your exact Roblox username, the approximate time you were kicked, and the message you received. Nothing else. Long protests of innocence get ignored; a clean report with an ID gets checked.
Be realistic about the odds. Small teams have no appeals process at all, and no obligation to run one.
What does not help
What works
What doesn't
Where 267 sits among the other codes
267 and 268 are the two script-issued kicks and they get confused constantly. The rest of the 260s are genuine connection failures with completely different fixes — 277 for mid-game drops, 279 for join failures.
If you are seeing several codes in a session, the full Roblox error code index shows which ones share a root cause, which saves you from fixing the same thing three times.
Frequently asked questions
Is error 267 a Roblox ban?
No. 267 is a kick from one specific experience, issued by that experience's own code. It does not touch your Roblox account, does not create a moderation record, and does not affect any other game on the platform. A genuine Roblox account ban appears as a message on the website when you log in, with a stated reason and duration.
How long does a 267 kick last?
The kick itself is instant and over — you can usually rejoin immediately. What varies is whether the thing that caused it will fire again. An idle timeout will not stop you rejoining. A game-level ban list will kick you again within seconds of every join, which is how you can tell the difference in under a minute.
Can I appeal an error 267 kick to Roblox?
There is nothing for Roblox to appeal. The kick was issued by the game's developer using their own code, and Roblox has no involvement in or record of it. If you believe you were banned from a game unfairly, the only route is the developer — usually their Discord server or a group wall.
Why does 267 keep happening in one game the moment I join?
That is the signature of a game-level ban list. Many experiences maintain their own banned-user lists and check them in a join handler, which means the kick lands within a second or two of loading in. Nothing on your machine will change that. If you think it is a mistake — banlists get applied to the wrong user ID more often than developers admit — contact the game's team.
Does error 267 mean the same thing as 268?
They come from the same mechanism but carry different meaning. Both are script-issued kicks. 268 specifically indicates the game detected 'unexpected client behaviour', which is the anti-exploit branch. 267 is the general case and covers idle timeouts, moderator kicks, ban lists and server maintenance. If your message says unexpected client behaviour, read the 268 guide instead.
About the author
Roblox & Live-Service Editor
Priya started scripting in Roblox Studio at fourteen and has since published three experiences, the largest of which passed 1.2 million visits. That background is why our Roblox coverage explains why a code fails rather than just telling you to try again later.
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.