- #Slack outage post mortem software
- #Slack outage post mortem Offline
- #Slack outage post mortem series
#Slack outage post mortem series
Slack did not immediately respond to questions seeking more information on the cause of the outage and how many users have been affected. The hours-long outage that kicked off the 2021 working year for Slack customers was the result of a cascading series of problems initially caused by network. Finally, there was an hours-long outage that impacted some Comcast customers on Super Bowl Sunday. (Federation with our AD) So the effects were still showing 8 hours after the first reports. You can read Square’s post-mortem of the incident here. I read the first reports on r/sysadmin around midnight (Central European Time) and when I arrived at work around 8 in the morning we had logs showing 36000 faulty logins since midnight and still increasing. Slack’s services were also disrupted last September as a DNS configuration change created issues for some users. The outage, however, breaks with the change-and-rollback pattern seen elsewhere in the past fortnight.
#Slack outage post mortem Offline
Slack was one of a number of SaaS vendors knocked offline last December due to an outage at cloud provider Amazon Web Services’ US East 1 data center apparently related to network device failure. While players were allowed to return to Roblox on October 31st, Roblox and HashiCorp continued refining their understanding of the outage throughout the following week. Further Analysis and Changes Resulting from the Outage. For this reason, we report our uptime as an average derived from the number of affected users. At 16:45 Sunday, 73 hours after the start of the outage, 100 of players were given access and Roblox was fully operational. While Software-as-a-Service (SaaS) vendors typically provide high levels of uptime, outages are not uncommon. Slack is a distributed platform and during any given incident it is rare for all Slack teams to be affected. That's according to its most recently released stats from October 2019, so it's likely the number is considerably higher now. Slack, which was acquired by Salesforce last year for $27.7 billion, has more 12 million daily active users. The company finally reported at 2:24 pm ET that operations were back to normal. If you're still encountering any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) or clear the app cache (Help > Troubleshooting > Clear Cache and Restart on desktop, Preferences > Advanced > Reset Cache on mobile)." ET, the company offered this advice: "We're continuing to see improvements, but we still have some work to do.
#Slack outage post mortem software
Identify the severity of the incident, the scope of impact, and the actions you take to resolve the incident. Post-mortems are an essential part of software projects. We’ll confirm once this issue is fully resolved." įor users still having issues as of about 1:45 p.m. Whether you are dealing with a cybersecurity threat or an actual breach, use this security postmortem template to clearly communicate the details of an incident and related system vulnerabilities. At 12:07 p.m., Slack pointed to "signs of improvement. Please try reloading Slack, and if not a cache reset.
0 kommentar(er)
