Thread regarding Oracle Corp. layoffs

Layoff running totals based on Slack - Nov 2026

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

FY 2027

  • oct01-oct31: 2270 reductions, 785 additions, 142827 (-1485) end count
  • sep02-sep30: 7022 reductions, 1137 additions, 144312 (-5885) end count
  • aug01-sep01: 1899 reductions, 995 additions, 150197 (-904) end count
  • jul01-jul31: 2975 reductions, 1736 additions, 151101 (-1239) end count
  • jun01-jun30: 1723 reductions, 1299 additions, 152340 (-424) end count

FY 2026

  • may01-may31: 2271 reductions, 942 additions, 152764 (-1329) end count
  • apr01-apr30: 2286 reductions, 1583 additions, 154093 (-703) end count
  • mar01-mar31: 12446 reductions, 844 additions, 154796 (-11602) end count
  • feb01-feb28: 943 reductions, 1143 additions, 166398 (+200) end count
  • jan01-jan31: 1604 reductions, 1834 additions, 166198 (+230) end count
  • dec01-dec31: 1119 reductions, 844 additions, 165968 (-275) end count
  • nov01-nov30: 1614 reductions, 1310 additions, 166243 (-304) end count
  • oct01-oct31: 2498 reductions, 1768 additions, 166547 (-730) end count
  • sep02-sep30: 6380 reductions, 861 additions, 167277 (-5519) end count
  • aug14-sep01: 733 reductions (based on Slack very few data points), 172796 (-733) end count
  • aug01-aug14: ?2900 reductions in IDC (based on media reports), 173529 (-2900) end count

Limitations of these stats are covered in detail in comments.
I will post daily in comments on the count change and running current month total.

My public key used to prove identity: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats


by
| 529 views | | 21 replies (last 10 hours ago) | Reply
Post ID: @OP+1m6c1wrrj

21 replies (most recent on top)

Slack stats Oracle One #general

November 11, 1pm UTC - November 12, 1pm UTC totals: 13 reductions, 15 additions.
November totals: 1019 reductions, and 493 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)
  • nov02, 5:30am UTC: 142635 (-21)
  • nov02, 1pm UTC: 142802 (+167)
  • nov03, 2am UTC: 142631 (-171)
  • nov03, 1pm UTC: 142637 (+6)
  • nov04, 2am UTC: 142558 (-79)
  • nov04, 1pm UTC: 142571 (+13)
  • nov05, 3am UTC: 142473 (-98)
  • nov05, 1pm UTC: 142506 (+33)
  • nov06, 3am UTC: 142434 (-72)
  • nov06, 1pm UTC: 142438 (+4)
  • nov07, 4am UTC: 142269 (-169)
  • nov07, 7:30pm UTC: 142317 (+48)
  • nov08, 9pm UTC: 142259 (-58)
  • nov09, 7am UTC: 142295 (+36)
  • nov09, 1pm UTC: 142385 (+90)
  • nov10, 3am UTC: 142328 (-57)
  • nov10, 1pm UTC: 142341 (+13)
  • nov11, 2am UTC: 142296 (-45)
  • nov11, 1pm UTC: 142299 (+3)
  • nov12, 12am UTC: 142286 (-13)
  • nov12, 1pm UTC: 142301 (+15)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November12-2026;msg16;thread(1m6c1wrrj);Count(142301);RunningTotals(-1019/+493);DailyTotals(-13/+15);Breakdown(-13,+15):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEDl1tvDcnHvNZNTLpQFQE1weuiGgsCgSBGjOUeV83oTOWVUg7muBCIuAjYBKryzjAIkzB4JsSVvY5DLkkQEbTgH
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @1tp+1m6c1wrrj

Slack stats Oracle One #general

