lkaklv.blogg.se - Discord and spotify down

There are fears that Russia may step up its cyberwarfare against the West in response to sanctions against Moscow for invading Ukraine – so any outages set off alarm bells in people's heads – though so far, there's been little sign of any significant increase in such activity.We’re aware of an issue causing message failures and are working on a fix.Īpologies for the disruption & thx for hanging tight! - Discord March 8, 2022Īfter roughly three hours, service was restored. There were also reports that Wikipedia also took a brief dive for some, although the site to us is up and running.Īs an aside, The Register reported last week that cloud status pages and complaints from netizens do not always reflect reality, for various technical and non-technical reasons.

ISO.org outage hits day 3: Still in the dark as the important matter of bunk bed standards enters discussion.

What is it with cloud status pages not reflecting reality?.

Iran's internet chokepoint caught fire, caused outages.

Work chat app Slack suffers services outage.

Some services where outages are being reported are not Cloudflare customers, so it's unlikely Cloudflare is the cause." There's no evidence of an increase in attack traffic. "We don't see any issues with Cloudflare's systems and traffic is flowing normally. "We have seen reports," a Cloudflare spokesperson to The Register. But Amazon's status page for its web services showed no issues – and AWS disputes the accuracy of Downdetector – while Cloudflare said everything was working fine despite online gripes. It may well be that Google Cloud's intermittent issues caused a knock-on effect for Discord and Spotify today.ĭ showed spikes in complaints from netizens about a range of services, including AWS and Cloudflare.

Thus far, impact has only been observed in us-east1, but customers with multi-regional Traffic Director deployments could be impacted in more regions.Ĭustomers with Traffic Director managing their envoys should consider moving to backends that are not Traffic Director-managed. Affected customers will see elevated HTTP 500s errors on load balancers with Traffic Director-managed customer-run Envoy backends.