#general

Posts mentioning hashtag #general

Below are all the posts — topics as well as replies — that mention the hashtag #general.

Mention #general in your post to continue the discussion!

Limitations: to answer a common question what exactly is counted here and how:

Every few hours I manually record Slack total participants count in #general Slack channel of Oracle One workspace - that's where all Oracle employees onboarded into corporate Slack account auto-join.

If count increases since the previous check - I add it to "additions" totals, if count decreases - I add it to "layoffs" totals. Obviously, additions and reductions may happen at the same time and cancel each other out. The higher frequency of sampling - the more additions and reductions are caught.

"Layoffs" is just a caught reduction number, and partially includes normal attrition when people quit on their own. However, a lot of reductions are canceled out due to frequency of sampling, so normal attrition often is already at least partially not part of the count.

Obviously this metric is far from ideal and mostly should be used as a trend indicator. It's especially less accurate (has more delay) in EU and Pacific regions, where employees are disconnected from Slack with long delay. However, it reflects the same day layoffs in NA and IDC usually.

As a historical comparison of daily stats:
September 2025: high intensity mass layoff, especially first few days
February 2026: no mass layoffs, normal attrition month to use as a baseline

Layoff running totals based on Slack

Tracking participants count #general Slack channel in Oracle One workspace, as the fastest available proxy indication of ongoing layoffs.

  • mar01-mar31: 12446 layoffs, and 844 additions (based on Slack regular tracking)
  • feb01-feb28: 943 layoffs, and 1143 additions (based on Slack regular tracking)
  • jan01-jan31: 1604 layoffs, and 1834 additions (based on Slack regular tracking)
  • dec01-dec31: 1031 layoffs, and 844 additions (based on Slack regular tracking)
  • nov01-nov30: 1614 layoffs, and 1327 additions (based on Slack regular tracking)
  • oct01-oct31: 2504 layoffs, 1762 additions (based on Slack regular tracking)
  • sep02-sep30: 6275 layoffs, 861 additions (based on Slack regular tracking)
  • aug14-sep01: 733 layoffs (based on Slack very few data points)
  • aug01-aug14: ?2900 layoffs in IDC (based on media reports)

Regions outside IDC and NA usually have a significant delay when laid off people are disconnected from Slack (e.g. 1 month in Pacific regions, perhaps longer in some EU countries), so this is a floor estimate with additions reflected immediately, but reductions lagging behind on average.

What is called "layoff estimates" are partially part of normal attrition, limitations are covered in details in comments.

I will post daily in comments on the count change and running current month total while this post is still on the first page.

#Attrition #EmployeeTurnover #Layoff #Layoffs

no

Slack #general totals in Oracle One Slack workspace

  • mar23, 6:30pm UTC: 166540 (-3)
  • mar24, 1am UTC: 166542 (+2)
  • mar24, 1:30pm UTC: 166434 (-108)
  • mar24, 10:30pm UTC: 166432 (-2)
  • mar25, 1pm UTC: 166343 (-89)
  • mar25, 3pm UTC: 166325 (-18)
  • mar25, 8:30pm UTC: 166092 (-233)
  • mar25, 9pm UTC: 166072 (-20)
  • mar25, 11pm UTC: 165995 (-77)
  • mar26, 1pm UTC: 165865 (-130)
  • mar26, 6:30pm UTC: 165800 (-65)
  • mar27, 3:30am UTC: 165707 (-93)
  • mar27, 2pm UTC: 165736 (+29)
  • mar27, 8pm UTC: 165723 (-13)
  • mar28, 2:30pm UTC: 165526 (-197)
  • mar30, 12:30pm UTC: 165614 (+88)
  • mar30, 4pm UTC: 165589 (-25)
  • mar30, 9:30pm UTC: 165333 (-256)
  • mar31, 2am UTC: 165228 (-105)
  • mar31, 5am UTC: 165198 (-30)
  • mar31, 12:30pm UTC: 155607 (-9591)
  • mar31, 6pm UTC: 155594 (-13)
  • mar31, 9:30pm UTC: 155604 (+10)
  • apr01, 2:30am UTC: 154796 (-808)

