BO7 Limited Matchmaking Explained: Why You're Stuck in It, How Long It Lasts & How to Get Out (Season 6, 2026)

If Black Ops 7 has quietly dropped you into a tiny pool of samey lobbies — or you boot up and the only playlist you can touch is Nuketown 24/7 — you're in limited matchmaking, and there are two completely different reasons it happens. One is a security flag on your Activision account. The other has nothing to do with your account at all: it's your PC failing a security check. They look almost identical in-game, they need opposite fixes, and getting them confused is why so many players "reset five times" with nothing changing. Here's exactly how to tell which one you're in and how to get out of each.

Quick answer: Limited matchmaking means your account (or your PC) has been restricted to a small, separate pool of lobbies. It comes from one of two causes: (1) a security/enforcement flag — Activision's security team suspects cheating, uses unauthorized input devices, or has weighed player reports against a hidden account trust factor, so you're placed with other flagged accounts and earn no progression; or (2) a failed Microsoft Azure Attestation (MAA) check on PC — since Season 04, PCs without TPM 2.0 + Secure Boot enabled are limited to Nuketown 24/7 in BO7 (and Battle Royale Casual in Warzone). To get out: if it's attestation, enable TPM 2.0 and Secure Boot in your BIOS (AMD users on TPM software in the 3.x.0.x range must update the BIOS/firmware) — this is an instant, self-serve fix. If it's a security flag and you haven't cheated, there is no button to press: the flag is temporary and lifts on its own once the security team reviews the account (often within hours to a few days), and only permanent bans can be appealed. Check your status on Activision's ban appeal page.

Key takeaways

• Two causes, one symptom. Limited matchmaking is either a security/enforcement flag on your account or a failed PC attestation check — they are unrelated and need different fixes.
• The attestation one is the good news: it's a PC setting, fully in your control. Enable TPM 2.0 + Secure Boot, and for AMD systems update the BIOS if you're on fTPM 3.x.0.x.
• The security flag is not appealable and has no manual fix. It's a temporary review state; per Activision, accounts can be returned to normal at any time — and reports alone don't automatically trigger it, a hidden account trust factor does.
• You earn zero progression in a security-flagged limited lobby, and Skill Rating (SR) can be revoked if a Ranked Play restriction is applied — so it stalls camo, level, and rank grinds cold.
• Never buy a "shadowban remover" or use tools that alter camos/loadouts — Activision explicitly calls that cheating and it escalates a temporary flag into a permanent ban.

What "limited matchmaking" actually is

Limited matchmaking is a state where Call of Duty stops matching you into normal lobbies and instead drops you into a separate, restricted pool. Activision describes it plainly in its official Call of Duty Security and Enforcement Policy:

"Accounts in this state may be placed in limited matchmaking lobbies with other accounts in a similar state... Players and their party members may not earn progression in limited matchmaking lobbies. At any time, the account may be returned to normal matchmaking, placed in a limited matchmaking state again, or it may receive a temporary or permanent ban or other penalties."

Two things matter in that wording. First, your party gets pulled in with you — squad up with a flagged friend and you'll all land in the limited pool. Second, you don't earn progression, so any time spent there is wasted for weapon XP, camos, and battle-pass tiers.

The confusion starts because a second, unrelated system produces an almost identical experience. Understanding which one you're in is the whole game.

Cause #1 — A security/enforcement flag (the "shadowban")

This is the one most people mean. Activision's RICOCHET Anti-Cheat and security team flag accounts they suspect of manipulating the game — cheating, modding, unauthorized scripted input devices (Cronus Zen, XIM Matrix), or content-altering tools. Player reports feed into it too, but reports alone are not a switch.

Players in the affected r/blackops7 thread describe it accurately: one legit high-KD player was "in limited matchmaking / shadow banned 3 times and yet [not] banned," and another explained the real mechanic — "reports are the main cause, but your account has a hidden trust factor that determines how easily you will get put into limited matchmaking." A third noted the review is time-boxed: "they simply don't have the manpower to look at everyone in a timely manner, so after a time limit you're set free till you get flagged again." That matches Activision's own line that an account "may be returned to normal matchmaking... at any time."

How to know it's this one: you can queue multiple modes but every lobby is full of blatant cheaters/other suspects, you earn no XP, and it clears on its own after a while (players report anything from a few hours to a few days). There is no BIOS or hardware message.

How to get out — honestly:

• If you haven't cheated, wait it out. The flag is a temporary review state; it lifts when the security team clears the account. There is no legitimate button, ticket, or purchase that removes a limited-matchmaking flag faster.
• Check your enforcement status on the ban appeal page — it shows whether your account is in good standing, limited, or banned. Note Activision's rule: only permanent bans can be appealed; a limited-matchmaking state itself is not an appealable ban.
• Do NOT use "shadowban removers," VPN lobby tricks, or camo/loadout-unlock tools. Activision's policy is explicit: "Avoid tutorials and services that offer ways to modify your camo or other game content... considered cheating. We will enforce accordingly." That turns a temporary flag into a permanent, cross-title ban.

If you want the deeper timeline on the enforcement side — how long a shadowban lasts and how to read your status — see our Black Ops 7 shadowban guide.

Cause #2 — Failed PC attestation (the Nuketown 24/7 lockout)

This is the newer, far more fixable cause, and it's the one behind the "I can only play Nuketown 24/7" complaints. Since Season 04, RICOCHET requires Microsoft Azure Attestation (MAA) to access competitive playlists on PC. From Activision's official RICOCHET Season 04 update:

