#general ..... it can't be unsubscribed .... no change there yet.
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!
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 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.
@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 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.
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!
@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.
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.
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-nov17: 682 layoffs, 791 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)
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.
A difference on 50 employees in #general sounds like normal turnover for Oracle
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.
- 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)
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 #general user count decreasing
Around 55,469 this morning at 9 and slowly decreasing a few dozen :(
Methodology:
Tracking participants count #general Slack channel in Oracle One workspace
- oct01, 4am UTC: 167277 (0)
- oct01, 6:30pm UTC: 167116 (-161)
- oct01, 10pm UTC: 167160 (+44)
- oct02, 4am UTC: 167080 (-80 in comparison to 167160)
- oct02, 3pm UTC: 167092 (+12)
- oct03, 4am UTC: 167001 (-91 in comparison to 167092)
- oct03, 3pm UTC: 167014 (+13)
- oct04, 5am UTC: 166695 (-319 in comparison to 167014)
- oct05, 6:30pm UTC: 166720 (+25)
- oct06, 4am UTC: 166692 (-28 in comparison to 166720)
- oct06, 7pm UTC: 166814 (+122)
- oct07, 6am UTC: 166774 (-40 in comparison to 166814)
- oct08, 4am UTC: 166731 (-43)
- oct08, 3pm UTC: 166740 (+9)
- oct09, 4am UTC: 166670 (-70 in comparison to 166740)
- oct09, 3pm UTC: 166943 (+273)
- oct10, 12pm UTC: 167416 (+473)
History:
- 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)
Methodology:
Tracking participants count #general Slack channel in Oracle One workspace
- oct01, 4am UTC: 167277 (0)
- oct01, 6:30pm UTC: 167116 (-161)
- oct01, 10pm UTC: 167160 (+44)
- oct02, 4am UTC: 167080 (-80 in comparison to 167160)
History:
- 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)
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)
- sep09, 6am UTC: 168672 (-87 in comparison to previous 168759)
- sep09, 1pm UTC: 168705 (+33)
- sep10, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
- sep13, 6am UTC: 168275 (-59)
- sep15, 6am UTC: 168268 (-7)
- sep15, 3pm UTC: 168533 (+265)
- sep16, 6am UTC: 168455 (-78 in comparison to previous 168533)
- sep17, 6am UTC: 168380 (-75)
- sep17, 5pm UTC: 168404 (+24)
- sep18, 6am UTC: 168313 (-89 in comparison to previous 168404)
- sep18, 9pm UTC: 168370 (+57)
- sep19, 6am UTC: 168292 (-78 in comparison to previous 168370)
- sep20, 6am UTC: 168211 (-81)
- sep22, 6am UTC: 168268 (+57)
- sep22, 5pm UTC: 168396 (+128)
- sep23, 7am UTC: 168004 (-392 in comparison to previous 168396)
- sep23, 8pm UTC: 168010 (+6)
- sep24, 6am UTC: 167952 (-58 in comparison to previous 168010)
- sep24, 3pm UTC: 167961 (+9)
- sep25, 6am UTC: 167881 (-80 in comparison to previous 167961)
- sep25, 7pm UTC: 167917 (+36)
- sep26, 5am UTC: 167876 (-41 in comparison to previous 167917)
- sep29, 2pm UTC: 167794 (-82)
- sep30, 1pm UTC: 167745 (-49)
- oct01, 4am UTC: 167277 (-468)
I will be tracking October as well, but may be with fewer checkpoints - will depend on the pace of EMEA layoffs expected on October and more importantly how fast they are reflected in Slack.
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)
- sep09, 6am UTC: 168672 (-87 in comparison to previous 168759)
- sep09, 1pm UTC: 168705 (+33)
- sep10, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
- sep13, 6am UTC: 168275 (-59)
- sep15, 6am UTC: 168268 (-7)
- sep15, 3pm UTC: 168533 (+265)
- sep16, 6am UTC: 168455 (-78 in comparison to previous 168533)
- sep17, 6am UTC: 168380 (-75)
- sep17, 5pm UTC: 168404 (+24)
- sep18, 6am UTC: 168313 (-89 in comparison to previous 168404)
- sep18, 9pm UTC: 168370 (+57)
- sep19, 1am UTC: 168292 (-78 in comparison to previous 168370)
- sep20, 1am UTC: 168211 (-81)
- sep22, 1am UTC: 168268 (+57)
- sep22, 5pm UTC: 168396 (+128)
- sep23, 2am UTC: 168004 (-392 in comparison to previous 168396)
- sep23, 8pm UTC: 168010 (+6)
- sep24, 1am UTC: 167952 (-58 in comparison to previous 168010)
- sep24, 3pm UTC: 167961 (+9)
- sep25, 1am UTC: 167881 (-80 in comparison to previous 167961)
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)
- sep09, 6am UTC: 168672 (-87 in comparison to previous 168759)
- sep09, 1pm UTC: 168705 (+33)
- sep10, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
- sep13, 6am UTC: 168275 (-59)
- sep15, 6am UTC: 168268 (-7)
- sep15, 3pm UTC: 168533 (+265)
- sep16, 6am UTC: 168455 (-78 in comparison to previous 168533)
- sep17, 6am UTC: 168380 (-75)
- sep17, 5pm UTC: 168404 (+24)
- sep18, 6am UTC: 168313 (-89 in comparison to previous 168404)
- sep18, 9pm UTC: 168370 (+57)
- sep19, 1am UTC: 168292 (-78 in comparison to previous 168370)
- sep20, 1am UTC: 168211 (-81)
- sep22, 1am UTC: 168268 (+57)
- sep22, 5pm UTC: 168396 (+128)
- sep23, 2am UTC: 168004 (-392 in comparison to previous 168396)
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)
- sep09, 6am UTC: 168672 (-87 in comparison to previous 168759)
- sep09, 1pm UTC: 168705 (+33)
- sep10, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
- sep13, 6am UTC: 168275 (-59)
- sep15, 6am UTC: 168268 (-7)
- sep15, 3pm UTC: 168533 (+265)
- sep16, 6am UTC: 168455 (-78 in comparison to previous 168533)
- sep17, 6am UTC: 168380 (-75)
- sep17, 5pm UTC: 168404 (+24)
- sep18, 6am UTC: 168313 (-89 in comparison to previous 168404)
- sep18, 9pm UTC: 168370 (+57)
- sep19, 1am UTC: 168292 (-78 in comparison to previous 168370)
- sep20, 1am UTC: 168211 (-81)
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)
- sep09, 6am UTC: 168672 (-87 in comparison to previous 168759)
- sep09, 1pm UTC: 168705 (+33)
- sep10, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
- sep13, 6am UTC: 168275 (-59)
- sep15, 6am UTC: 168268 (-7)
- sep15, 3pm UTC: 168533 (+265)
- sep16, 6am UTC: 168455 (-78 in comparison to previous 168533)
- sep17, 6am UTC: 168380 (-75)
- sep17, 5pm UTC: 168404 (+24)
- sep18, 6am UTC: 168313 (-89 in comparison to previous 168404)
- sep18, 9pm UTC: 168370 (+57)
- sep19, 1am: 168292 (-78 in comparison to previous 168370)
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)
- sep09, 6am UTC: 168672 (-87 in comparison to previous 168759)
- sep09, 1pm UTC: 168705 (+33)
- sep10, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
- sep13, 6am UTC: 168275 (-59)
- sep15, 6am UTC: 168268 (-7)
- sep15, 3pm UTC: 168533 (+265)
- sep16, 6am UTC: 168455 (-78 in comparison to previous 168533)
- sep17, 6am UTC: 168380 (-75)
- sep17, 5pm UTC: 168404 (+24)
- sep18, 6am UTC: 168313 (-89 in comparison to previous 168404)
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, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
- sep13, 6am UTC: 168275 (-59)
- sep15, 6am UTC: 168268 (-7)
- sep15, 3pm UTC: 168533 (+265 new people were onboarded?)
- sep16, 6am: 168455 (-78 in comparison to previous 168533)
- sep17, 6am: 168380 (-75)
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, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
- sep13, 6am UTC: 168275 (-59)
- sep15, 6am UTC: 168268 (-7)
- sep15, 3pm UTC: 168533 (+265 new people were onboarded?)
- sep16, 6am: 168455 (-78 in comparison to previous 168533)
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, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
- sep13, 6am UTC: 168275 (-59)
- sep15, 6am UTC: 168268 (-7)
Thanks for posting these - do you also have the numbers for August? No need for day by day...
Unfortunately, I didn't track it. IDC lost 3.5k in August based on news.
August 15 #general totals were 173529, but this missing all layoffs first 2 weeks of August.
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, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
- sep13, 6am UTC: 168275 (-59)
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, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)
- sep12, 6am UTC: 168334 (-100)
Some countries in the Pacific region have a 2-week delay before access is cut. So even through they received "notices" already, they are still in Slack.
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, 4:30am UTC: 168627 (-78 in comparison to previous 168705)
- sep11, 6.30am UTC: 168434 (-190)