{"id":277614,"date":"2023-02-07T11:39:05","date_gmt":"2023-02-07T10:39:05","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=277614"},"modified":"2024-01-24T11:28:59","modified_gmt":"2024-01-24T10:28:59","slug":"outlook-com-ist-ausgefallen-7-feb-2023","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2023\/02\/07\/outlook-com-ist-ausgefallen-7-feb-2023\/","title":{"rendered":"Outlook.com ist ausgefallen (7. Feb. 2023)"},"content":{"rendered":"

\"Stop[English<\/a>]Microsofts E-Mail-Dienst outlook.com ist heute (7. Februar 2023) seit ca. 5:00 Uhr deutscher Zeit wohl weltweit gest\u00f6rt. Es gibt aktuell zwar Indizien, dass die St\u00f6rung zur\u00fcck geht. Aber die Statusseiten von Microsoft 365 oder Outlook 365 melden weiterhin ein Problem mit diesem Dienst. Nutzer, die auf diese Cloud-Funktion angewiesen sind, k\u00f6nnen sich weder anmelden noch Mails versenden oder empfangen. Hier ein schneller \u00dcberblick, was Sache ist. Erg\u00e4nzungen zum 8.2.2023.<\/p>\n

<\/p>\n

\"\"Ich habe, nachdem ich den Hinweis bei den Kollegen von Bleeping Computer gesehen<\/a> habe, mal den downdetector.com bzw. allestoerungen.de aufgerufen. Hier die Meldungen von downdetector.com<\/a>:<\/p>\n

\"outlook.com<\/a><\/p>\n

Es wird eine St\u00f6rung um 5:00 Uhr UTC angezeigt, die nun aber bereits am Abklingen ist. Auf der deutschen Seite allestoerungen.de findet sich diese Darstellung.<\/p>\n

\"Outlook.com<\/a><\/p>\n

Auch hier zeigt sich ab 5:00 Uhr heute fr\u00fch (7. Feb. 2023) eine starke Zunahme der St\u00f6rungsmeldungen, die aber langsam abnimmt. Auf reddit.com hat sich dieser Nutzer<\/a> vor 5 Stunden gemeldet:<\/p>\n

Help! Everything is gone!<\/p>\n

I opened my outlook app to check my mail like always but everything is gone! I don't mean some emails have disappeared, I mean literally EVERYTHING is gone. Inbox, deleted, junk, everything!!!!<\/p>\n

Please, any advice????<\/p><\/blockquote>\n

Auf Twitter hat Microsoft 365 Status [@MSFT365Status<\/a>) das Problem mit outlook.com best\u00e4tigt<\/a>. Microsoft untersucht Zugriffs- und Serviceprobleme f\u00fcr Outlook. Weitere Informationen werden im Admin Center unter EX512238 bereitgestellt.<\/p>\n

\"Outlook.com<\/p>\n

Verfolgt man die Meldungen, hat Microsoft bereits erste Ma\u00dfnahmen zur Behebung des Problems eingeleitet. Die Statusseite f\u00fcr Dienste<\/a> von Microsoft weist aber weiterhin Probleme mit outlook.com aus. Dort hei\u00dft es aktuell:<\/p>\n

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

Title: Unable to send, receive, or search email through Outlook.com<\/p>\n

User impact: Users may be unable to send, receive, or search email within Outlook.com.<\/p>\n

More info: Outlook.com functionality such as Calendar APIs consumed by other services such as Microsoft Teams are also affected.<\/p>\n

Current status: We're applying targeted mitigations to a subset of affected infrastructure and validating that it has mitigated impact. We're also making traffic optimization efforts to alleviate user impact and expedite recovery.<\/p>\n

Start time: Tuesday, February 7, 2023, at 4:04 AM UTC<\/p>\n

Next update by: Tuesday, February 7, 2023, at 11:00 AM UTC<\/p><\/blockquote>\n

Neben dem Mailversand sind auch Zusatzfunktionen wie die Kalender-API betroffen. Auch Microsoft Teams-Nutzer bekommen diese St\u00f6rung zu sp\u00fcren, wenn ich die Statusmeldung richtig interpretiere. Jemand von euch betroffen?<\/p>\n

Blog-Leser Andreas P. hat mir folgende Erg\u00e4nzungen aus dem Statusbereich des Dashboard zukommen lassen – danke daf\u00fcr.<\/p>\n

Published Time: 08.02.2023 05:41:40<\/p>\n

Current status: We have began receiving reports of customers stating that the communication is not visible in their Service Health Dashboard. This experience may occur if your organization is hosted in a non-impacted region, but you have users in the affected areas. We have expanded the scope of this post to ensure the message visible.<\/p>\n

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

Published Time: 08.02.2023 05:15:44<\/p>\n

Title: Users may be unable to use various features or services within Microsoft Teams<\/p>\n

User impact: Users may be unable to use various features or services within Microsoft Teams.<\/p>\n

More info: Our investigation indicates that these features are likely still affected:
\n-Microsoft Teams meetings start with default policies rather than previously set organizer policies
\n-Users may be unable to receive notifications with Microsoft Teams
\n-Users may be unable to receive calls
\n-Users may be unable to see presence of other users within Microsoft Teams
\n-Users may be unable to schedule, present, or broadcast during Live Events<\/p>\n

Our telemetry indicates that these scenarios are likely mitigated:
\n-Users may have received an \"oops\" page when attempting to start the Teams client.
\n-Users may have been unable to make emergency calls-Users may have been unable to join live events.<\/p>\n

We received reports of customers stating that the communication is not visible in their Service Health Dashboard. This experience may occur if your organization is hosted in a non-impacted region, but you have users in the affected areas. We have expanded the scope of this post to ensure the message visible.<\/p>\n

Current status: Based on our monitoring, a majority of the impact has been resolved. We are continuing to treat this incident with the highest urgency while we address the residual impact related to this event.<\/p>\n

Scope of impact: This issue primarily impacts users located within or hosted through the Asia Pacific and Australia regions, but could impact any user if served through those regions as well. Users located in non-impacted regions may see impact when attempting to interact with an affected user.<\/p>\n

Start time: Tuesday, February 7, 2023, at 8:25 PM UTC<\/p>\n

Root cause: A portion of infrastructure supporting users' ability to access and send messages in Microsoft Teams is operating below acceptable performance thresholds, resulting in impact.<\/p>\n

Next update by: Wednesday, February 8, 2023, at 5:30 AM UTC<\/p>\n

Published Time: 08.02.2023 03:51:12<\/p>\n

Title: Users may be unable to use various features or services within Microsoft Teams<\/p>\n

User impact: Users may be unable to use various features or services within Microsoft Teams.<\/p>\n

More info: Our investigation indicates that these features are likely still affected:
\n-Microsoft Teams meetings start with default policies rather than previously set organizer policies
\n-Users may be unable to receive notifications with Microsoft Teams
\n-Users may be unable to see presence of other users within Microsoft Teams
\n-Users may be unable to schedule, present, or broadcast during Live Events<\/p>\n

Our telemetry indicates that these scenarios are mitigated:
\n-Users may have received an \"oops\" page when attempting to start the Teams client.
\n-Users may have been unable to receive calls
\n-Users may have been unable to make emergency calls-Users may have been unable to join live events.<\/p>\n

Current status: We are continuing to urgently address any residual impact related to this incident. We understand the impact that this issue may have on your organization and we are dedicated to addressing the degradation associated with this issue.<\/p>\n

Scope of impact: This issue primarily impacts users located within or hosted through the Asia Pacific and Australia regions, but could impact any user if served through those regions as well.<\/p>\n

Start time: Tuesday, February 7, 2023, at 8:25 PM UTC<\/p>\n

Root cause: A portion of infrastructure supporting users' ability to access and send messages in Microsoft Teams is operating below acceptable performance thresholds, resulting in impact.<\/p>\n

Next update by: Wednesday, February 8, 2023, at 4:30 AM UTC<\/p>\n

Published Time: 08.02.2023 02:56:46<\/p>\n

Title: Users may be unable to use various features or services within Microsoft Teams<\/p>\n

User impact: Users may be unable to use various features or services within Microsoft Teams.<\/p>\n

More info: Our investigation indicates that these features are likely still affected:
\n-Microsoft Teams meetings start with default policies rather than previously set organizer policies
\n-Users may be unable to receive notifications with Microsoft Teams
\n-Users may be unable to see presence of other users within Microsoft Teams<\/p>\n

Our telemetry indicates that these scenarios are mitigated:
\n-Users may also receive an \"oops\" page when attempting to start the Teams client.
\n-Users may be unable to receive calls
\n-Users may be unable to make emergency calls<\/p>\n

Current status: We're seeing continual improvements to the service after rerouting the affected traffic. We are continuing to monitor while we address any lingering impact related to this incident.<\/p>\n

Scope of impact: This issue primarily impacts users hosted through the Asia Pacific and Australia regions but could impact any user if served through those regions as well.<\/p>\n

Start time: Tuesday, February 7, 2023, at 8:25 PM UTC<\/p>\n

Root cause: A portion of infrastructure supporting users' ability to access and send messages in Microsoft Teams is operating below acceptable performance thresholds, resulting in impact.<\/p>\n

Next update by: Wednesday, February 8, 2023, at 3:00 AM UTC<\/p>\n

Published Time: 08.02.2023 01:48:37<\/p>\n

Title: Users may be unable to use various features or services within Microsoft
\nTeams
\nUser impact: Users may be unable to use various features or services within Microsoft Teams.<\/p>\n

More info: Our investigation indicates that these features are likely still affected:
\n-Microsoft Teams meetings start with default policies rather than previously set organizer policies
\n-Users may be unable to receive notifications with Microsoft Teams
\n-Users may be unable to see presence of other users within Microsoft Teams<\/p>\n

Our telemetry indicates that these scenarios are mitigated:
\n-Users may also receive an \"oops\" page when attempting to start the Teams client.
\n-Users may be unable to receive calls
\n-Users may be unable to make emergency calls<\/p>\n

Current status: We've finished rerouting the affected service traffic to alternate infrastructure and our monitoring indicates that Microsoft Teams start up and sign-in have been recovered for users in the affected regions. We'll continue monitoring the service health and perform any additional steps necessary to fully resolve the issue for all users.<\/p>\n

Scope of impact: Your organization is affected by this event, and all or most of your users are likely affected.<\/p>\n

Start time: Tuesday, February 7, 2023, at 8:25 PM UTC<\/p>\n

Root cause: A portion of infrastructure supporting users' ability to access and send messages in Microsoft Teams is operating below acceptable performance thresholds, resulting in impact.<\/p>\n

Next update by: Wednesday, February 8, 2023, at 2:00 AM UTC<\/p>\n

Published Time: 08.02.2023 00:57:49<\/p>\n

Title: Users may be unable to send messages and create or update meetings in all Microsoft Teams connection methods<\/p>\n

User impact: Users may be unable to send or receive messages, or create, update, or join meetings in Microsoft Teams.<\/p>\n

More info: Additionally, affected users may also see that Microsoft Teams meetings start with default policies rather than previously set organizer policies. Users may also receive an \"oops\" page when attempting to start the Teams client.<\/p>\n

Current status: We've identified a specific portion of our hosting infrastructure that is performing below acceptable levels and are working to move Microsoft Teams services to healthy infrastructure to remediate the problem. In parallel, we're evaluating all options to restore service as quickly as possible.<\/p>\n

Scope of impact: Your organization is affected by this event, and all or most of your users are likely affected.<\/p>\n

Start time: Tuesday, February 7, 2023, at 8:25 PM UTC<\/p>\n

Root cause: A portion of infrastructure supporting users' ability to access and send messages in Microsoft Teams is operating below acceptable performance thresholds, resulting in impact.<\/p>\n

Next update by: Wednesday, February 8, 2023, at 1:00 AM UTC<\/p>\n

Published Time: 07.02.2023 22:58:49<\/p>\n

Title: Users may be unable to send messages and create or update meetings in all Microsoft Teams connection methods<\/p>\n

User impact: Users may be unable to send messages and create or update meetings in all Microsoft Teams connection methods.<\/p>\n

More info: Additionally, new Microsoft Teams users may be unable to access the Microsoft Teams client in the desktop and web clients.<\/p>\n

Affected users may also see that Microsoft Teams meetings start with default policies rather than previously set organizer policies.<\/p>\n

Current status: We're investigating issues detected by our monitoring systems indicating that some users are unable to send messages in any Microsoft Teams connection method and some new users are inhibited from accessing Microsoft Teams altogether via the desktop and web clients. Our investigation so far suggests that a portion of infrastructure supporting users' ability to access and send messages in Microsoft Teams is operating below acceptable performance thresholds, resulting in impact. To resolve the issue, we're optimizing this infrastructure and monitoring telemetry to ensure it recovers as expected.<\/p>\n

Scope of impact: Some new users attempting to access the Microsoft Teams desktop and web clients, as well as current users attempting to send messages and create or update meetings in all clients, are affected.<\/p>\n

Start time: Tuesday, February 7, 2023, at 8:25 PM UTC<\/p>\n

Root cause: A portion of infrastructure supporting users' ability to access and send messages in Microsoft Teams is operating below acceptable performance thresholds, resulting in impact.<\/p>\n

Next update by: Wednesday, February 8, 2023, at 12:30 AM UTC<\/p>\n

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

[English]Microsofts E-Mail-Dienst outlook.com ist heute (7. Februar 2023) seit ca. 5:00 Uhr deutscher Zeit wohl weltweit gest\u00f6rt. Es gibt aktuell zwar Indizien, dass die St\u00f6rung zur\u00fcck geht. Aber die Statusseiten von Microsoft 365 oder Outlook 365 melden weiterhin ein Problem … 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":[987],"class_list":["post-277614","post","type-post","status-publish","format-standard","hentry","category-stoerung","tag-storung"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/277614","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=277614"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/277614\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=277614"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=277614"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=277614"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}