"Players who fail Microsoft Azure Attestation (MAA) checks will be placed into a separate matchmaking pool... Players who do not complete attestation will be limited to Nuketown 24/7 in Call of Duty: Black Ops 7 and Battle Royale Casual in Call of Duty: Warzone."

Crucially, this is not a punishment and not a report — it's a PC security-configuration check. Remote Attestation validates your machine's security settings directly with Microsoft (part of RICOCHET's TPM 2.0 implementation), which is harder to spoof than local checks. If your PC isn't compliant, you get a notification that your system failed attestation, and access is trimmed accordingly.

How to know it's this one: you're on PC, you saw a "failed attestation" / secure-boot notification, and your playlist access is chopped down to Nuketown 24/7 (BO7) or BR Casual (Warzone). Console players are not affected by MAA.

How to fix it — step by step:

• Enable TPM 2.0 in your motherboard BIOS/UEFI. On Intel boards this is often labeled PTT (Platform Trust Technology); on AMD it's fTPM.
• Enable Secure Boot in the same BIOS menu (you may need to set the OS type to "Windows UEFI mode" and disable CSM/Legacy).
• Save, reboot, and re-launch the game — attestation re-checks on startup.
• AMD-specific trap: if you enabled fTPM but still fail, you may be on AMD TPM software in the 3.x.0.x range, which returns an attestation error. The fix is to update your motherboard BIOS/firmware to a newer version.
• Check your party. Per Activision, if a squadmate's PC isn't compliant, you get the failed-attestation message too — so every PC in the party needs TPM 2.0 + Secure Boot on.

For the exact "BIOS update required / still failing after enabling" edge cases, we've documented them separately in the Warzone failed attestation BIOS fix and the BIOS update required but still failing fix.

How to tell the two apart fast

Run this check before you touch anything:

Signal	Security flag ("shadowban")	Failed attestation (MAA)
Platform affected	PC and console	PC only
On-screen message	None — you just notice bad lobbies	"Failed attestation" / Secure Boot notice
Playlist access	Multiple modes, but all vs. suspects	Chopped to Nuketown 24/7 / BR Casual
Progression	None earned	Normal in the allowed playlist
Fix	Wait it out (temporary review)	Enable TPM 2.0 + Secure Boot
In your control?	No	Yes
Clears by itself?	Yes, after review	No — you must fix the PC

If you're on console and stuck in samey no-XP lobbies, it's the security flag every time — attestation can't touch you.

What limited matchmaking costs you (and getting back on track)

Whichever cause it is, the practical damage is the same: your grind stops. A security-flagged lobby earns zero weapon XP, no camo progress, and no battle-pass tiers, and if a Ranked Play restriction gets stacked on, Activision notes Skill Rating (SR) and rewards may be revoked. With Season 6 (The Haunting) being BO7's final big update before Modern Warfare 4 resets mastery progress, lost days matter — every match in a limited pool is a match not spent finishing camos.

Once your account is clean and back in normal matchmaking, if you're staring at a mountain of weapon levels, prestige, or camo objectives you don't have time for, a legitimate boosting service can close the gap without ever touching your account's security standing:

Get back on schedule the safe way:

- CoD Warzone & BO7 Ranked Boost — climb back to your real SR after a restriction lifts.

- CoD Account & Weapon Leveling — recover the weapon XP and levels the limited-pool days cost you.

- All Call of Duty services — camos, leveling, and more for BO7 & Warzone.

Frequently Asked Questions

Does limited matchmaking mean I'm banned? No. Limited matchmaking is a restriction, not a ban. Per Activision's Security and Enforcement Policy, an account in this state can be returned to normal matchmaking at any time, or it may later escalate to a temporary or permanent ban. It sits below a ban — think of it as a review holding pattern.

How long does BO7 limited matchmaking last? If it's a security flag, there's no fixed timer — Activision reviews flagged accounts and lifts the state when they're cleared, which players report can be anywhere from a few hours to a few days. If it's a failed-attestation (MAA) restriction, it lasts until you enable TPM 2.0 and Secure Boot and pass the check; it will not clear on its own.

Do player reports alone put me in limited matchmaking? No. Reports feed the system, but they don't flip a switch by themselves. Accounts carry a hidden trust factor, and the security team combines reports with RICOCHET detection data. Legit high-KD players get mass-reported constantly without ever being flagged, which is why "just reports" isn't the full story.

Can I appeal limited matchmaking? Not directly. Activision states that only permanent bans may be appealed. You can, however, use the ban appeal page to check your account's current enforcement status. For a temporary limited-matchmaking flag, waiting for the review to complete is the only legitimate route.

Why can I only play Nuketown 24/7 in Black Ops 7? That's the failed-attestation lockout on PC, not a shadowban. Your PC hasn't passed Microsoft Azure Attestation, so you're restricted to Nuketown 24/7 in BO7 (and BR Casual in Warzone) until you enable TPM 2.0 + Secure Boot in your BIOS. AMD users on fTPM software in the 3.x.0.x range must update the BIOS to fix it.

Will using a VPN or a "shadowban remover" get me out faster? No — and it's actively dangerous. Activision explicitly treats camo/content-modifying tools and game manipulation as cheating and enforces with escalating penalties, up to permanent cross-title bans. Nothing you buy or install legitimately removes a security flag; the only safe move for a clean account is to wait.