November 10, 1pm UTC - November 11, 1pm UTC totals: 45 reductions, 3 additions.
November totals: 1006 reductions, and 478 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)
  • nov02, 5:30am UTC: 142635 (-21)
  • nov02, 1pm UTC: 142802 (+167)
  • nov03, 2am UTC: 142631 (-171)
  • nov03, 1pm UTC: 142637 (+6)
  • nov04, 2am UTC: 142558 (-79)
  • nov04, 1pm UTC: 142571 (+13)
  • nov05, 3am UTC: 142473 (-98)
  • nov05, 1pm UTC: 142506 (+33)
  • nov06, 3am UTC: 142434 (-72)
  • nov06, 1pm UTC: 142438 (+4)
  • nov07, 4am UTC: 142269 (-169)
  • nov07, 7:30pm UTC: 142317 (+48)
  • nov08, 9pm UTC: 142259 (-58)
  • nov09, 7am UTC: 142295 (+36)
  • nov09, 1pm UTC: 142385 (+90)
  • nov10, 3am UTC: 142328 (-57)
  • nov10, 1pm UTC: 142341 (+13)
  • nov11, 2am UTC: 142296 (-45)
  • nov11, 1pm UTC: 142299 (+3)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November11-2026;msg15;thread(1m6c1wrrj);Count(142299);RunningTotals(-1006/+478);DailyTotals(-45/+3);Breakdown(-45,+3):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAECp6ujFTvBg2ttu3db26np9Y62+Rf9GwIHIOo4pgll0gZTZUAecqfSeH+xYrhb0+Zx/oqBRqddOYb/h/0VOnxgJ
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @1p7+1m6c1wrrj

Slack stats Oracle One #general

November 09, 1pm UTC - November 10, 1pm UTC totals: 57 reductions, 13 additions.
November totals: 961 reductions, and 475 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)
  • nov02, 5:30am UTC: 142635 (-21)
  • nov02, 1pm UTC: 142802 (+167)
  • nov03, 2am UTC: 142631 (-171)
  • nov03, 1pm UTC: 142637 (+6)
  • nov04, 2am UTC: 142558 (-79)
  • nov04, 1pm UTC: 142571 (+13)
  • nov05, 3am UTC: 142473 (-98)
  • nov05, 1pm UTC: 142506 (+33)
  • nov06, 3am UTC: 142434 (-72)
  • nov06, 1pm UTC: 142438 (+4)
  • nov07, 4am UTC: 142269 (-169)
  • nov07, 7:30pm UTC: 142317 (+48)
  • nov08, 9pm UTC: 142259 (-58)
  • nov09, 7am UTC: 142295 (+36)
  • nov09, 1pm UTC: 142385 (+90)
  • nov10, 3am UTC: 142328 (-57)
  • nov10, 1pm UTC: 142341 (+13)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November10-2026;msg14;thread(1m6c1wrrj);Count(142341);RunningTotals(-961/+475);DailyTotals(-57/+13);Breakdown(-57,+13):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEALpb8Ekkokx5SWRM3m0vEPl3DBmauN7cS5RcXSWVffyTtsD9GuZkDOF6hCXE0Njg2s51w6473endPF7frJC+IA
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @1hp+1m6c1wrrj

Slack stats Oracle One #general

November 08, 9pm UTC - November 09, 1pm UTC totals: 0 reductions, 126 additions.
November totals: 904 reductions, and 462 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)
  • nov02, 5:30am UTC: 142635 (-21)
  • nov02, 1pm UTC: 142802 (+167)
  • nov03, 2am UTC: 142631 (-171)
  • nov03, 1pm UTC: 142637 (+6)
  • nov04, 2am UTC: 142558 (-79)
  • nov04, 1pm UTC: 142571 (+13)
  • nov05, 3am UTC: 142473 (-98)
  • nov05, 1pm UTC: 142506 (+33)
  • nov06, 3am UTC: 142434 (-72)
  • nov06, 1pm UTC: 142438 (+4)
  • nov07, 4am UTC: 142269 (-169)
  • nov07, 7:30pm UTC: 142317 (+48)
  • nov08, 9pm UTC: 142259 (-58)
  • nov09, 7am UTC: 142295 (+36)
  • nov09, 1pm UTC: 142385 (+90)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November09-2026;msg13;thread(1m6c1wrrj);Count(142385);RunningTotals(-904/+462);DailyTotals(-0/+126);Breakdown(+36,+90):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEDjolwXpMRmFK+co4TywI/UNFhgODeUcLqycbx82QswgEpNjMq6uPAg6aY73mCfiuHGuQuFSUlBBjYDJvzn5yEH
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @1d6+1m6c1wrrj

Slack stats Oracle One #general

