Hi! When Instagram selfie verification gets stuck, it usually falls into a few “buckets”:
• Submission problem (camera permission, app glitch, corrupted cache, unstable connection)
• Integrity / security challenge (new device/login location, suspicious activity flags, repeated attempts)
• Review delay (it accepts the video selfie but sits on pending or “we’re reviewing your info”)

I’ll keep this safe — no risky steps like buying services, sharing codes, or “hacks.”

First, what exactly do you see on-screen: loading loop, “try again later”, “couldn’t confirm it’s you”, or pending review? And are you on iPhone or Android?

That’s a super common pattern after a “new device / new network” login event — especially school Wi-Fi + laptop sign-in, then your phone gets a confirm it’s you flow.

Let’s separate “upload is failing” vs “Instagram is rate-limiting the verification attempt.” Quick questions (order matters here):
1) Are you using the official Instagram app from the App Store, or a modified/clone app?
2) Any VPN, iCloud Private Relay, ad-blocking DNS, or “privacy” profile running on the phone?
3) Did you recently change anything on the account (email/phone/password), or did you get “suspicious login attempt” messages?

Helpful. A VPN + school network is a classic trigger for repeated security checks, and it can also mess with the upload step (video selfie uploads are more sensitive than normal browsing).

Safe diagnostics (no account changes yet):

• Camera permission check: iPhone Settings → Instagram → make sure Camera is allowed. If Camera permission is off or restricted, the flow can behave weirdly (recording looks fine but submission fails).

• Network test: Do one attempt on a stable home Wi-Fi or cellular (not school Wi-Fi). And for the test, keep VPN OFF.

• Rate-limit clue: If “Try again later” appears after multiple tries, that usually means you hit a temporary verification cooldown — re-submitting over and over can make the wait longer.

When it spins forever, does it ever show an error code like challenge_required, or does it just hang?

Got it — if upload completes but it hangs at “processing,” that points more to the verification decision step (or the app not receiving the response) than to your camera itself.

Two important “risk checks” before we touch anything:
1) Any third-party apps connected (followers/analytics/auto-posting tools)? Those can create extra risk signals and keep you in a verification loop.
2) Are you getting any emails from Instagram that say “Your information is being reviewed,” “We need to confirm your identity,” or “Someone tried to log in”? (Check spam/promotions too.)

Also: are you trying inside the app only, or does it also happen if you attempt login from a browser and it pushes you back to the selfie step?

Totally fair to be stressed — but we’ll keep it controlled so you don’t accidentally trigger more security friction.

The follower-stats tool detail matters because even old third-party access can be part of the “why am I seeing this identity check?” story. I’m not asking you to revoke anything right this second — just to confirm the landscape first.

A safe way to narrow it down without “big moves”:
• Attempt spacing: Do one selfie submission attempt, then stop. If you keep hitting it, you’ll mostly learn about rate limits, not the real cause.

• Clean environment: For the next attempt, use: VPN off, strong lighting, no hats/masks/filters, and hold the phone steady. The goal is to reduce false “can’t confirm” signals and avoid repeated re-tries.

• Device context: Were you previously logged in on this same iPhone for a long time, or is this a fresh install/new phone? Instagram sometimes treats “same device” vs “new device” very differently.

You didn’t “break” anything — but repeated attempts can definitely turn a normal verification step into a cooldown situation. That’s why “Try again later” shows up.

Here’s what I’d avoid for now (to keep access chances high):
• Don’t keep re-submitting every few minutes.
• Don’t trust random “verification services” or people asking for screenshots/video — those are common scams.
• Don’t install modified clients or “unban” tools (they can add more risk signals).

Low-risk checks you can do today:
1) Confirm Instagram has Camera + Photos permissions (some iOS privacy settings can block background processing).
2) Make sure the app is fully updated (older builds can glitch during identity confirmation flows).
3) Try a single attempt on cellular data if Wi-Fi is inconsistent (or vice versa). The point is to avoid network middleboxes that interrupt uploads/responses.

When you try now, does the screen say anything like “We’ll review your info” or “This may take a day”? Or is it just the spinner and then nothing?

Yes — low storage can be a sneaky factor. Even if you can record the clip, the app may need extra space to process/compress it before upload, and iOS can behave inconsistently when storage is near full.

That said, we’ll keep it “safe and reversible” (not a full reset):
• Storage clue: If your phone is close to full, freeing a little space can reduce app crashes and stuck processing — it doesn’t guarantee anything, but it removes a common failure point.

• Integrity clue: The fact it loops back to start suggests Instagram isn’t receiving/accepting the final verification response, or it’s rejecting the submission silently due to quality/risk signals.

If you want the “most likely causes” list based on your exact story (school login + VPN + repeated tries + spinner), it’s usually one of these:
1) temporary verification cooldown (rate limit after many submissions)
2) unstable route (VPN/school network history) causing the flow to fail on response
3) device resource constraints (low storage, background restrictions)
4) account risk signals (new device login, third-party access history)

One last detail: is your Instagram connected to an email/phone you still control right now, or is that uncertain?

That’s actually good news: controlling your email/phone means you have “proof of continuity,” even if the app is forcing identity verification right now.

For now, the safest play is: reduce variables and avoid repeated submissions. If you do one attempt, do it clean (good light, steady, no VPN, stable connection), then give it time instead of hammering the button. The goal is to stop feeding the rate limiter and gather signals about whether it’s a submission problem or a security challenge hold.

If you keep a quick note of: the exact message shown, the network used, whether it loops instantly vs after upload, and whether “Try again later” appears, you’ll have a clear diagnosis path without risky changes.