@q4 there are also some more targeted #general channels that can be used for the same calculations. for example #general in the "Oracle Health" workspace, which seems to have users from appropriate orgs added automatically.

this round stats on #general on Oracle One workspace:

  • mar23, 6:30pm UTC: 166540 (-3)
  • mar24, 1am UTC: 166542 (+2)
  • mar24, 1:30pm UTC: 166434 (-108)
  • mar24, 10:30pm UTC: 166432 (-2)
  • mar25, 1pm UTC: 166343 (-89)
  • mar25, 3pm UTC: 166325 (-18)
  • mar25, 8:30pm UTC: 166092 (-233)
  • mar25, 9pm UTC: 166072 (-20)
  • mar25, 11pm UTC: 165995 (-77)
  • mar26, 1pm UTC: 165865 (-130)
  • mar26, 6:30pm UTC: 165800 (-65)
  • mar27, 3:30am UTC: 165707 (-93)
  • mar27, 2pm UTC: 165736 (+29)
  • mar27, 8pm UTC: 165723 (-13)
  • mar28, 2:30pm UTC: 165526 (-197)
  • mar30, 12:30pm UTC: 165614 (+88)
  • mar30, 4pm UTC: 165589 (-25)
  • mar30, 9:30pm UTC: 165333 (-256)
  • mar31, 2am UTC: 165228 (-105)
  • mar31, 5am UTC: 165198 (-30)
  • mar31, 12:30pm UTC: 155607 (-9591)

the largest single day drop previously was on September 02, 2025, when 3.4k dropped within 24h.
and NA timezone hasn't even started yet.

They cannot shut down #general on Oracle One Slack workspace, that is a default workspace channel every new account auto joina. You can create your own Slack workspace against you personal email and verify that's how Slack works

To answer a common question what exactly is counted here and how:

Every few hours I manually record Slack total participants count in #general Slack channel of Oracle One workspace - that's where all Oracle employees onboarded into corporate Slack account auto-join.

If count increases since the previous check - I add it to "additions" totals, if count decreases - I add it to "layoffs" totals. Obviously, additions and reductions may happen at the same time and cancel each other out. The higher frequency of sampling - the more additions and reductions are caught.

"Layoffs" is just a caught reduction number, and partially includes normal attrition when people quit on their own. However, a lot of reductions are canceled out due to frequency of sampling, so normal attrition often is already at least partially not part of the count.

Obviously this metric is far from ideal and mostly should be used as a trend indicator. It's especially less accurate (has more delay) in EU and Pacific regions, where employees are disconnected from Slack with long delay. However, it reflects the same day layoffs in NA and IDC usually.

As a historical comparison of daily stats:
September 2025: high intensity mass layoff, especially first few days
February 2026: no mass layoffs, normal attrition month to use as a baseline

Layoff running totals based on Slack

Tracking participants count #general Slack channel in Oracle One workspace, as the fastest available proxy indication of ongoing layoffs.

This round of mass layoff started on Mar24-25 according to Slack totals and it's sustained. I have to start a new thread, because our resident troll started counterfeiting Slack totals and trends again on the first page.

  • mar01-mar28: 1618 layoffs, and 746 additions (based on Slack regular tracking)
  • feb01-feb28: 943 layoffs, and 1143 additions (based on Slack regular tracking)
  • jan01-jan31: 1604 layoffs, and 1834 additions (based on Slack regular tracking)
  • dec01-dec31: 1031 layoffs, and 844 additions (based on Slack regular tracking)
  • nov01-nov30: 1614 layoffs, and 1327 additions (based on Slack regular tracking)
  • oct01-oct31: 2504 layoffs, 1762 additions (based on Slack regular tracking)
  • sep02-sep30: 6275 layoffs, 861 additions (based on Slack regular tracking)
  • aug14-sep01: 733 layoffs (based on Slack very few data points)
  • aug01-aug14: ?2900 layoffs in IDC (based on media reports)

Regions outside IDC and NA usually have a significant delay when laid off people are disconnected from Slack (e.g. 1 month in Pacific regions, perhaps longer in some EU countries), so this is a floor estimate with additions reflected immediately, but reductions lagging behind on average.