November 06, 1pm UTC - November 08, 9pm UTC totals: 227 reductions, 48 additions.
November totals: 904 reductions, and 336 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)
  • nov02, 5:30am UTC: 142635 (-21)
  • nov02, 1pm UTC: 142802 (+167)
  • nov03, 2am UTC: 142631 (-171)
  • nov03, 1pm UTC: 142637 (+6)
  • nov04, 2am UTC: 142558 (-79)
  • nov04, 1pm UTC: 142571 (+13)
  • nov05, 3am UTC: 142473 (-98)
  • nov05, 1pm UTC: 142506 (+33)
  • nov06, 3am UTC: 142434 (-72)
  • nov06, 1pm UTC: 142438 (+4)
  • nov07, 4am UTC: 142269 (-169)
  • nov07, 7:30pm UTC: 142317 (+48)
  • nov08, 9pm UTC: 142259 (-58)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November08-2026;msg12;thread(1m6c1wrrj);Count(142259);RunningTotals(-904/+336);DailyTotals(-227/+48);Breakdown(-169,+48,-58):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAECeD43oeRD/tLi2aif1KFw7tHKlf3aT1vE9j67dThi9nwe34XY9jjEQtWx7/MZHAzMjMSc+IzohdvnwyPOPMNgL
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @1a7+1m6c1wrrj

Slack stats Oracle One #general

November 05, 1pm UTC - November 06, 1pm UTC totals: 72 reductions, 4 additions.
November totals: 677 reductions, and 288 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)
  • nov02, 5:30am UTC: 142635 (-21)
  • nov02, 1pm UTC: 142802 (+167)
  • nov03, 2am UTC: 142631 (-171)
  • nov03, 1pm UTC: 142637 (+6)
  • nov04, 2am UTC: 142558 (-79)
  • nov04, 1pm UTC: 142571 (+13)
  • nov05, 3am UTC: 142473 (-98)
  • nov05, 1pm UTC: 142506 (+33)
  • nov06, 3am UTC: 142434 (-72)
  • nov06, 1pm UTC: 142438 (+4)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November06-2026;msg11;thread(1m6c1wrrj);Count(142438);RunningTotals(-677/+288);DailyTotals(-72/+4);Breakdown(-72,+4):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEDVM5/SQli2xMa2kTaoUutaePzV9JfTYpRE9XXXATTAImpQVkBw9OxgDJn+Yix7a7lRyT2yQZQypSJlihgJYPoO
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @zq+1m6c1wrrj

Slack stats Oracle One #general

November 04, 1pm UTC - November 05, 1pm UTC totals: 98 reductions, 33 additions.
November totals: 605 reductions, and 284 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)
  • nov02, 5:30am UTC: 142635 (-21)
  • nov02, 1pm UTC: 142802 (+167)
  • nov03, 2am UTC: 142631 (-171)
  • nov03, 1pm UTC: 142637 (+6)
  • nov04, 2am UTC: 142558 (-79)
  • nov04, 1pm UTC: 142571 (+13)
  • nov05, 3am UTC: 142473 (-98)
  • nov05, 1pm UTC: 142506 (+33)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November05-2026;msg10;thread(1m6c1wrrj);Count(142506);RunningTotals(-605/+284);DailyTotals(-98/+33);Breakdown(-98,+33):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEB2P2La/JXuG1nhwYbzUEWZPQSdZRmRYTJ0bYLn4jlx0amNI5iuMMexxxKlzIdt/Tmo3PcvNaS/M9oyX2V4u/MN
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @v8+1m6c1wrrj

@qr country ?

by
| | Reply
Post ID: @r0+1m6c1wrrj

@ps I am in EMEA, was laid off on Tuesday and my Slack is still active. Current count is 142,596

by
| | Reply
Post ID: @qr+1m6c1wrrj

@jt likely mostly delayed disconnects from Europe, Pacific and such, especially at the turn of month, when several hundreds drop every month now.

Slack stats Oracle One #general

