#general

got cryptic invite from my manager together with my dev and QA colleagues from NA region for tomorrow. so may be this was my last post with totals. will keep you posted.

Looks like I survived for now, unfortunately most of my team mates didn't... Everything is hush hush. Unlike NA, where access is cut immediately and layoff is with no notice, it looks locations in Pacific regions got a separate process like couple of weeks going back and forward (depends on the country) and people not just kept on payroll, but have full access, including Slack.

So #general stats will catch up for Pacific with couple of weeks delay. I will continue daily Slack totals updates.

at the moment, they stopped disconnecting people immediately from the system (perhaps it was so ruthless just in NA, or they got spooked how easy it is to track it), so #general method is no longer up-to-date

• sep02, 6am UTC: 172796 (0)
• sep03, 7am UTC: 169366 (-3430)
• sep04, 6am UTC: 168958 (-408)
• sep05, 6am UTC: 168771 (-187)
• sep05, 1pm UTC: 168824 (+53 new people were onboarded?)
• sep06, 7am UTC: 168579 (-245 in comparison to previous 168824)
• sep08, 7am UTC: 168566 (-13)
• sep08, 2pm UTC: 168759 (+193 new people were onboarded?)
• sep09, 6am UTC: 168672 (-87 in comparison to previous 168759)
• sep09, 1pm UTC: 168705 (+33 new people were onboarded?)
• sep10, 5:30am UTC: 168627 (-78 in comparison to previous 168705)
• sep10, 1pm UTC: 168624

Methodology:
Tracking participants count #general Slack channel in Oracle One workspace

• sep02, 6am UTC: 172796 (0)
• sep03, 7am UTC: 169366 (-3430)
• sep04, 6am UTC: 168958 (-408)
• sep05, 6am UTC: 168771 (-187)
• sep05, 1pm UTC: 168824 (+53 new people were onboarded?)
• sep06, 7am UTC: 168579 (-245 in comparison to previous 168824)
• sep08, 7am UTC: 168566 (-13)
• sep08, 2pm UTC: 168759 (+193 new people were onboarded?)
• sep09, 6am UTC: 168672 (-87 in comparison to previous 168759)
• sep09, 1pm UTC: 168705 (+33 new people were onboarded?)
• sep10, 5:30am UTC: 168627 (-78 in comparison to previous 168705)

Methodology:
Tracking participants count #general Slack channel in Oracle One workspace

• sep02, 6am UTC: 172796 (0)
• sep03, 7am UTC: 169366 (-3430)
• sep04, 6am UTC: 168958 (-408)
• sep05, 6am UTC: 168771 (-187)
• sep05, 1pm UTC: 168824 (+53 new people were onboarded?)
• sep06, 7am UTC: 168579 (-245 in comparison to previous 168824)
• sep08, 7am UTC: 168566 (-13)
• sep08, 2pm UTC: 168759 (+193 new people were onboarded?)
• sep09, 6am UTC: 168672 (-87 in comparison to previous 168759)

it's not done manually by HR, it's should be at least semi automated onboarding hitting Slack API: https://docs.slack.dev/

and according that API, a worker has to login manually through browser to complete OAuth2 flow to join the Oracle corporate Slack workspaces, HR won't be able to do it for you.

It's an interesting question when do you join #general. From tests I ran on non-enterprise Slack version, you join workspace #general upon joining the workspace after the login. I wonder if enterprise version got some pre-boarding with batch processing, as I see spikes of joins of many dozen people at once outside of normal hours for Europe and America and I doubt it's New Zealand suddenly mass hiring this month.

How are you checking additions ?
I monitor the same #general regularly, if there is count increase - I count it as onboarding additions. I cannot catch all of them (only when balance goes into positive territory), but at least some.

Methodology:
Tracking participants count #general Slack channel in Oracle One workspace

• sep02, 6am UTC: 172796 (0)
• sep03, 7am UTC: 169366 (-3430)
• sep04, 6am UTC: 168958 (-408)
• sep05, 6am UTC: 168771 (-187)
• sep05, 1pm UTC: 168824 (+53 looks like bunch of people were onboarded)
• sep06, 7am UTC: 168579 (-245 and -53 additions discounted = -298)
• sep08, 7am UTC: 168566 (-13)

could naysayers post a table or chart supporting their claims?

September totals (except Sep01): 4323 layoffs, and 53 additions.

Methodology:
Tracking participants count #general Slack channel in Oracle One workspace

• sep02, 6am UTC: 172796 (0)
• sep03, 7am UTC: 169366 (-3430)
• sep04, 6am UTC: 168958 (-408)
• sep05, 6am UTC: 168771 (-187)
• sep05, 1pm UTC: 168824 (+53 looks like bunch of people were onboarded)
• sep06, 7am UTC: 168579 (-245 and -53 additions discounted = -298)

Can you provide ANY source to your claims about 17k or 10k or anything significantly higher than 4.5k just for September?

Slack #general mentions about 10,000 reductions and still decreasing. I think the poster might be right.

no. I track Slack #general daily. September total is 4323 so far. Cross check against Oracle news channel is about the same.

Slack #general mentions about 10,000 reductions and still decreasing. I think the poster might be right.

Methodology:
Tracking participants count #general Slack channel in Oracle One workspace

• sep02, 6am UTC: 172796 (0)
• sep03, 7am UTC: 169366 (-3430)
• sep04, 6am UTC: 168958 (-408)
• sep05, 6am UTC: 168771 (-187)
• sep05, 1pm UTC: 168824 (+53 looks like bunch of people were onboarded)
• sep06, 7am UTC: 168579 (-192 and -53 additions discounted = -245)

#general on Oracle One

• sep02, 6am UTC: 172796 (0)
• sep03, 7am UTC: 169366 (-3430)
• sep04, 6am UTC: 168958 (-408)
• sep05, 6am UTC: 168771 (-187)
• sep05, 1pm UTC: 168824 (+53 looks like bunch of people were onboarded)
• now: 168812 (-12)

Hm, for the past 8h, general count went up in Slack #general on Oracle One workspace from 168771 on 6am UTC to 168824 (+53 added back) now. I wonder if access was restored in some location, or more likely some company was acquired before or now and their employees got integrated. Or something else. I hope admins didn't catchup to the fact how easy is to track through Slack and didn't start messing up with this metric for obfuscation purposes.

Anyway, I will discount these 53 to avoid messing up with layoff totals starting from tonight totals. However, it means I lost layoffs between 6am UTC to 1pm UTC on September 05, which is Asia and Pacific.

Numbers as of this post.
Total # under Larry and Saffra per Aria. This # should include all that were notified and given an end date of Sep 22, Oct 3, etc. = 177,930
Total # in Slack #General, Should represent all active employees, ie this would not include those that have had access revoked. = 168,872

177,930 - 168,872 = 9,058

Yes, American timezone layoffs halted at the moment judging by #general Slack channel participants count.

I think they will move to other regions now. However, there's a good chance it will return back before October, as CX former Rob's org which recently folded under Fusion Chris's org was not touched yet, which looks very suspicious. It was expected to be trimmed the most due to redundancies. On the other hand, Rob was purging CX for years, may be not much meat left.

@c8 apologies. #general shows 168,893 as of Sept 4

@c7 in slack #general now is at 169,089

Down from 169,217 earlier.

64,259 employees under Larry
113,742 under Safra
Total in ARIA of 178,001
Believe ARIA includes contractors

169,217 in #general

1.50am UK Time 4th Sep

#general Oracle One had 161k in March 2023. It was 178k on 8/28/25 and now at 169k

68 laid off for the past 1.5h, which is just east coast

Tracking is easy with writing down participants count in #general slack channel, as it reflects loss of access and is the best real-time approximation available.

September 2nd night started with 172796, now it's 169220

If anyone within Oracle doesn't mind having a look at Oracle One #general slack channel and giving us a membership count...yesterday it seems like about 4,000 were impacted. We appreciate it.

• 68 for the past 1.5h in #general, it's slower pace than yesterday, but it's just east coast being hit. We will see in few hours.

@a6 Easiest to just track the members in the #general slack channel. It was well over 172K yesterday am, and is now down to 169K

If they disappear from Slack, it's a sure indicator they lost access. Everyone is automatically subscribed to #general Slack channel and nobody bothers to leave it, so it's the best approximator of layoffs with immediate loss of access. It's very unlikely those are catchup disconnects from 2 weeks back.

yes tracking members of #general is the way to go
#watercooler numbers can go up or down as other slack orgs add the channel for people to announce they are gone!

@ab #general is at 169269 right now

3430 for the past 24 hours based on #general participants count change

#general started from 172796 starting today.

So far 3k jobs were lost today alone

The best way is via the #general channel which was about 172k a few hours ago and now it's under 170k.

#general oracle one had 173k and now 169k

@b4 Which channel? Definitely wasn't #all-company or #general. I tried searching but came up empty.