Layoff estimates are partially part of normal attrition, but the other part of normal attrition is already hidden due to additions and removals compensate each other when they happen at the same period of time. Strictly speaking what is called "layoffs" here are just "reductions" in totals.

I will post daily in comments on the count change and running current month total while this post is still on the first page.

#Attrition #Slack #Trends

Minimum $700m / 12,000 to go in Q4

#general will be below 155,000 by 31st May

There was $700m left in the restructuring fund at the end of Q3 and it wasn't enough, so they added $500m more.

All you can be sure is it will happen in the next 9 weeks.

I'm coming on like a hurricane
My lightning's flashing across the sky
You're only young, but you're gonna die

I won't take no prisoners, won't spare no lives
Nobody's putting up a fight
I've got my bell, I'm gonna take you to he-l
I'm gonna get ya, said I'll get ya

He-l's bells........

#Layoffs #Restructuring #Rumor #NextLayoff

@a6 just stop lying
mass layoffs indeed started today, and dropped 471 past 2.5 days (360 past 23h),

#general Slack count in Oracle One workspace:

  • mar23, 2:30pm UTC: 166543
  • mar23, 6:30pm UTC: 166540 (-3)
  • mar24, 1am UTC: 166542 (+2)
  • mar24, 1:30pm UTC: 166434 (-108)
  • mar24, 10:30pm UTC: 166432 (-2)
  • mar25, 1pm UTC: 166343 (-89)
  • mar25, 3pm UTC: 166325 (-18)
  • mar25, 8:30pm UTC: 166092 (-233)
  • mar25, 9pm UTC: 166072 (-20)

yes, mass layoff started today
methodology, tracking total headcount in #general Slack channel of Oracle One workspace:

  • mar24, 10:30pm UTC: 166432 (-2)
  • mar25, 1pm UTC: 166343 (-89)
  • mar25, 3pm UTC: 166325 (-18)
  • mar25, 8:30pm UTC: 166092 (-233)
  • mar25, 9pm UTC: 166072 (-20)

It has not dropped 2,000 in the past 2 days. I've been tracking since 3/10. at it's peak this month #general in OO had 166,554. As of today it's 166,220. So it's dropped 334 and climbing.

IDC disconnects from Slack right away, and here are Slack total stats for #general in Oracle One workspace across the company:

  • mar23, 2:30pm UTC: 166543 (+257)
  • mar23, 6:30pm UTC: 166540 (-3)
  • mar24, 1am UTC: 166542 (+2)
  • mar24, 1:30pm UTC: 166434 (-108)

looks so far as part of normal deviation, no mass layoff happened in IDC past two days.

Layoff running totals based on Slack

Tracking participants count #general Slack channel in Oracle One workspace, as the fastest available proxy indication of ongoing layoffs.

  • mar01-mar23: 573 layoffs, and 715 additions (based on Slack regular tracking)
  • feb01-feb28: 943 layoffs, and 1143 additions (based on Slack regular tracking)
  • jan01-jan31: 1604 layoffs, and 1834 additions (based on Slack regular tracking)
  • dec01-dec31: 1031 layoffs, and 844 additions (based on Slack regular tracking)
  • nov01-nov30: 1614 layoffs, and 1327 additions (based on Slack regular tracking)
  • oct01-oct31: 2504 layoffs, 1762 additions (based on Slack regular tracking)
  • sep02-sep30: 6275 layoffs, 861 additions (based on Slack regular tracking)
  • aug14-sep01: 733 layoffs (based on Slack very few data points)
  • aug01-aug14: ?2900 layoffs in IDC (based on media reports)

Regions outside IDC and NA usually have a significant delay when laid off people are disconnected from Slack (e.g. 1 month in Pacific regions, perhaps longer in some EU countries), so this is a floor estimate with additions reflected immediately, but reductions lagging behind on average.

Layoff estimates are partially part of normal attrition, but the other part of normal attrition is already hidden due to additions and removals compensate each other when they happen at the same period of time.

I will post daily in comments (if admin stops deleting my posts and comments) on the count change and running current month total while this post is still on the first page.