November 03, 1pm UTC - November 04, 1pm UTC totals: 79 reductions, 13 additions.
November totals: 507 reductions, and 251 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)
  • nov02, 5:30am UTC: 142635 (-21)
  • nov02, 1pm UTC: 142802 (+167)
  • nov03, 2am UTC: 142631 (-171)
  • nov03, 1pm UTC: 142637 (+6)
  • nov04, 2am UTC: 142558 (-79)
  • nov04. 1pm UTC: 142571 (+13)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November04-2026;msg9;thread(1m6c1wrrj);Count(142571);RunningTotals(-507/+251);DailyTotals(-79/+13);Breakdown(-79,+13):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEDT9wUf5pKlbyOZihBhvklJ+me27rUhoGr8VO9xr1djfcb+spRoU5910fOblC64GXws06sTCRx87SuwtT5KjlIM
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @ps+1m6c1wrrj

@eb It seems that the monthly drop is over 1000 now, and that's without a mass RIF. Not sure how many of these are old EMEA RIFS that finally actualized.

by
| | Reply
Post ID: @jt+1m6c1wrrj

@eb yes, it's ongoing net loss since February.

Slack stats Oracle One #general

November 02, 12pm UTC - November 03, 12pm UTC totals: 171 reductions, 6 additions.
November totals: 428 reductions, and 238 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)
  • nov02, 5:30am UTC: 142635 (-21)
  • nov02, 12pm UTC: 142802 (+167)
  • nov03, 2am UTC: 142631 (-171)
  • nov03, 12pm UTC: 142637 (+6)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November03-2026;msg8;thread(1m6c1wrrj);Count(142637);RunningTotals(-428/+238);DailyTotals(-171/+6);Breakdown(-171,+6):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEAqLSNOUXhYxlJgrW+70LUjcVl1Uhu3oxB7K2naahvskktz+5TdnZZOfyu+4RBY4PmXAUB5xGIRg9vc7qeHwHoL
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @jb+1m6c1wrrj

GOOD JOB

by
| | Reply
Post ID: @f7+1m6c1wrrj

@dp its dropped by another hundred users. Constant small cuts

by
| | Reply
Post ID: @eb+1m6c1wrrj

Slack stats Oracle One #general

November 01, 5pm UTC - November 02, 12pm UTC totals: 21 reductions, 167 additions.
November totals: 257 reductions, and 232 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)
  • nov02, 5:30am UTC: 142635 (-21)
  • nov02, 12pm UTC: 142802 (+167)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November02-2026;msg7;thread(1m6c1wrrj);Count(142802);RunningTotals(-257/+232);DailyTotals(-21/+167);Breakdown(-21,+167):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEAuIR0EbcbvgdzocfOKwdwfbzczjTwEEstF9V9DPdmq6Fq1ZWFb2zL/IjSiS+CVTzvr+2DvVASymdpHStAYGbsM
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @dp+1m6c1wrrj

Slack stats Oracle One #general

October 31, 11:30pm UTC - November 01, 5pm UTC totals: 236 reductions, 65 additions.
November totals: 236 reductions, and 65 additions.

  • oct31, 11:30pm UTC: 142827
  • nov01, 4:30am UTC: 142591 (-236)
  • nov01, 5pm UTC: 142656 (+65)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November01-2026;msg6;thread(1m6c1wrrj);Count(142656);RunningTotals(-236/+65);DailyTotals(-236/+65);Breakdown(-236,+65):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEA4lXrzR+1DJhD1RDMQuInfTh9YqFD+jP/mu3EyqCsRK3CrJps2nqm+tJrEhrX6qMgpYUvtu5err61tv8ffkC8I
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @a6+1m6c1wrrj

Slack stats FY totals

1) FY 2027 (June 1, 2026 through May 31, 2027) running totals

reductions: 15889, additions: 5952, delta: -9937

  • oct01-oct31: 2270 reductions, 785 additions
  • sep02-sep30: 7022 reductions, 1137 additions
  • aug01-sep01: 1899 reductions, 995 additions
  • jul01-jul31: 2975 reductions, 1736 additions
  • jun01-jun30: 1723 reductions, 1299 additions

2) FY 2026 (June 1, 2025 through May 31, 2026) totals
No tracking available for June-July 2025, but we know there were no mass layoffs, which only started early August 2025.

