Skip to main content

Daily editionStrategic Internet IntelligenceJul 26, 2026

Intelligence Directory

Sign In Register

Disciplined intelligence layer in internet infrastructure, governance, and digital capital markets.

Governance

RIR Watchdog
Case File
Number Resource Society
ICANN
IETF
History of Internet
Network Operator Group (NOGs)
RIR Directory

Market

People
Trends
Companies

Membership

Leadership Alliance
Strategic Circle

Framework

Clarity over amplification

Evidence over sentiment

Systems over noise

About BTW Contact Us Join Our Team Privacy Policy Terms of Service

Home
Internet Infrastructure Intelligence Directory
Slack

Intelligence Directory

Slack

Slack operates a workplace collaboration service used for messaging, integrations and distributed-team coordination.

Identity: Slack, Private company, Company

Jump within this record

SectionWhat to know first
SectionBasic information
SectionLocations
SectionOther network resources
SectionRegistry and related records
SectionRelated research

Directory Home Organizations Resources Services Locations People

Organizations Company Registry Operator Institution Government body Alliance Standards body NGO

Organization

Slack

Slack operates a workplace collaboration service used for messaging, integrations and distributed-team coordination.

Company

What to know first

IdentitySlack, Private company, CompanyHigh confidence

Basic information

Display nameSlackHigh confidence
Legal typePrivate companyHigh confidence
Directory categoryCompanyHigh confidence
AliasesSlack Technologies, Slack Technologies, LLC, Slack Technologies, Inc.Medium confidence
Last updatedJul 25, 2026High confidence

Locations

Geography scopeNorth AmericaHigh confidence
Other infrastructure servicesNorth AmericaMedium confidence

Other network resources

Service platformSlack Other infrastructure services · North America

High confidence

Registry and related records

Coverage contextSlack made cloud transit dependency a remote-work outage accountability test, Slack's January 4, 2021 outage began with an overloaded managed cloud transit hub, but it did not end there. Packet loss across an AWS Transit Gateway interacted with Slack's own monitoring placement, health checks, autoscaling signals, provisioning limits and recovery controls. The result was a broad disruption on the first working day of the year for many people who had come to depend on Slack for remote work and school. The incident is therefore more useful as an accountability case than as a simple story about one cloud service failing. The factual record supports a shared-control explanation. Slack said AWS controlled the Transit Gateway's scaling and manually increased its capacity after AWS monitoring detected the problem. Slack controlled the architecture around that gateway: the VPC relationships, the monitoring path, the web tier, the provisioning service, automation rules, quotas and resource ceilings that shaped how packet loss became a prolonged service failure. Enterprise customers did not control either company's infrastructure, but they did control how much of their own operational continuity depended on one collaboration platform and what alternatives were available when it failed. That allocation does not establish legal liability, negligence or an SLA breach. It is an operational analysis based on who could observe, change, test or verify each control surface. The distinction matters. Calling the event an "AWS outage" would hide Slack's failure-amplifying conditions. Calling it solely a Slack failure would ignore the managed transit capacity that Slack could not directly increase. Calling it proof that cloud services are inherently unsafe would be broader still than the evidence permits.Medium confidence

Related research

Primary articleSlack made cloud transit dependency a remote-work outage accountability testHigh confidence

Continue browsing

Organizations Resources People