Examples might include the Chief Information Officer or FAS Commissioner. TTS collaborators within GSA may be added as full Slack members. Other collaborators should be added as single or multi-channel guests as appropriate. By default, contractors who are 'embedded' in TTS (working on TTS projects most or full-time) can be added as full members using their GSA emails. Other feds we're not working with directlyĬontractors' level of access will be determined by the Contracting Officer (CO).The general public, for which we have dedicated channels.Vendors with GSA who are working on a project with TTS, for which we have a Memorandum of Understanding (MOU).Vendors under contract (not just a Terms of Service) with TTS.Partners at federal agencies whose projects are under an Interagency Agreement with TTS, or at state or local agencies whose projects are under an Intergovernmental Collaboration Act agreement with TTS.If you'd like to receive a full Root Cause Analysis (RCA) report, please reach out to to request one.Collaboration with people outside of TTS falls into one of two categories: We continued to closely monitor the situation until we had full confidence the issue was resolved and no further impact would reoccur. By 9:14 AM PST, everyone should have been able to connect to Slack again after reloading their app or browser tab. This allowed the system to recover while steadily restoring full access to all users. With traffic distributed across the additional databases, we gradually lifted the rate limits to allow more people to connect to Slack. We reinstated the rate limits and redirected some traffic to the database replicas to relieve the demand on our primary databases. However, we moved too quickly and the increased activity affected the system again.

Once the system had stabilized, we began lifting these rate limits to enable more connections to Slack. This meant that some people could not access Slack at all, but also that Slack would continue working for those who were already connected. We introduced tighter rate limits on connection requests to reduce the load on the system. Due to this increased activity, the affected databases failed to serve incoming requests to connect to Slack. On Februfrom 6:00 AM PST to 9:14 AM PST, customers may not have been able to access Slack.Ī configuration change inadvertently lead to a sudden increase in activity on our database infrastructure.

Slack official website