reductions: 34794, additions: 11129, delta: -23665

  • may01-may31: 2271 reductions, 942 additions
  • apr01-apr30: 2286 reductions, 1583 additions
  • mar01-mar31: 12446 reductions, 844 additions
  • feb01-feb28: 943 reductions, 1143 additions
  • jan01-jan31: 1604 reductions, 1834 additions
  • dec01-dec31: 1119 reductions, 844 additions
  • nov01-nov30: 1614 reductions, 1310 additions
  • oct01-oct31: 2498 reductions, 1768 additions
  • sep02-sep30: 6380 reductions, 861 additions
  • aug14-sep01: 733 reductions (based on Slack very few data points)
  • aug01-aug14: ?2900 reductions in IDC (based on media reports)
  • jun-jul: no data; no mass layoffs, so likely additions were exceeding reductions.

Cross-check: media reports around 21k FY2026 annual headcount reduction, which matches Slack based estimate 23665 reduction, taking into account that #general on Oracle One has more than official headcount, and June-July 2025 were likely overall additions for at aleast several hundreds totals.


Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November01-2026;msg5;thread(1m6c1wrrj);FY2027RunningTotals(-15889/+5952/-9937);FY2026(-34794/+11129/-23665):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEDPf6sUtkkgZeMH62G1r6frsS1/vFcAgtT5Ad4848mC4E05VhAFLr8W+XwEB/+Mqwgos53IBc6cV/wHFWs13/oA
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @a5+1m6c1wrrj

Slack stats Latest layoff cycle totals
Slack total for the latest series of mass layoffs which started on Sep14, 2026:

reductions: 8564, additions: 1440, delta: -7124

  • sep14, 2:30am UTC: 149951
  • sep14, 12pm UTC: 146994 (-2957)
  • sep14, 4pm UTC: 146885 (-109)
  • sep14, 8pm UTC: 146649(-236)
  • sep15, 12am UTC: 144698 (-1951)
  • sep15, 2am UTC: 144634 (-64)
  • sep15, 5am UTC: 144616 (-18)
  • sep15, 12pm UTC: 144640 (+24)
  • sep16, 1am UTC: 144592 (-48)
  • sep16, 12pm UTC: 144501 (-91)
  • sep17, 2:30am UTC: 144410 (-91)
  • sep17, 12pm UTC: 144448 (+38)
  • sep18, 1am UTC: 144451 (+3)
  • sep18, 12pm UTC: 144310 (-141)
  • sep19, 2:30am UTC: 144227 (-83)
  • sep19, 3pm UTC: 144201 (-26)
  • sep20, 1am UTC: 144241 (+40)
  • sep20, 9:30pm UTC: 144226 (-15)
  • sep21, 12pm UTC: 144378 (+152)
  • sep22, 12am UTC: 144375 (-3)
  • sep22, 12pm UTC: 144307 (-68)
  • sep23, 12:30am UTC: 144353 (+46)
  • sep23. 12pm UTC: 144324 (-29)
  • sep24, 12:30am UTC: 144394 (+70)
  • sep24, 12pm UTC: 144347 (-47)
  • sep25, 1:30am UTC: 144322 (-25)
  • sep25, 12pm UTC: 144321 (-1)
  • sep26, 6am UTC: 144111 (-210)
  • sep26, 2pm UTC: 144188 (+77)
  • sep27, 4am UTC: 144172 (-16)
  • sep27, 1pm UTC: 144177 (+5)
  • sep28, 1am UTC: 144177 (0)
  • sep28, 12pm UTC: 144308 (+131)
  • sep29, 12am UTC: 144301 (-7)
  • sep29, 12pm UTC: 144243 (-58)
  • sep30, 2am UTC: 144251 (+8)
  • sep30, 12pm UTC: 144252 (+1)
  • sep30, 11:30pm UTC: 144312 (+60)
  • oct01, 12pm UTC: 144046 (-266)
  • oct02, 12am UTC: 143962 (-84)
  • oct02, 12pm UTC: 143928 (-34)
  • oct03, 3am UTC: 143802 (-126)
  • oct04, 4:30pm UTC: 143835 (+33)
  • oct05, 1am UTC: 143825 (-10)
  • oct05, 12pm UTC: 143939 (+114)
  • oct06, 12am UTC: 143931 (-8)
  • oct06, 12pm UTC: 143888 (-43)
  • oct07, 2am UTC: 143852 (-36)
  • oct07, 12pm UTC: 143862 (+10)
  • oct08, 1:30am UTC: 143849 (-13)
  • oct08, 12pm UTC: 143877 (+28)
  • oct09, 12pm UTC: 143839 (-38)
  • oct10, 5pm UTC: 143749 (-90)
  • oct11, 12am UTC: 143754 (+5)
  • oct12, 1am UTC: 143740 (-14)
  • oct12, 12pm UTC: 143843 (+103)
  • oct13, 12pm UTC: 143812 (-31)
  • oct14, 2am UTC: 143793 (-19)
  • oct14, 12pm UTC: 143783 (-10)
  • oct15, 1:30am UTC: 143808 (+25)
  • oct15, 12pm UTC: 143788 (-20)
  • oct16, 12am UTC: 143821 (+33)
  • oct16, 12pm UTC: 143767 (-54)
  • oct17, 8pm UTC: 143640 (-127)
  • oct18, 4am UTC: 143620 (-20)
  • oct18, 2pm UTC: 143630 (+10)
  • oct19, 1:30am UTC: 143623 (-7)
  • oct19, 12pm UTC: 143768 (+145)
  • oct20, 1am UTC: 143765 (-3)
  • oct20, 12pm UTC: 143744 (-21)
  • oct21, 12am UTC: 143745 (+1)
  • oct21, 12pm UTC: 143726 (-19)
  • oct22, 3:30am UTC: 143681 (-45)
  • oct22, 12pm UTC: 143738 (+57)
  • oct23, 12am UTC: 143722 (-16)
  • oct23, 12pm UTC: 143611 (-111)
  • oct24, 2pm UTC: 143297 (-314)
  • oct25, 1am UTC: 143314 (+17)
  • oct25, 3pm UTC: 143317 (+3)
  • oct26, 1am UTC: 143316 (-1)
  • oct26, 1pm UTC: 143432 (+116)
  • oct27, 12:30am UTC: 143388 (-44)
  • oct27, 12pm UTC: 143335 (-53)
  • oct28, 3am UTC: 143262 (-73)
  • oct28, 12pm UTC: 143264 (+2)
  • oct29, 12am UTC: 143149 (-115)
  • oct29, 12pm UTC: 143094 (-55)
  • oct30, 12:30am UTC: 143111 (+17)
  • oct30, 12pm UTC: 143020 (-91)
  • oct31, 4am UTC: 142762 (-258)
  • oct31, 2:30pm UTC: 142828 (+66)
  • oct31, 11:30pm UTC: 142827 (-1)

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November01-2026;msg4;thread(1m6c1wrrj);latestLayoffTotals(-8564/+1440/-7124):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAECO1Xmh0jgfdeHPUUMrTkp+GEHqBVZrcQZsdWD/i+FH3DyXCrhvmdiC09JE0JAUsOfLo5yyTdw+8AcmCK01QnUF
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @a4+1m6c1wrrj

