Errors accessing Slack Application

Resolved
Resolved
After 36 minutes

A fix has been implemented and access to Slack is fully restored. We will continue to closely monitor this situation for any re-occurrence. This incident is now closed.

Identified

We are aware of WSS customers experiencing DNS errors when accessing Slack application. This is due to issues Slack experienced earlier today. We are currently working on flushing DNS on our side to restore Slack access.

There is no impact to protection services and all other aspects of our service remain operational. We will provide further updates as new information is discovered.

Began at:

Affected components
  • Cloud Secure Web Gateway
    • Data Centers - Americas
      • Las Vegas (GUSLV1)
      • Buenos Aires (GARBA1)
      • Columbia (GUSCO1)
      • Des Moines (GUSDM1)
      • Portland (GUSPO1)
      • Sao Paulo (GBRSP1)
      • Los Angeles (GUSLA1)
      • Mexico City (GMXMC1)
      • Washington, DC (GUSAS1)
      • Montreal (GCAMO1)
    • Data Centers - Asia Pacific
      • Sydney (GAUSY1)
      • Taipei (GTWTA1)
      • Tokyo (GJPTK)
      • Wellington (GNZWL)
      • Mumbai (GINMU1)
      • Osaka (GJPOS1)
      • Seoul (GKRSE1)
      • Shanghai (SHA1)
      • Singapore (GSGRS1)
      • Auckland (GNZAU1)
      • Hong Kong (GCNHK1)
      • Indonesia (GIDJK11)
      • Beijing (PEK1)
    • Data Centers - Europe, Middle East & Africa
      • Abu Dhabi (GAEAD1)
      • Stockholm (GSESK1)
      • Copenhagen (GDKCP1)
      • Tel Aviv (GILTA1)
      • Turin (GITTU1)
      • Dubai (GAEDX1)
      • Dublin (GIEDU1)
      • Frankfurt (GDEFR1)
      • Helsinki (GFIHE1)
      • Johannesburg (GZAJB1)
      • Madrid (GESMA1)
      • Middlesex (GGBLO1)
      • Milan (GITMI1)
      • Munich (GDEMU)
      • Oslo (GNOOS1)
      • Amsterdam (GNLAM1)
      • Belgium (GBEBR11)
      • Bucharest (GROBU1)
      • Paris (GFRPA1)
      • Zurich (GCHZU1)