{"id":278385,"date":"2023-03-01T14:16:58","date_gmt":"2023-03-01T13:16:58","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=278385"},"modified":"2023-03-02T00:31:37","modified_gmt":"2023-03-01T23:31:37","slug":"microsoft-365-und-twitter-rumpeln-1-maerz-2023","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2023\/03\/01\/microsoft-365-und-twitter-rumpeln-1-maerz-2023\/","title":{"rendered":"Microsoft 365 und Twitter \"rumpeln\" (1. M\u00e4rz 2023) – jetzt auch Exchange Online"},"content":{"rendered":"

Heute Mittag war der Blog hier kurz mal weg – die Zugriffe auf die Datenbank waren wegen \u00dcberlastung nicht durchf\u00fchrbar. Aber auch andernorts hat es gerumpelt – sowohl Twitter als auch Microsoft 365 hatten in diversen Regionen dieser Welt Probleme. Erg\u00e4nzung:<\/strong> In den sp\u00e4ten Stunden des 1. M\u00e4rz 2023 kommt es auch zu einem Ausfall von Exchange Online.<\/p>\n

<\/p>\n

Twitter down<\/h2>\n

\"\"Der Kurznachrichtendienst Twitter scheint einen Ausfall am heutigen 1. M\u00e4rz 2023 gehabt zu haben. Ich konnte zwar bei Tests weiterhin auf mein Konto zugreifen, aber es war etwas z\u00e4h. Andere Nutzer kamen wohl nicht mehr auf die Plattform.<\/p>\n

\"Twitter<\/a><\/p>\n

Unter \"Twitter down\" wurden mir bei einer kurzen Suche einige Tweets<\/a> angezeigt, die vor 2-3 Stunden Probleme reklamierten.<\/p>\n

\"Twitter<\/a><\/p>\n

Jemand hat es in obigem Tweet auf den Punkt gebracht – er hat einen Spaziergang gemacht – ist herrliches Wetter drau\u00dfen. Habe ich auch am sp\u00e4teren Vormittag gemacht, als ich einen Umweg von 6 km von der Physiotherapie nach Hause durch den Wald gelaufen bin. Mir ist der Ausfall auch nur bewusst geworden, weil die Kollegen von Bleeping Computer in diesem Artikel<\/a> berichteten.<\/p>\n

Microsoft 365 down<\/h2>\n

Zudem scheint es einen Ausfall der Microsoft 365-Dienste – vor allem im asiatischen Raum gegeben zu haben. Auf Twitter habe ich diese Meldung<\/a> gesehen. Blog-Leser Andreas P. hat mir per Mail folgende Informationen zukommen lassen (danke daf\u00fcr).<\/p>\n

Incident: MO521925, impacted service: Microsoft 365 suite, impacted feature: Portal, current status is: Service degradation<\/p>\n

ublished Time: 01.03.2023 09:18:53<\/p>\n

Title: Users in the Asia Pacific region may be unable to access multiple Microsoft 365 services<\/p>\n

User impact: Users may be unable to access multiple Microsoft 365 services.<\/p>\n

More info: Impacted services may include but aren't limited to:<\/p>\n

– Microsoft Teams
\n– Exchange Online
\n– Power BI
\n– SharePoint Online
\n– OneDrive for Business<\/p>\n

Current status: We're reviewing our telemetry for impacted scenarios to help determine our next troubleshooting steps.<\/p>\n

Scope of impact: This issue may potentially affect any Asia Pacific user attempting to access Microsoft 365 services.<\/p>\n

Next update by: Wednesday, March 1, 2023, at 10:30 AM UTC<\/p>\n

Published Time: 01.03.2023 08:27:49<\/p>\n

Title: Users can't access Microsoft Teams and Exchange Online<\/p>\n

User impact: Users can't access Microsoft Teams and Exchange Online.<\/p>\n

Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.<\/p><\/blockquote>\n

Jemand von den Ausf\u00e4llen betroffen?<\/p>\n

Exchange Online mit Problemen<\/h2>\n

Erg\u00e4nzung: Seit den sp\u00e4ten Abendstunden gibt es auch Probleme mit Exchange Online, wo Nutzer keine Mails verarbeiten k\u00f6nnen. Microsoft hat auf Twitter<\/a> ein Problem eingestanden:<\/p>\n

\"Exchange<\/a>
\nAndreas P. hat mir die betreffenden Statusinformation f\u00fcr EX522020 per Mail zukommen lassen (danke daf\u00fcr).<\/p>\n

Published Time: 01.03.2023 21:58:06<\/p>\n

Title: Users may be unable to access their Exchange Online mailbox or send\/receive messages<\/p>\n

User impact: Users may have been unable to access their Exchange Online mailboxes or send and receive email messages.<\/p>\n

More info: Users may have received an error message including: \"550 5.4.1 Recipient address rejected: Access denied\" when attempting to send or receive messages.<\/p>\n

Final status: We've confirmed that rerouting EOP traffic away from the affected portion of infrastructure has successfully resolved the user impact.<\/p>\n

Scope of impact: Impact was specific to users who are served through the affected infrastructure in North America, Europe, and the United Kingdom.<\/p>\n

Start time: Wednesday, March 1, 2023, at 1:02 PM UTC<\/p>\n

End time: Wednesday, March 1, 2023, at 8:20 PM UTC<\/p>\n

Preliminary root cause: A portion of Exchange Online Protection (EOP) infrastructure wasn't operating as expected due to a potential misconfiguration, resulting in the impact.<\/p>\n

Next steps:
\n– We're continuing to investigate the underlying cause of the issue.
\n– We're reviewing our telemetry signals to find ways to identify and resolve similar issues in the future more quickly.<\/p>\n

A post-incident report will be available on the Service Health Dashboard within five business days.<\/p>\n

Published Time: 01.03.2023 21:19:30<\/p>\n

Title: Users may be unable to access their Exchange Online mailbox or send\/receive messages<\/p>\n

User impact: Users may be unable to access their Exchange Online mailboxes or send and receive email messages.<\/p>\n

More info: Users may receive an error message including: \"550 5.4.1 Recipient address rejected: Access denied\" when attempting to send or receive messages.<\/p>\n

Current status: We've successfully routed EOP traffic away from affected portion of infrastructure. We're monitoring our systems and reaching out to previously affected users to confirm impact has been resolved.<\/p>\n

Scope of impact: Impact is specific to users who are served through the affected infrastructure in North America, Europe, and the United Kingdom.<\/p>\n

Start time: Wednesday, March 1, 2023, at 1:11 PM UTC<\/p>\n

Preliminary root cause: A portion of Exchange Online Protection (EOP) infrastructure isn't operating as expected, resulting in the impact.<\/p>\n

Next update by: Wednesday, March 1, 2023, at 9:30 PM UTC<\/p>\n

Published Time: 01.03.2023 20:55:45<\/p>\n

While our root cause investigation is ongoing, we're in the process of routing EOP traffic away from what appears to be the affected infrastructure as a potential mitigation strategy.<\/p>\n

This quick update is designed to give the latest information on this issue.<\/p>\n

Published Time: 01.03.2023 20:24:39<\/p>\n

Title: Users may be unable to access their Exchange Online mailbox or send\/receive messages<\/p>\n

User impact: Users may be unable to access their Exchange Online mailboxes or send and receive email messages.<\/p>\n

More info: Users may receive an error message including: \"550 5.4.1 Recipient address rejected: Access denied\" when attempting to send or receive messages.<\/p>\n

Current status: We continue to suspect a potential DBEB issue as the source of impact and are reviewing associated Exchange Online Protection (EOP) telemetry data. In parallel, we continue to collect information from affected users to aid in our investigation.<\/p>\n

Scope of impact: Impact is specific to users who are served through the affected infrastructure in North America, Europe, and the United Kingdom.<\/p>\n

Start time: Wednesday, March 1, 2023, at 1:11 PM UTC<\/p>\n

Next update by: Wednesday, March 1, 2023, at 8:30 PM UTC<\/p>\n

Published Time: 01.03.2023 19:40:07<\/p>\n

Our continued monitoring has indicated that the issue is ongoing. We're reviewing diagnostics from affected users to determine our next steps.<\/p>\n

This quick update is designed to give the latest information on this issue.<\/p>\n

Published Time: 01.03.2023 19:19:05<\/p>\n

Title: Users may be unable to access their Exchange Online mailbox or send\/receive messages<\/p>\n

User impact: Users may be unable to access their Exchange Online mailboxes or send and receive email messages.<\/p>\n

More info: Users may receive an error message including: \"550 5.4.1 Recipient address rejected: Access denied\" when attempting to send or receive messages.<\/p>\n

Current status: Our internal telemetry has indicated that the service has largely recovered. We're monitoring our systems while continuing our investigation to determine the underlying cause of the issue and whether additional action is required.<\/p>\n

Scope of impact: Impact is specific to users who are served through the affected infrastructure in North America, Europe, and the United Kingdom.<\/p>\n

Start time: Wednesday, March 1, 2023, at 1:11 PM UTC<\/p>\n

Next update by: Wednesday, March 1, 2023, at 7:30 PM UTC<\/p>\n

Published Time: 01.03.2023 18:22:03<\/p>\n

Title: Users may be unable to access their Exchange Online mailbox or send\/receive messages<\/p>\n

User impact: Users may be unable to access their Exchange Online mailboxes or send and receive email messages.<\/p>\n

More info: Users may receive an error message including: \"550 5.4.1 Recipient address rejected: Access denied\" when attempting to send or receive messages.<\/p>\n

Current status: We've identified a potential Directory Based Edge Blocking (DBEB) issue that may be contributing to impact. We're investigating this alongside our existing diagnostic data to determine our next steps.<\/p>\n

Scope of impact: Impact is specific to users who are served through the affected infrastructure in North America, Europe, and the United Kingdom.<\/p>\n

Start time: Wednesday, March 1, 2023, at 1:11 PM UTC<\/p>\n

Next update by: Wednesday, March 1, 2023, at 6:30 PM UTC<\/p>\n

Published Time: 01.03.2023 17:33:04<\/p>\n

Title: Users may be unable to access their Exchange Online mailboxes via any connection method<\/p>\n

User impact: Users may be unable to access their Exchange Online mailboxes via any connection method.<\/p>\n

Current status: We're analyzing mailbox request exceptions and continuing our review of service telemetry trends to identify the underlying root cause and formulate a plan to remediate impact.<\/p>\n

Scope of impact: Impact is specific to users who are served through the affected infrastructure in North America and Europe.<\/p>\n

Start time: Wednesday, March 1, 2023, at 1:11 PM UTC<\/p>\n

Next update by: Wednesday, March 1, 2023, at 7:00 PM UTC<\/p>\n

Published Time: 01.03.2023 15:15:07<\/p>\n

Title: Some users may be unable to access their Exchange Online mailboxes via any connection method<\/p>\n

User impact: Users may be unable to access their Exchange Online mailboxes via any connection method.<\/p>\n

Current status: We're reviewing trends in service telemetry to determine our next troubleshooting steps.<\/p>\n

Scope of impact: Impact is specific to some users who are served through the affected infrastructure in North America and Europe.<\/p>\n

Start time: Wednesday, March 1, 2023, at 1:11 PM UTC<\/p>\n

Next update by: Wednesday, March 1, 2023, at 4:30 PM UTC<\/p>\n

Published Time: 01.03.2023 14:59:58<\/p>\n

Title: We're looking into a potential problem.<\/p>\n

User Impact: We're investigating the potential end-user impact.<\/p>\n

Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.<\/p><\/blockquote>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Heute Mittag war der Blog hier kurz mal weg – die Zugriffe auf die Datenbank waren wegen \u00dcberlastung nicht durchf\u00fchrbar. Aber auch andernorts hat es gerumpelt – sowohl Twitter als auch Microsoft 365 hatten in diversen Regionen dieser Welt Probleme. … Weiterlesen →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7862],"tags":[7377,987,1267],"class_list":["post-278385","post","type-post","status-publish","format-standard","hentry","category-stoerung","tag-microsoft-365","tag-storung","tag-twitter"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/278385","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=278385"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/278385\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=278385"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=278385"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=278385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}