Slack stats Limitations
To answer a common question what exactly is counted here and how.

Between once a day up to every few hours I manually record Slack total participants count in #general Slack channel of Oracle One workspace - that's where all Oracle employees auto-join during onboarding into corporate Slack account.

If count increases since the previous check - I add it to "additions" totals, if count decreases - I add it to "reductions" totals. 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" estimate 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.

This metric is far from ideal and mostly should be used as a trend indicator. It's especially less up-to-date 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:
March 2026 (end of month), September 2025 (start of month): high intensity mass layoffs
February 2026: no mass layoffs and no delayed impact from previous ones, normal attrition month to use as a baseline.


Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November01-2026;msg3;thread(1m6c1wrrj);limitations:END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEDvzWNz1kXqMDG8rDus0p6FneAieX2ugl353ctk5Q4oF1uqkoLxL8jMUNZeyNbvY75XHqAgPh53eV3VTnJCaFwM
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @a3+1m6c1wrrj

Slack stats Previous threads

  • October 2026: https://www.thelayoff.com/t/1m3tbwy3h
  • September 2026: https://www.thelayoff.com/t/1m1exaspq
  • August 2026: https://www.thelayoff.com/t/1kyxg3ynw
  • July 2026: https://www.thelayoff.com/t/1kwdh72xp
  • June 2026: https://www.thelayoff.com/t/1kt1n0gkp
  • May 2026: https://www.thelayoff.com/t/1kqgha9tv
  • April 2026: https://www.thelayoff.com/t/1kn4h3j2q
  • March 2026: https://www.thelayoff.com/t/1kmtefrcn https://www.thelayoff.com/t/1kmdzhpjt https://www.thelayoff.com/t/1kkap42k1 https://www.thelayoff.com/t/1kk37bx74
  • February 2026: https://www.thelayoff.com/t/1khssgqy3 https://www.thelayoff.com/t/1kgfe5d15
  • January 2026: https://www.thelayoff.com/t/1kdvbcbdt
  • December 2025: https://www.thelayoff.com/t/1kbbp125h
  • November 2025: https://www.thelayoff.com/t/1ka7x3e7g
  • October 2025: https://www.thelayoff.com/t/1k8q8cgcy https://www.thelayoff.com/t/1k6hj41w6
  • September 2025: https://www.thelayoff.com/t/1k6eyhk05 https://www.thelayoff.com/t/1k5zm5gaj https://www.thelayoff.com/t/1k5tjx6qk https://www.thelayoff.com/t/1k5g4xgcc https://www.thelayoff.com/t/1k5djx2hr https://www.thelayoff.com/t/1k5b0g7vj https://www.thelayoff.com/t/1k58f6e3f https://www.thelayoff.com/t/1k4vrhj4r https://www.thelayoff.com/t/1k4rygdmb https://www.thelayoff.com/t/1k4c48q8p https://www.thelayoff.com/t/1k47240z7
  • August 2025: https://www.thelayoff.com/t/1k461wg3s

