>We appreciate your organization’s patience and understanding while we work with urgency to resolve this incident.>As we’ve applied our current ongoing mitigation actions, we’ve observed a surge in outbound call volume from our routing services to our backend servers. This occurs when the backend servers outbound service cannot properly route to the backend machines. We’re continuing to observe heightened volume due to traffic rebalancing actions that we have taken throughout this event. We’re working on multiple workstreams to pinpoint the underlying cause of this traffic influx and address it.>Current actions we are taking include scaling up virtual machines to increase capacity and reduce load. Additionally, we’re querying for machines in a bad state to perform a force sync for our recent network change, which may improve service availability. However, we are encountering issues with the machines being stuck in a bad state, preventing our changes from syncing as expected. We’ll continue to monitor the effectiveness of changes applied so we can determine what refinements are necessary.
God I hope they cancel work tomorrow
>>546138093Is this real? It's poor, unclear writing
>>546138597real looks like it was written by ai
>>546138093>"We have no fucking idea whats going on"
>>546138142Being sent into drone war is better than sharing a room with these.
>>546138093jeeted
>Current status: We’re continuing to pursue multiple workstreams to pinpoint the underlying cause of the traffic influx and advance the recoverability of the backend servers. We’re taking a measured approach to identify and repair affected infrastructure to improve the ability to confirm the developed changes were applied. We’re tracking the results of this approach to verify the servers are showing the anticipated recovery and performance intended.>As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution. Once mitigated, we will provide full details of the root cause, defense-in-depth repair items, and more within a Post-Incident Report.
>>546140701Tldr: we don't know what's causing this network traffic flood but it's not a malicious attack ok relax guy
>>546138093>get put in charge of massive onboarding event at work>email goes down day beforeit's gonna be a clusterfuck tomorrow
>>546140701>We’re taking a measured approach to identify and repair affected infrastructure to improve the ability to confirm the developed changes were applied
The best part is that all the certificates will be out of date the moment it comes back online, flooding every IT guy with "what does this popup mean? I can't send emails" until Microsoft literally has to push an update again to every Outlook client just to fix the certificate issue.