#Layoffs #Metrics

@ad That is not the point. Nobody thinks layoffs aren't happening.

The point is it's not started yet. In #general there are 15 more people in comparison to yesterday and 7 more in comparison to 2 days ago.

Despite this 45k in one go may be way too much.

Assuming that layoff happened, it may be an unrelated layoff from the mass layoffs. And a lot of other comments may be the trolls that have been pestering it here.

The #general channel barely changed from Yesterday to Today.

I see 6 less people from Yesterday in #general

  • Yesterday, 17th of March 166,494 at 6 PM GMT
  • Today, 18 of March, 166,488, at 9 AM GMT

@b6 That stuff USED to be posted to #watercooler, I was seeing a lot of them before I was let go. I was told they deleted that channel a week or so after I got it. Where ELSE is anyone to post about it? Heh, they SHOULD use #general, they're not going to delete that one.

Mar13 2:30am UTC - Mar14 5am UTC totals: 127 layoffs, 1 additions.
March totals: 570 layoffs, and 458 additions.

  • mar13, 12pm UTC: 166413 (+1)
  • mar14, 5am UTC: 166286 (-127)

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

Will be out next week.

Mar13 2:30am UTC - Mar14 5am UTC totals: 127 layoffs, 1 additions.
March totals: 570 layoffs, and 458 additions.

  • mar13, 12pm UTC: 166413 (+1)
  • mar14, 5am UTC: 166286 (-127)

Not sure where my previous post disappeared. Will try again: I will be out till Mar21. Please somebody keep posting sometimes during next week total count on #general Slack channel of Oracle One workspace. Specifically that thread and that workspace.
If "somebody" starts making wild claims on large total swings - please always doublecheck yourself.

Mar13 2:30am UTC - Mar14 5am UTC totals: 127 layoffs, 1 additions.
March totals: 570 layoffs, and 458 additions.

  • mar13, 12pm UTC: 166413 (+1)
  • mar14, 5am UTC: 166286 (-127)

I will be out till Mar21, so I would be very grateful is somebody can sometime post current count on #general of Oracle One Slack workspace.

If somebody starts posting some wild Slack stats, please always check for yourself, and especially keep in mind that was tracking only #general channel totals for Oracle One workspace, not news channel or something, not smaller workspaces. I wouldn't be able to post anything till Mar21 starting now.

@af you are lying troll, there were no layoffs today across the globe

Slack totals of #general participants in Oracle One workspace. They reflect India and North America layoffs pretty much immediately within 30 minutes after RIF call. So as at this moment, all 1-on-1 calls claimed by our mentally re--rded troll already supposed to happen in IDC and NA locations on both coasts. They didn't.

  • mar10, 1:30am UTC: 166361 (-42)
  • mar10, 1pm UTC: 166354 (-7)
  • mar10, 2:30pm UTC: 166354 (0)
  • mar10, 5:30pm UTC: 166354 (0)

Layoff running totals based on Slack

Tracking participants count #general Slack channel in Oracle One workspace, as the fastest available proxy indication of ongoing layoffs.

  • mar01-mar10: 395 layoffs, and 358 additions (based on Slack regular tracking)
  • feb01-feb28: 943 layoffs, and 1143 additions (based on Slack regular tracking)
  • jan01-jan31: 1604 layoffs, and 1834 additions (based on Slack regular tracking)
  • dec01-dec31: 1031 layoffs, and 844 additions (based on Slack regular tracking)
  • nov01-nov30: 1614 layoffs, and 1327 additions (based on Slack regular tracking)
  • oct01-oct31: 2504 layoffs, 1762 additions (based on Slack regular tracking)
  • sep02-sep30: 6275 layoffs, 861 additions (based on Slack regular tracking)
  • aug14-sep01: 733 layoffs (based on Slack very few data points)
  • aug01-aug14: ?2900 layoffs in IDC (based on media reports)

Regions outside IDC and NA usually have a significant delay when laid off people are disconnected from Slack (e.g. 1 month in Pacific regions, perhaps longer in some EU countries), so this is a floor estimate with additions reflected immediately, but reductions lagging behind on average.