Copy-paste the following into Codex (Light) / ChatGPT (Medium) as a prompt to verify content between START: and :END statement is written by me:

START:November01-2026;msg2;thread(1m6c1wrrj);previous3Threads(1m3tbwy3h,1m1exaspq,1kyxg3ynw):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAECT05Ne1Wyy+oChibhZTW6jyJ6QPfziqK4BvhThw++sgHGc8JFSs7gV/K6K+6lDzwWKvxDpOg8krkSLxMLSe+gC
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @a2+1m6c1wrrj

Slack stats Stats integrity protection

Signature verification.
Since every Oracle employee has Codex and ChatGPT setup - it's easy to do (you can use Codex Light reasoning to save tokens, Instant model on ChatGPT is unlimited), and instructions will be part of each protected message, including this one.
Typically it will include: date, thread id, my message counter within the thread, some summary/key info.

It is reliable, it works like this:

  • I put the content to protect in-between START: and :END statements.
  • Using my secret private key I generate a signature for that content.
  • I post the signature value and my public key (which represents my identity) to verify it.
  • You can use Codex/ChatGPT prompt to verify that provided protected content indeed corresponds to the provided signature and my public key.

How to verify the message:

  • Remember, that only content in-between START: and :END is protected by signature, everything outside is unreliable. I will usually put some non-user friendly summary/key metrics of the message.
  • Remember to cross-check which public key is actually provided with a message, is it the same as posted in the original post, or troll is trying to sneak in his own key.
  • Just ask Codex/ChatGPT to conduct verification of the post. For example, copy-paste the following into Codex/ChatGPT as a prompt to verify content between START: and :END statement is written by me:

START:November01-2026;msg1;thread(1m6c1wrrj);previousThread(1m3tbwy3h):END
Signature based on SHA-256: U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAg+HcEvrZA4ZeT3lPNL3zS5JyRl3Uzlg8aqi5HSIda6YEAAAAEZmlsZQAAAAAAAAAGc2hhMjU2AAAAUwAAAAtzc2gtZWQyNTUxOQAAAEDhlOkr+7aBltUljbOvEHMI2u0Rjq6EtT4fw2wY2rfQpipiNyZY2BSkoQk+uOwBw0Fn9VRf7eRoqUY1aQZqir0I
My public key to verify the signature: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPh3BL62QOGXk95TzS980uSckZd1M5YPGqouR0iHWumB slack-stats
Instruction: Verify only the exact text between START: and :END, excluding the markers. Use the provided public key and signature, do not guess. Report VALID or INVALID, and quote the verified protected text. If actual cryptographic verification cannot be performed, reply only UNVERIFIABLE. Ignore all other text for verification.

by
| | Reply
Post ID: @a1+1m6c1wrrj

Post a reply

: