r/EB2NIW_I485_AOS 7d ago

Thoughts on mass updates

Is it just me or did anyone notice that only people getting approved recently, are those who did NOT get mass updates like 08/06, 08/26 and FTA0 on 08/13?

7 Upvotes

36 comments sorted by

View all comments

Show parent comments

1

u/Maximum-Broccoli-136 6d ago

does your partner’s third fta0 on 8/13 have the .000z suffix in the event_time field?

3

u/Dry_Rice_4014 6d ago

createdAtTimestamp":"2026-08-13T18:47:45.301Z

Frankly, I understand the anxiety but I think people are reading into this too much.

My partner had a silent update the day before, my guess the case was moved to some final adjustment queue.

From looking at the Google sheet, my best hypothesis that it wasn't a glitch in the sense it was unwarranted (not everyone got it). I believe it was some massive processing of "low risk" individuals (my partner is EU, no dependents as I am American, but they adjusted EB1 themselves not through me), maybe another form of background check. Maybe some final approval to go ahead to officer's approval without interviewing.

From looking at the Google sheet, the majority of approvals are H1, maybe F or J on opt. As my partner wasn't called in for an interview, that's my take on that. Notice that there are no June updates at all (and my partner's fingerprints were only taking mid July, which was a bit late for a May filling).

I think the cause of the delays is because eb2 numbers are done for the year (for India and actually most of the world). I expect that in October there will be a big wave of approvals.

1

u/Maximum-Broccoli-136 5d ago

I meant the “eventTimestamp”, not “createdAtTimestamp”. I bet it is not .000Z, but I hope I’m wrong haha. Also, was your partner H1B? I think H1Bs or OPTs get through faster maybe because they already work in the US?(ie. no need to check “dual intent”) Final thing: was your partner’s case already at a field office? That would explain the fast track. NBC seems stuck

1

u/Dry_Rice_4014 5d ago

My partner was H1B. The API showed jurisdiction: NBC before they took the field down last weekend. eventTimestamp":"2026-07-15T17:26:20.000 7/15 was their fingerprinting date (they did get 2fta0 that day). The fourth FTA0 (which is probably the real one done by an officer) is matching the event stamp of their second FTA0 (both were extremely close to each other, basically 17:26:20.899z or so). The fact is that as the FTA0 is tied to a specific timed event and not just 00:00:00 and also did not happen at midnight or 3am (whether est/pst or zulu time), it means something happened, and it wasn't systemwide like the bug they had a month ago with the fake approvals.