Layoff estimates are partially part of normal attrition, but the other part of normal attrition is already hidden due to additions and removals compensate each other when they happen at the same period of time.

I will post daily in comments on the count change and running current month total while this post is still on the first page.

#Layoff #Layoffs #Regional

@dc This count always came from #general in Oracle One workspace. That's where you always automatically auto-join when Oracle corporate Slack account is issued to you.

Layoff running totals based on Slack

Tracking participants count #general Slack channel in Oracle One workspace, as the fastest available proxy indication of ongoing layoffs.

  • mar01-mar07: 351 layoffs, and 43 additions (based on Slack regular tracking)
  • feb01-feb28: 943 layoffs, and 1143 additions (based on Slack regular tracking)
  • jan01-jan31: 1604 layoffs, and 1834 additions (based on Slack regular tracking)
  • dec01-dec31: 1031 layoffs, and 844 additions (based on Slack regular tracking)
  • nov01-nov30: 1614 layoffs, and 1327 additions (based on Slack regular tracking)
  • oct01-oct31: 2504 layoffs, 1762 additions (based on Slack regular tracking)
  • sep02-sep30: 6275 layoffs, 861 additions (based on Slack regular tracking)
  • aug14-sep01: 733 layoffs (based on Slack very few data points)
  • aug01-aug14: ?2900 layoffs in IDC (based on media reports)

Regions outside IDC and NA usually have a significant delay when laid off people are disconnected from Slack (e.g. 1 month in Pacific regions, perhaps longer in some EU countries), so this is a floor estimate with additions reflected immediately, but reductions lagging behind on average.

Layoff estimates are partially part of normal attrition, but the other part of normal attrition is already hidden due to additions and removals compensate each other when they happen at the same period of time.

I will post daily in comments on the count change and running current month total while this post is still on the first page.

#Attrition #Slack

@ez
Looks like regular attrition past 2-3 months, in comparison to actual mass lay-offs aug-oct:

History based on Slack #general in Oracle One namespace:

  • feb01-feb28: 943 layoffs, and 1143 additions (based on Slack regular tracking)
  • jan01-jan31: 1604 layoffs, and 1834 additions (based on Slack regular tracking)
  • dec01-dec31: 1031 layoffs, and 844 additions (based on Slack regular tracking)
  • nov01-nov30: 1614 layoffs, and 1327 additions (based on Slack regular tracking)
  • oct01-oct31: 2504 layoffs, 1762 additions (based on Slack regular tracking)
  • sep02-sep30: 6275 layoffs, 861 additions (based on Slack regular tracking)
  • aug14-sep01: 733 layoffs (based on Slack very few data points)
  • aug01-aug14: ?2900 layoffs in IDC (based on media reports)

Layoff running totals based on Slack

Tracking participants count #general Slack channel in Oracle One workspace, as the fastest available proxy indication of ongoing layoffs.

Since our local troll started counterfeiting Slack totals to induce panic on the front page, I have to create this thread not waiting for March.

  • feb01-feb19: 485 layoffs, and 725 additions (based on Slack regular tracking)
  • jan01-jan31: 1604 layoffs, and 1834 additions (based on Slack regular tracking)
  • dec01-dec31: 1031 layoffs, and 844 additions (based on Slack regular tracking)
  • nov01-nov30: 1614 layoffs, and 1327 additions (based on Slack regular tracking)
  • oct01-oct31: 2504 layoffs, 1762 additions (based on Slack regular tracking)
  • sep02-sep30: 6275 layoffs, 861 additions (based on Slack regular tracking)
  • aug14-sep01: 733 layoffs (based on Slack very few data points)
  • aug01-aug14: ?2900 layoffs in IDC (based on media reports)

Regions outside IDC and NA usually have a significant delay when laid off people are disconnected from Slack (e.g. 1 month in Pacific regions, perhaps longer in some EU countries), so this is a floor estimate with additions reflected immediately, but reductions lagging behind on average.

I will post daily in comments on the count change and running current month total while this post is still on the first page.

#Layoff #Layoffs

@cc you go to "Oracle One" Slack workspace, and #general channel. All new people are onboarded into it automatically.

Feb02 3pm UTC - Feb03 4pm UTC totals: 53 layoffs, 39 additions.
February totals: 122 layoffs, and 280 additions.

  • feb03, 2:30am UTC: 166317 (-53)
  • feb03, 4pm UTC: 166356 (+39)

Layoff running totals based on Slack

Tracking participants count #general Slack channel in Oracle One workspace, as the fastest available proxy indication of ongoing layoffs.

  • jan01-jan31: 1604 layoffs, and 1834 additions (based on Slack regular tracking)
  • dec01-dec31: 1031 layoffs, and 844 additions (based on Slack regular tracking)
  • nov01-nov30: 1614 layoffs, and 1327 additions (based on Slack regular tracking)
  • oct01-oct31: 2504 layoffs, 1762 additions (based on Slack regular tracking)
  • sep02-sep30: 6275 layoffs, 861 additions (based on Slack regular tracking)
  • aug14-sep01: 733 layoffs (based on Slack very few data points)
  • aug01-aug14: ?2900 layoffs in IDC (based on media reports)

Regions outside IDC and NA usually have a significant delay when laid off people are disconnected from Slack (e.g. 1 month in Pacific regions, perhaps longer in some EU countries), so this is a floor estimate with additions reflected immediately, but reductions lagging behind on average.

I will post daily in comments on the count change and running current month total while this post is still on the first page.

#EmployeeRelations #Layoff #Layoffs #WorkforceReduction

Layoff running totals based on Slack

Tracking participants count #general Slack channel in Oracle One workspace, as the fastest available proxy indication of ongoing layoffs.

  • dec01-dec31: 1031 layoffs, and 844 additions (based on Slack regular tracking)
  • nov01-nov30: 1614 layoffs, and 1327 additions (based on Slack regular tracking)
  • oct01-oct31: 2504 layoffs, 1762 additions (based on Slack regular tracking)
  • sep02-sep30: 6275 layoffs, 861 additions (based on Slack regular tracking)
  • aug14-sep01: 733 layoffs (based on Slack very few data points)
  • aug01-aug14: ?2900 layoffs in IDC (based on media reports)

Regions outside IDC and NA usually have a significant delay when laid off people are disconnected from Slack (e.g. 1 month in Pacific regions, perhaps longer in some EU countries), so this is a floor estimate with additions reflected immediately, but reductions lagging behind on average.

I will post daily in comments on the count change and running current month total while this post is still on the first page.

P.S. Happy New Year!

#Layoffs #Slack

@OP And yet they have a ton of openings posted on their web site.

I know there is a freeze in some organizations (manager friends have told me when I asked if they had openings), they ARE hiring in others. The person who posts headcount changes here based on Slack's #general membership shows headcount deleted and headcount added.

All this makes me wonder how much longer O is even going to be around.

Layoff running totals based on Slack

Tracking participants count #general Slack channel in Oracle One workspace, as the fastest available proxy indication of ongoing layoffs.

  • nov01-nov30: 1614 layoffs, 1327 additions (based on Slack regular tracking)
  • oct01-oct29: 1950 layoffs, 1689 additions (based on Slack regular tracking)
  • sep02-sep30: 6275 layoffs, 861 additions (based on Slack regular tracking)
  • aug14-sep01: 733 layoffs (based on Slack very few data points)
  • aug01-aug14: ?2900 layoffs in IDC (based on media reports, no public info about other locations available)

Regions outside IDC and NA usually have a significant delay when laid off people are disconnected from Slack (e.g. 1 month in Pacific regions, perhaps longer in some EU countries), so this is a floor estimate with additions reflected immediately, but reductions lagging behind on average.

I will post daily in comments on the count change and running current month total while this post is still on the first page.

#Slack #Updates #Layoff #Layoffs

I think they're replacing everyone. They seem to be hiring almost as fast as they are laying off, judging from the #general slack numbers being posted.

Exactly. They are loading up for the next RIF.

@aw I think they're replacing everyone. They seem to be hiring almost as fast as they are laying off, judging from the #general slack numbers being posted.