Sep24 6am UTC - Sep25 6am UTC totals: 80 layoffs, 9 additions.
September totals (except Sep01): 5635 layoffs, and 825 additions.
Methodology and day-by-day breakdown is in comments.
I know a dev team in Pacific, which had the last day yesterday, but they are still in Slack and it is unclear why O stopped cutting access to some people. Maybe it was too easy to track layoffs. Therefore, these totals are the floor estimate.
Sep29 2pm UTC - Sep30 1pm UTC totals: 49 layoffs.
September totals (except Sep01): 5807 layoffs, and 861 additions.
Sep26 5am UTC - Sep29 2pm UTC totals: 82 layoffs.
September totals (except Sep01): 5758 layoffs, and 861 additions.
Sep25 6am UTC - Sep26 6am UTC totals: 41 layoffs, 36 additions.
September totals (except Sep01): 5676 layoffs, and 861 additions.
To answer your "access cut off" question - some territories have particular requirements for employee access. In many places, management/HR are not allowed to cut access to any service that the employee may have had while fully employed until the very last day.
So, as the actual last day (usually 30-60 days out) comes up, you'll see many more dropping out of slack and so on. This is purely a legal thing.
@b1 20% across all departments? How many heads were in Mexico pre cuts?
I'm sure this is definitely being looked at and some of the account inactivations will be protracted, but this is a valuable exercise, thank you for doing it.
Oracle Mexico just had a 20 percent cut yesterday
Methodology:
Tracking participants count #general Slack channel in Oracle One workspace