Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [We are continuing to monitor for any further issues.] has changed as [This incident has been resolved.]. " on alert: "Partial outage of the services in AWS US - West2 region"

Oct 18, 2022 - 12:34 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [A fix has been deployed and we are monitoring the results.] has changed as [We are continuing to monitor for any further issues.]. " on alert: "Partial outage of the services in AWS US - West2 region"
Oct 18, 2022 - 11:27 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING].
Statuspage incident message [We are currently investigating partial services outages impacting a subset of customers on AWS USW-2 region due to Cloud infrastructure high load issues . The root cause has been identified & we are working towards implementing the remediations] has changed as [A fix has been deployed and we are monitoring the results.].
Statuspage incident component [Pipelines] status [partial_outage] has changed as [operational].
Statuspage incident component [Xray] status [partial_outage] has changed as [operational].
Statuspage incident component [Artifactory] status [partial_outage] has changed as [operational]. " on alert: "Partial outage of the services in AWS US - West2 region"

Oct 18, 2022 - 11:14 UTC
Investigating - We are currently investigating partial services outages impacting a subset of customers on AWS USW-2 region due to Cloud infrastructure high load issues . The root cause has been identified & we are working towards implementing the remediations
Oct 18, 2022 - 09:11 UTC
Investigating - Click on [Body.html] attachment for HTML version

Pipelines artifact uploads and downloads failing

Incident status: Monitoring
A fix has been implemented and we are monitoring the results.

Time posted
Mar 18, 06:16 UTC

Components Affected
Pipelines

View 1 previous incident update https://stspg.io/6pkzvgf38fjw

You received this email because you are subscribed to Atlassian Bitbucket's service status notifications.
Manage your subscription: https://bitbucket.status.atlassian.com/subscriptions/wzd3bxhvf137/edit

Mar 18, 2021 - 06:18 UTC
Investigating - Click on [Body.html] attachment for HTML version

Unauthorized Users Added to Marketplace Vendor Accounts from Bug caused by Database Failover

An update has been posted
As communicated in the previous update:

- No billing details were accessed or changed by unauthorized users in any impacted vendor partner account
- No reports and transaction details were accessed or changed by unauthorized users in any impacted vendor partner account
- No new app versions were created by unauthorized users in any vendor partner account

However, we are continuing to investigate and enumerate all unauthorized access to any Marketplace Partner account’s contact information and app details. In the process, we have already reached out directly to a subset of impacted Marketplace partners to communicate the impact to them and will be reaching out to others as we progress.

As no billing details were accessed or changed by unauthorized users in any impacted Partner partner account, our finance teams have started to process the payments for the month of February (due in March).

Up to now we have prioritized understanding the full scope of potential unauthorised access to partner data and communicating this to partners above restoring access to Marketplace Partner admin functionality.

We are now evaluating options to safely restore access to Marketplace Partner functionality, and hope to be able to do this tomorrow ( 18 Mar 2021 ) for the majority of functionality.

We will keep you informed as we progress.

Thank you for your patience and continued support as we work through this sensitive matter.

Time posted
Mar 17, 14:20 UTC

Components Affected
Marketplace - Reporting APIs and dashboards, Marketplace - Vendor management

View 7 previous incident updates https://stspg.io/7h978z5p3l0c

You received this email because you are subscribed to Atlassian Developer's service status notifications.
Manage your subscription: https://developer.status.atlassian.com/subscriptions/ck2ybnl95jjl/edit

Mar 17, 2021 - 14:21 UTC
Investigating - Click on [Body.html] attachment for HTML version

Unauthorized Users Added to Marketplace Vendor Accounts from Bug caused by Database Failover

Incident status: Identified
On March 14th 2021, the Atlassian team discovered unauthorized users were being given access to Marketplace Partner accounts for marketplace.atlassian.com.

At that time, we froze access to all users of partner accounts and halted payment processing in order to properly investigate the scope of the incident. We have since confirmed this activity was happening because of a bug, and not because of malicious activity.

We have also confirmed:
No billing details were accessed or changed by unauthorized users in any impacted vendor account
No reports and transaction details were accessed or changed by unauthorized users in any impacted vendor account
No new app versions were created by unauthorized users in any vendor partner account

Our team is continuing to investigate potential unauthorized access to your vendor account’s contact information and app details.

We will reach out directly to each impacted partner when our investigation is complete. We will also provide further technical details on this incident in a public PIR.

Follow the Atlassian Developer Statuspage for further updates.

Time posted
Mar 17, 01:10 UTC

Components Affected
Marketplace - Reporting APIs and dashboards, Marketplace - Vendor management

View 6 previous incident updates https://stspg.io/7h978z5p3l0c

You received this email because you are subscribed to Atlassian Developer's service status notifications.
Manage your subscription: https://developer.status.atlassian.com/subscriptions/ck2ybnl95jjl/edit

Mar 17, 2021 - 01:10 UTC
Investigating - Click on [Body.html] attachment for HTML version

Unauthorized users were being given access to Marketplace Partner accounts

New incident: Identified
On March 14th 2021, the Atlassian team discovered unauthorized users were being given access to Marketplace Partner accounts for marketplace.atlassian.com.

At that time, we froze access to all users of partner accounts and halted payment processing in order to properly investigate the scope of the incident. We have since confirmed this activity was happening because of a bug, and not because of malicious activity.

We have also confirmed:
No billing details were accessed or changed by unauthorized users in any impacted vendor account
No reports and transaction details were accessed or changed by unauthorized users in any impacted vendor account
No new app versions were created by unauthorized users in any vendor partner account

Our team is continuing to investigate potential unauthorized access to your vendor account’s contact information and app details.

We will reach out directly to each impacted partner when our investigation is complete. We will also provide further technical details on this incident in a public PIR.

Follow the Atlassian Developer Statuspage for further updates.

Time posted
Mar 17, 00:59 UTC

Components Affected
Marketplace - Vendor management

View full incident details https://stspg.io/20slrvttvg68

You received this email because you are subscribed to Atlassian Developer's service status notifications.
Manage your subscription: https://developer.status.atlassian.com/subscriptions/ck2ybnl95jjl/edit

Mar 17, 2021 - 01:03 UTC
Investigating - Click on [Body.html] attachment for HTML version

Bitbucket is experiencing a performance degredation

Incident resolved
The incident has been resolved

Time posted
Mar 16, 17:02 UTC

Components Affected
Website, API, SSH, Git via HTTPS

View 1 previous incident update https://stspg.io/lysc3k96vh7s

You received this email because you are subscribed to Atlassian Bitbucket's service status notifications.
Manage your subscription: https://bitbucket.status.atlassian.com/subscriptions/wzd3bxhvf137/edit

Mar 16, 2021 - 17:04 UTC
Investigating - Click on [Body.html] attachment for HTML version

Bitbucket is experiencing a performance degredation

New incident: Investigating
We are investigating cases of degraded performance for some Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.

Time posted
Mar 16, 15:59 UTC

Components Affected
Website, API, SSH, Git via HTTPS

View full incident details https://stspg.io/lysc3k96vh7s

You received this email because you are subscribed to Atlassian Bitbucket's service status notifications.
Manage your subscription: https://bitbucket.status.atlassian.com/subscriptions/wzd3bxhvf137/edit

Mar 16, 2021 - 16:01 UTC
Investigating - Click on [Body.html] attachment for HTML version

Malicious users in Marketplace vendor account

An update has been posted
The investigation is still underway, Marketplace Partner's admin features will continue to be disabled to prevent any potential abuse while we resolve this.

Traffic on the Marketplace itself continues to operate as normal and customers can continue to evaluate and purchase apps.

We will continue to provide updates on our investigations and fixes as they progress.

Time posted
Mar 16, 08:23 UTC

Components Affected
Marketplace - Reporting APIs and dashboards, Marketplace - Vendor management

View 5 previous incident updates https://stspg.io/7h978z5p3l0c

You received this email because you are subscribed to Atlassian Developer's service status notifications.
Manage your subscription: https://developer.status.atlassian.com/subscriptions/ck2ybnl95jjl/edit

Mar 16, 2021 - 08:24 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance [Opsgenie Reporting & Analytics is under maintenance in EU] is deleted from Statuspage [Atlassian Opsgenie]. " on alert: "Opsgenie Reporting & Analytics is under maintenance in EU"
Mar 16, 2021 - 07:33 UTC
Investigating - We will be undergoing scheduled maintenance during this time.
Mar 15, 2021 - 13:44 UTC
Investigating - Click on [Body.html] attachment for HTML version

Malicious users in Marketplace vendor account

An update has been posted
We are still investigating the root cause, but based on our analysis we believe this to be an application-level bug that caused data corruption.

We are currently investigating how we can safely restore a backup and will keep you informed on further updates.

Traffic on the Marketplace itself continues to operate as normal and customers can continue to evaluate and purchase apps, but the block on all admin functionality on Marketplace for Vendors is still in place

Time posted
Mar 15, 19:46 UTC

Components Affected
Marketplace - Reporting APIs and dashboards, Marketplace - Vendor management

View 4 previous incident updates https://stspg.io/7h978z5p3l0c

You received this email because you are subscribed to Atlassian Developer's service status notifications.
Manage your subscription: https://developer.status.atlassian.com/subscriptions/ck2ybnl95jjl/edit

Mar 15, 2021 - 19:46 UTC
Investigating - Click on [Body.html] attachment for HTML version

Malicious users in Marketplace vendor account

An update has been posted
We are still investigating the issue and the block on all admin functionality on Marketplace for Vendors is still in place, this includes access to vendor reports as well admin-only actions.

Traffic on the Marketplace itself is normal and customers can continue to evaluate and purchase apps.

Time posted
Mar 15, 14:43 UTC

Components Affected
Marketplace - Reporting APIs and dashboards, Marketplace - Vendor management

View 3 previous incident updates https://stspg.io/7h978z5p3l0c

You received this email because you are subscribed to Atlassian Developer's service status notifications.
Manage your subscription: https://developer.status.atlassian.com/subscriptions/ck2ybnl95jjl/edit

Mar 15, 2021 - 14:43 UTC
Investigating - Click on [Body.html] attachment for HTML version

Malicious users in Marketplace vendor account

An update has been posted
We are continuing to investigate this issue.

Time posted
Mar 15, 10:12 UTC

Components Affected
Marketplace - Reporting APIs and dashboards, Marketplace - Vendor management

View 1 previous incident update https://stspg.io/7h978z5p3l0c

You received this email because you are subscribed to Atlassian Developer's service status notifications.
Manage your subscription: https://developer.status.atlassian.com/subscriptions/ck2ybnl95jjl/edit

Mar 15, 2021 - 10:13 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [IN_PROGRESS] has changed as [COMPLETED].
Statuspage scheduled maintenance message [Scheduled maintenance is currently in progress. We will provide updates as necessary.] has changed as [The scheduled maintenance has been completed.].
Statuspage scheduled maintenance component [Azure EU West] status [under_maintenance] has changed as [operational].
Statuspage scheduled maintenance component [Azure Southeast Asia (Singapore)] status [under_maintenance] has changed as [operational]. " on alert: "Maintenance on cloud infrastructure in Azure SEA and Azure EUW"

Mar 07, 2021 - 17:17 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [SCHEDULED] has changed as [IN_PROGRESS].
Statuspage scheduled maintenance message [We will be undergoing scheduled maintenance during this time.] has changed as [Scheduled maintenance is currently in progress. We will provide updates as necessary.].
Statuspage scheduled maintenance component [Azure EU West] status [operational] has changed as [under_maintenance].
Statuspage scheduled maintenance component [Azure Southeast Asia (Singapore)] status [operational] has changed as [under_maintenance]. " on alert: "Maintenance on cloud infrastructure in Azure SEA and Azure EUW"

Mar 07, 2021 - 09:16 UTC
Investigating - We will be undergoing scheduled maintenance during this time.
Mar 07, 2021 - 09:15 UTC
Investigating - HTTP 502 - Bad Gateway
Mar 06, 2021 - 04:27 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [The problem is identified and the fix is sent.] has changed as [The problem is resolved and notification delays are back to normal.].
Following components are added: [Voice Notification Delivery,SMS Notification Delivery,Email Notification Delivery,Mobile Notification Delivery]. " on alert: "We observe increased latency with notifications"

Mar 05, 2021 - 09:58 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [MONITORING].
Statuspage incident message [We're currently investigating the problem and we will provide more information soon.] has changed as [The problem is identified and the fix is sent.]. " on alert: "We observe increased latency with notifications"

Mar 05, 2021 - 09:47 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident impact [NONE] has changed as [MINOR]. " on alert: "We observe increased latency with notifications"
Mar 05, 2021 - 09:08 UTC
Investigating - We're currently investigating the problem and we will provide more information soon.
Mar 05, 2021 - 09:08 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [This issue has been resolved and all the services are operating normally.] has changed as [This issue has been resolved and all the services are operating normally. The problem is mitigated at 14:10 UTC. We will provide detailed impact analysis.]. " on alert: "We observe increased error rates on API"
Mar 03, 2021 - 02:18 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [The issue has been resolved and we are closely monitoring the services.] has changed as [This issue has been resolved and all the services are operating normally.]. " on alert: "We observe increased error rates on API"

Feb 04, 2021 - 15:28 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING].
Statuspage incident message [The problem is related to a customer sending a massive amount of traffic and causing degraded performance.
We have rate-limited the customer requests and observing recovery at the moment.] has changed as [The issue has been resolved and we are closely monitoring the services.].
Statuspage incident component [Incident REST API] status [degraded_performance] has changed as [operational].
Statuspage incident component [Heartbeat REST API] status [degraded_performance] has changed as [operational].
Statuspage incident component [Alert REST API] status [degraded_performance] has changed as [operational]. " on alert: "We observe increased error rates on API"

Feb 04, 2021 - 14:33 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are investigating the increased error rates and we'll be providing more updates shortly.] has changed as [The problem is related to a customer sending a massive amount of traffic and causing degraded performance.
We have rate-limited the customer requests and observing recovery at the moment.].
Statuspage incident component [Incident REST API] status [degraded_performance] has changed as [operational].
Statuspage incident component [Alert REST API] status [degraded_performance] has changed as [operational].
Statuspage incident component [Heartbeat REST API] status [degraded_performance] has changed as [operational]. " on alert: "We observe increased error rates on API"

Feb 04, 2021 - 14:18 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident impact [MINOR] has changed as [MAJOR]. " on alert: "We observe increased error rates on API"
Feb 04, 2021 - 14:17 UTC
Investigating - We are investigating the increased error rates and we'll be providing more updates shortly.
Feb 04, 2021 - 13:41 UTC
Investigating - Click on [Body.html] attachment for HTML version

Sprint name and goal cannot be edited

Incident status: Identified
We have identified the problem and we're working on a fix.

Time posted
Feb 12, 18:55 UTC

Components Affected
Create and edit

View 1 previous incident update https://stspg.io/lhlc942vs6hg

You received this email because you are subscribed to Jira Software's service status notifications.
Manage your subscription: https://jira-software.status.atlassian.com/subscriptions/0p9wt6w5b2q5/edit

Feb 12, 2021 - 18:55 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [We found an issue with a node in the cluster. To resolve this, we remove the faulty node and recovered the services. We are now monitoring the instances for any issues.] has changed as [This incident has been resolved.]. " on alert: "Artifactory and Pipeline services running in degraded mode"

Feb 12, 2021 - 13:06 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING].
Statuspage incident message [We have identified the issue, one of the cluster nodes in this region running in degraded mode due to a resource crunch, we are working to fix the same] has changed as [We found an issue with a node in the cluster. To resolve this, we remove the faulty node and recovered the services. We are now monitoring the instances for any issues.].
Statuspage incident component [AWS Europe Central 1 (Frankfurt)] status [degraded_performance] has changed as [operational]. " on alert: "Artifactory and Pipeline services running in degraded mode"

Feb 12, 2021 - 09:42 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident name [Artifactory,Xray and Pipeline services running in degraded mode, impact is minimal for a very few customers] is updated as [Artifactory,Xray and Pipeline services running in degraded mode, minimal impact for few customers]. " on alert: "Artifactory and Pipeline services running in degraded mode"
Feb 12, 2021 - 09:28 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident name [Artifactory and Pipeline services running in degraded mode] is updated as [Artifactory,Xray and Pipeline services running in degraded mode, impact is minimal for a very few customers]. " on alert: "Artifactory and Pipeline services running in degraded mode"
Feb 12, 2021 - 09:28 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are currently investigating this issue.] has changed as [We have identified the issue, one of the cluster nodes in this region running in degraded mode due to a resource crunch, we are working to fix the same]. " on alert: "Artifactory and Pipeline services running in degraded mode"

Feb 12, 2021 - 09:27 UTC
Investigating - We are currently investigating this issue.
Feb 12, 2021 - 09:24 UTC
Investigating - Click on [Body.html] attachment for HTML version

Unable to view attachments in Jira old issue view

Incident status: Identified
The issue has been identified and a fix is being implemented.

Time posted
Feb 12, 04:29 UTC

Components Affected
Viewing content

View 1 previous incident update https://stspg.io/23pl639rk0wd

You received this email because you are subscribed to Jira Software's service status notifications.
Manage your subscription: https://jira-software.status.atlassian.com/subscriptions/0p9wt6w5b2q5/edit

Feb 12, 2021 - 04:30 UTC
Investigating - Click on [Body.html] attachment for HTML version

User management syncs are affected across all products

Incident resolved
This incident has been resolved.

Time posted
Feb 11, 19:10 PST

Components Affected
Signup

View 1 previous incident update http://mstspg.co/mb74pm07ssw0

You received this email because you are subscribed to Atlassian Statuspage's service status notifications.
Manage your subscription: http://metastatuspage.com/subscriptions/22wj99zrgcdn/edit

Feb 12, 2021 - 03:19 UTC
Investigating - Click on [Body.html] attachment for HTML version

User Management Syncs are affected across all products

Incident resolved
Impact on User Management Syncs has been mitigated.

Time posted
Feb 12, 03:13 UTC


View 2 previous incident updates https://stspg.io/rxfktmd4yswp

You received this email because you are subscribed to Trello's service status notifications.
Manage your subscription: https://trello.status.atlassian.com/subscriptions/9q4tjz0947gl/edit

Feb 12, 2021 - 03:15 UTC
Investigating - Click on [Body.html] attachment for HTML version

User Management Syncs are affected across all products

Incident resolved
Impact on User Management Syncs has been mitigated.

Time posted
Feb 12, 03:13 UTC


View 2 previous incident updates https://stspg.io/3shqxq80y731

You received this email because you are subscribed to Jira Software's service status notifications.
Manage your subscription: https://jira-software.status.atlassian.com/subscriptions/0p9wt6w5b2q5/edit

Feb 12, 2021 - 03:14 UTC
Investigating - Click on [Body.html] attachment for HTML version

User Management Syncs are affected across all products

Incident resolved
Impact on User Management Syncs has been mitigated.

Time posted
Feb 12, 03:13 UTC


View 2 previous incident updates https://stspg.io/fh7sdj5nzwzj

You received this email because you are subscribed to Jira Service Management's service status notifications.
Manage your subscription: https://jira-service-management.status.atlassian.com/subscriptions/qlycjkkd3217/edit

Feb 12, 2021 - 03:14 UTC
Investigating - Click on [Body.html] attachment for HTML version

User Management Syncs are affected across all products

Incident resolved
Impact on User Management Syncs has been mitigated.

Time posted
Feb 12, 03:13 UTC


View 2 previous incident updates https://stspg.io/ydlp8ls1n0rx

You received this email because you are subscribed to Confluence's service status notifications.
Manage your subscription: https://confluence.status.atlassian.com/subscriptions/f8w17w5n04c7/edit

Feb 12, 2021 - 03:14 UTC
Investigating - Click on [Body.html] attachment for HTML version

User Management Syncs are affected across all products

Incident resolved
Impact on User Management Syncs has been mitigated.

Time posted
Feb 12, 03:13 UTC


View 2 previous incident updates https://stspg.io/rz5w3315y46z

You received this email because you are subscribed to Opsgenie's service status notifications.
Manage your subscription: https://opsgenie.status.atlassian.com/subscriptions/skfvbthmf79d/edit

Feb 12, 2021 - 03:14 UTC
Investigating - Click on [Body.html] attachment for HTML version

User Management Syncs are affected across all products

Incident resolved
Impact on User Management Syncs has been mitigated.

Time posted
Feb 12, 03:13 UTC


View 2 previous incident updates https://stspg.io/sd3bmj91hd0s

You received this email because you are subscribed to Atlassian Access's service status notifications.
Manage your subscription: https://access.status.atlassian.com/subscriptions/gg6cjdzzsw18/edit

Feb 12, 2021 - 03:13 UTC
Investigating - Click on [Body.html] attachment for HTML version

User management syncs are affected across all products

New incident: Investigating
We are investigating issues in syncing User Management changes to Statuspage. We will provide more details within the next hour.

Time posted
Feb 11, 19:05 PST

Components Affected
Signup

View full incident details http://mstspg.co/mb74pm07ssw0

You received this email because you are subscribed to Atlassian Statuspage's service status notifications.
Manage your subscription: http://metastatuspage.com/subscriptions/22wj99zrgcdn/edit

Feb 12, 2021 - 03:12 UTC
Investigating - Click on [Body.html] attachment for HTML version

User Management Syncs are affected across all products

An update has been posted
We continue investigating issues with syncing User Management changes to products. We will provide more details in an hour.

Time posted
Feb 12, 02:28 UTC


View 1 previous incident update https://stspg.io/3shqxq80y731

You received this email because you are subscribed to Jira Software's service status notifications.
Manage your subscription: https://jira-software.status.atlassian.com/subscriptions/0p9wt6w5b2q5/edit

Feb 12, 2021 - 02:29 UTC
Investigating - Click on [Body.html] attachment for HTML version

User Management Syncs are affected across all products

An update has been posted
We continue investigating issues with syncing User Management changes to products. We will provide more details in an hour.

Time posted
Feb 12, 02:28 UTC


View 1 previous incident update https://stspg.io/rxfktmd4yswp

You received this email because you are subscribed to Trello's service status notifications.
Manage your subscription: https://trello.status.atlassian.com/subscriptions/9q4tjz0947gl/edit

Feb 12, 2021 - 02:29 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [RESOLVED].
Statuspage incident message [We continue to work on resolving the managed account access problems identified for Confluence, Jira Core, Jira Service Management, Jira Software, Opsgenie, Trello, and Atlassian Bitbucket. We have identified the root cause and have performed corrective actions against a handful of customer accounts and expect full recovery on these shortly with a wider rollout to the other customer accounts impacted.

Additional updates will be posted when available.] has changed as [Between 10/Feb/21 03:15 UTC to 10/Feb/21 23:20 UTC, we experienced login issues for a subset of managed accounts for Confluence, Jira Core, Jira Service Management, Jira Software, and Trello. The issue has been resolved and the impacted organizations and related products are operating normally.]. " on alert: "Login issues with single sign on account"

Feb 11, 2021 - 15:33 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We have identified an incident that has resulted in a small number of customers having been locked out of their accounts as a result of the incident. Atlassian has identified that this outage is caused by the incident and is not a security related issue and there is no data loss or any accounts have been compromised.

We are actively working to resolve this outage. We will post more information here in the next 2 hours] has changed as [We continue to work on resolving the managed account access problems identified for Confluence, Jira Core, Jira Service Management, Jira Software, Opsgenie, Trello, and Atlassian Bitbucket. We have identified the root cause and have performed corrective actions against a handful of customer accounts and expect full recovery on these shortly with a wider rollout to the other customer accounts impacted.

Additional updates will be posted when available.]. " on alert: "Login issues with single sign on account"

Feb 10, 2021 - 21:08 UTC
Investigating - We have identified an incident that has resulted in a small number of customers having been locked out of their accounts as a result of the incident. Atlassian has identified that this outage is caused by the incident and is not a security related issue and there is no data loss or any accounts have been compromised.

We are actively working to resolve this outage. We will post more information here in the next 2 hours

Feb 10, 2021 - 19:26 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [RESOLVED].
Statuspage incident message [This issue has been resolved and verified against the affected Orgs.] has changed as [This incident has been resolved.]. " on alert: "Prior Claimed Domains are reporting as Unclaimed against Atlassian Orsanizations"

Feb 11, 2021 - 15:26 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We have taken all the steps required to resolve the incident. We are completing the verification of the resolution on all affected Orgs to mark the incident as resolved.] has changed as [This issue has been resolved and verified against the affected Orgs.].
Statuspage incident component [Domain Claims] status [partial_outage] has changed as [operational]. " on alert: "Prior Claimed Domains are reporting as Unclaimed against Atlassian Orsanizations"

Feb 11, 2021 - 04:32 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We continue to work on resolving the issue. Currently, we have restored some of the organizations and are in the process of restoring the remaining Organizations to a good state. The work underway includes some Organizations whose SAML configuration may not be working for SSO. The team is working on corrective actions and we expect to fully recover shortly.

Additional updates will be posted when available.] has changed as [We have taken all the steps required to resolve the incident. We are completing the verification of the resolution on all affected Orgs to mark the incident as resolved.]. " on alert: "Prior Claimed Domains are reporting as Unclaimed against Atlassian Orsanizations"

Feb 11, 2021 - 04:12 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We continue to work on resolving the unclaimed domain issues against the organizations that should otherwise have claimed domains. This includes domain claims that are marked as "superseded". Team has identified the root cause and have performed corrective actions against a handful of organizations' claimed domains reverting back to the last valid state. Same team is working on corrective actions for the other impacted organizations and expect full recovery shortly.

Additional updates will be posted when available.] has changed as [We continue to work on resolving the issue. Currently, we have restored some of the organizations and are in the process of restoring the remaining Organizations to a good state. The work underway includes some Organizations whose SAML configuration may not be working for SSO. The team is working on corrective actions and we expect to fully recover shortly.

Additional updates will be posted when available.]. " on alert: "Prior Claimed Domains are reporting as Unclaimed against Atlassian Orsanizations"

Feb 10, 2021 - 23:37 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are currently investigating an issue where a subset of domains (and thus organisations) that were impacted by the earlier incident are still facing issues with their prior domain claims not being shown and resulting users may be locked out of associated products. Atlassian has identified that this outage is caused by the incident and is not a security related issue and there is no data loss or any of the associated accounts have been compromised.

We are actively working to resolve this outage. We will post more information here in the next 2 hours] has changed as [We continue to work on resolving the unclaimed domain issues against the organizations that should otherwise have claimed domains. This includes domain claims that are marked as "superseded". Team has identified the root cause and have performed corrective actions against a handful of organizations' claimed domains reverting back to the last valid state. Same team is working on corrective actions for the other impacted organizations and expect full recovery shortly.

Additional updates will be posted when available.]. " on alert: "Prior Claimed Domains are reporting as Unclaimed against Atlassian Orsanizations"

Feb 10, 2021 - 21:12 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident name [Prior Claimed Domains are reporting as Unclaimed against Atlassian Orsanizations] is updated as [Prior Claimed Domains are reporting as Unclaimed against Atlassian Organizations]. " on alert: "Prior Claimed Domains are reporting as Unclaimed against Atlassian Orsanizations"
Feb 10, 2021 - 21:08 UTC
Investigating - We are currently investigating an issue where a subset of domains (and thus organisations) that were impacted by the earlier incident are still facing issues with their prior domain claims not being shown and resulting users may be locked out of associated products. Atlassian has identified that this outage is caused by the incident and is not a security related issue and there is no data loss or any of the associated accounts have been compromised.

We are actively working to resolve this outage. We will post more information here in the next 2 hours

Feb 10, 2021 - 19:33 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [RESOLVED].
Statuspage incident message [We continue to work on resolving the managed account access problems identified for Confluence, Jira Core, Jira Service Management, Jira Software, Opsgenie, Trello, and Atlassian Bitbucket. We have identified the root cause and have performed corrective actions against a handful of customer accounts and expect full recovery on these shortly with a wider rollout to the other customer accounts impacted.

Additional updates will be posted when available.] has changed as [This incident has been resolved.]. " on alert: "Login issues with single sign on account"

Feb 11, 2021 - 08:05 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We have identified an incident that has resulted in a small number of customers having been locked out of their accounts as a result of the incident. Atlassian has identified that this outage is caused by the incident and is not a security related issue and there is no data loss or any accounts have been compromised.

We are actively working to resolve this outage. We will post more information here in the next 2 hours] has changed as [We continue to work on resolving the managed account access problems identified for Confluence, Jira Core, Jira Service Management, Jira Software, Opsgenie, Trello, and Atlassian Bitbucket. We have identified the root cause and have performed corrective actions against a handful of customer accounts and expect full recovery on these shortly with a wider rollout to the other customer accounts impacted.

Additional updates will be posted when available.]. " on alert: "Login issues with single sign on account"

Feb 10, 2021 - 21:08 UTC
Investigating - We have identified an incident that has resulted in a small number of customers having been locked out of their accounts as a result of the incident. Atlassian has identified that this outage is caused by the incident and is not a security related issue and there is no data loss or any accounts have been compromised.

We are actively working to resolve this outage. We will post more information here in the next 2 hours

Feb 10, 2021 - 19:25 UTC
Investigating - Click on [Body.html] attachment for HTML version

Error in copy page hierarchy API

An update has been posted
The team estimates the issue will be resolved by 11:00 PST.

Time posted
Feb 11, 02:05 UTC

Components Affected
APIs - Confluence Cloud APIs

View 1 previous incident update https://stspg.io/gtwn4kqqh1wy

You received this email because you are subscribed to Atlassian Developer's service status notifications.
Manage your subscription: https://developer.status.atlassian.com/subscriptions/ck2ybnl95jjl/edit

Feb 11, 2021 - 02:07 UTC
Investigating - Click on [Body.html] attachment for HTML version

Prior Claimed Domains are reporting as Unclaimed against Atlassian Organizations

Incident status: Identified
We continue to work on resolving the unclaimed domain issues against the organizations that should otherwise have claimed domains. This includes domain claims that are marked as "superseded". Team has identified the root cause and have performed corrective actions against a handful of organizations' claimed domains reverting back to the last valid state. Same team is working on corrective actions for the other impacted organizations and expect full recovery shortly.

Additional updates will be posted when available.

Time posted
Feb 10, 21:12 UTC

Components Affected
Domain Claims

View 1 previous incident update https://stspg.io/w61bypt9g22m

You received this email because you are subscribed to Atlassian Access's service status notifications.
Manage your subscription: https://access.status.atlassian.com/subscriptions/gg6cjdzzsw18/edit

Feb 10, 2021 - 21:12 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [RESOLVED].
Statuspage incident message [We have identified an incident that has caused a trigger of false email notifications to a small number of customers, stating an update has been initiated by the customer admin. A subset of these customers has also been locked out of their accounts as a result of the incident.
Atlassian has identified that this outage and a related email sent is caused by the incident and is not a security-related issue.
We are actively working to resolve this outage and will post more information here in the next 2 hours.] has changed as [Between 9 Feb 2021 18:25 UTC to 10 Feb 2021 13:00 UTC, a subset of customers were experiencing issues with Single Sign On and a false Managed Account email notification for their account access to Confluence, Jira Core, Jira Service Management, Jira Software, Opsgenie, Trello, and Atlassian Bitbucket. The issue has been resolved and the service is operating normally.].
Statuspage incident component [Domain Claims] status [degraded_performance] has changed as [operational]. " on alert: "Accounts of some domains were incorrectly claimed within an Atlassian Organisation"

Feb 10, 2021 - 13:39 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are currently investigating an issue where accounts of some domains were incorrectly claimed within an Atlassian Organisation. This also caused a bulk update of users via email with a subject “Your organization now manages your account”.] has changed as [We have identified an incident that has caused a trigger of false email notifications to a small number of customers, stating an update has been initiated by the customer admin. A subset of these customers has also been locked out of their accounts as a result of the incident.
Atlassian has identified that this outage and a related email sent is caused by the incident and is not a security-related issue.
We are actively working to resolve this outage and will post more information here in the next 2 hours.]. " on alert: "Accounts of some domains were incorrectly claimed within an Atlassian Organisation"

Feb 10, 2021 - 13:05 UTC
Investigating - We are currently investigating an issue where accounts of some domains were incorrectly claimed within an Atlassian Organisation. This also caused a bulk update of users via email with a subject “Your organization now manages your account”.
Feb 10, 2021 - 06:00 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [RESOLVED].
Statuspage incident message [We have identified an incident that has caused a trigger of false email notifications to a small number of customers, stating an update has been initiated by the customer admin. A subset of these customers have also been locked out of their accounts as a result of the incident . Atlassian has identified that this outage and email set is caused by the incident and is not a security related issue.

We are actively working to resolve this outage and related email sent. We will post more information here in the next 2 hours] has changed as [Between 9 Feb 2021 18:25 UTC to 10 Feb 2021 13:00 UTC, a subset of customers were experiencing issues with Single Sign On and a false Managed Account email notification for their account access to Confluence, Jira Core, Jira Service Management, Jira Software, Opsgenie, Trello, and Atlassian Bitbucket. The issue has been resolved and the service is operating normally.]. " on alert: "Login issues with single sign on account"

Feb 10, 2021 - 13:37 UTC
Investigating - We have identified an incident that has caused a trigger of false email notifications to a small number of customers, stating an update has been initiated by the customer admin. A subset of these customers have also been locked out of their accounts as a result of the incident . Atlassian has identified that this outage and email set is caused by the incident and is not a security related issue.

We are actively working to resolve this outage and related email sent. We will post more information here in the next 2 hours

Feb 10, 2021 - 12:23 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [RESOLVED].
Statuspage incident message [We have identified an incident that has caused a trigger of false email notifications to a small number of customers, stating an update has been initiated by the customer admin. A subset of these customers have also been locked out of their accounts as a result of the incident . Atlassian has identified that this outage and email set is caused by the incident and is not a security related issue.

We are actively working to resolve this outage and related email sent. We will post more information here in the next 2 hours] has changed as [Between 9 Feb 2021 18:25 UTC to 10 Feb 2021 13:00 UTC, a subset of customers were experiencing issues with Single Sign On and a false Managed Account email notification for their account access to Confluence, Jira Core, Jira Service Management, Jira Software, Opsgenie, Trello, and Atlassian Bitbucket. The issue has been resolved and the service is operating normally.]. " on alert: "Login issues with single sign on account"

Feb 10, 2021 - 13:37 UTC
Investigating - We have identified an incident that has caused a trigger of false email notifications to a small number of customers, stating an update has been initiated by the customer admin. A subset of these customers have also been locked out of their accounts as a result of the incident . Atlassian has identified that this outage and email set is caused by the incident and is not a security related issue.

We are actively working to resolve this outage and related email sent. We will post more information here in the next 2 hours

Feb 10, 2021 - 12:24 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [IN_PROGRESS] has changed as [COMPLETED].
Statuspage scheduled maintenance message [Scheduled maintenance is currently in progress. We will provide updates as necessary.] has changed as [The scheduled maintenance has been completed.].
Statuspage scheduled maintenance component [Signup] status [under_maintenance] has changed as [operational].
Statuspage scheduled maintenance component [Signup, Login & Authorization] status [under_maintenance] has changed as [operational].
Statuspage scheduled maintenance component [Signup, Login & Authorization] status [under_maintenance] has changed as [operational].
Statuspage scheduled maintenance component [Signup] status [under_maintenance] has changed as [operational]. " on alert: "Authentication systems maintenance"

Feb 07, 2021 - 06:02 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [SCHEDULED] has changed as [IN_PROGRESS].
Statuspage scheduled maintenance message [On Sunday, 7th February 2021, from 05:00 am to 06:00 am UTC, there will be a scheduled maintenance period. During the maintenance period for up to 90 seconds some customers will experience degraded login and signup functionality across Atlassian Cloud. Atlassian Ecosystem Cloud Apps may still display UI but will fail to successfully perform user operation.] has changed as [Scheduled maintenance is currently in progress. We will provide updates as necessary.].
Statuspage scheduled maintenance component [Signup] status [operational] has changed as [under_maintenance].
Statuspage scheduled maintenance component [Signup, Login & Authorization] status [operational] has changed as [under_maintenance].
Statuspage scheduled maintenance component [Signup, Login & Authorization] status [operational] has changed as [under_maintenance].
Statuspage scheduled maintenance component [Signup] status [operational] has changed as [under_maintenance]. " on alert: "Authentication systems maintenance"

Feb 07, 2021 - 05:01 UTC
Investigating - On Sunday, 7th February 2021, from 05:00 am to 06:00 am UTC, there will be a scheduled maintenance period. During the maintenance period for up to 90 seconds some customers will experience degraded login and signup functionality across Atlassian Cloud. Atlassian Ecosystem Cloud Apps may still display UI but will fail to successfully perform user operation.
Feb 04, 2021 - 00:20 UTC
Investigating - Click on [Body.html] attachment for HTML version

We observe increased error rates on API

Incident status: Monitoring
The issue has been resolved and we are closely monitoring the services.

Time posted
Feb 4, 14:33 UTC

Components Affected
US - Incident REST API, US - Alert REST API, US - Heartbeat REST API, EU - Incident REST API, EU - Alert REST API and 1 more component.

View 2 previous incident updates https://stspg.io/cjgft9rkf0mq

You received this email because you are subscribed to Opsgenie's service status notifications.
Manage your subscription: https://opsgenie.status.atlassian.com/subscriptions/skfvbthmf79d/edit

Feb 04, 2021 - 14:33 UTC
Investigating - Click on [Body.html] attachment for HTML version

We observe increased error rates on API

Incident status: Identified
The problem is related to a customer sending a massive amount of traffic and causing degraded performance.
We have rate-limited the customer requests and observing recovery at the moment.

Time posted
Feb 4, 14:18 UTC

Components Affected
US - Incident REST API, US - Alert REST API, US - Heartbeat REST API, EU - Incident REST API, EU - Alert REST API and 1 more component.

View 1 previous incident update https://stspg.io/cjgft9rkf0mq

You received this email because you are subscribed to Opsgenie's service status notifications.
Manage your subscription: https://opsgenie.status.atlassian.com/subscriptions/skfvbthmf79d/edit

Feb 04, 2021 - 14:18 UTC
Investigating - Click on [Body.html] attachment for HTML version

We observe increased error rates on API

New incident: Investigating
We are investigating the increased error rates and we'll be providing more updates shortly.

Time posted
Feb 4, 13:41 UTC

Components Affected
US - Incident REST API, US - Alert REST API, US - Heartbeat REST API, EU - Incident REST API, EU - Alert REST API and 1 more component.

View full incident details https://stspg.io/cjgft9rkf0mq

You received this email because you are subscribed to Opsgenie's service status notifications.
Manage your subscription: https://opsgenie.status.atlassian.com/subscriptions/skfvbthmf79d/edit

Feb 04, 2021 - 13:41 UTC
Investigating - Click on [Body.html] attachment for HTML version

Broken views when using Safari browser

An update has been posted
We are still rolling out the fix for this issue but we are no longer treating it as an incident due to the very low impact.

Time posted
Feb 4, 05:47 UTC

Components Affected
View Content, Create and Edit

View 3 previous incident updates https://stspg.io/hp24qy8zr02f

You received this email because you are subscribed to Confluence's service status notifications.
Manage your subscription: https://confluence.status.atlassian.com/subscriptions/f8w17w5n04c7/edit

Feb 04, 2021 - 05:47 UTC
Investigating - Click on [Body.html] attachment for HTML version

Broken views when using Safari browser

An update has been posted
Due to the very low impact, we are no longer treating this as an incident but will continue to work on a fix.

Time posted
Feb 3, 21:46 UTC

Components Affected
Website

View 3 previous incident updates https://stspg.io/mhh3nxvkdsm3

You received this email because you are subscribed to Atlassian Bitbucket's service status notifications.
Manage your subscription: https://bitbucket.status.atlassian.com/subscriptions/wzd3bxhvf137/edit

Feb 03, 2021 - 21:47 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We are rolling out the fix to the Pipeline servers in the region.] has changed as [We are removing the component with degraded performance and working on stabilizing the infrastructure.]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"
May 14, 2020 - 18:18 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We have identified an issue with the underlying component which is used by the Pipelines service. Currently we are working on a fix to mitigate the situation.] has changed as [We are rolling out the fix to the Pipeline servers in the region.]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"
May 13, 2020 - 14:09 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [IDENTIFIED].
Statuspage incident message [We are continuing to monitor for any further issues.] has changed as [We have identified an issue with the underlying component which is used by the Pipelines service. Currently we are working on a fix to mitigate the situation.]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"

May 13, 2020 - 08:03 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident impact [NONE] has changed as [MINOR]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"
May 13, 2020 - 08:03 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [JFrog Pipelines background services are operating normally for the past 12h.
There was an issue with our underlying message-broker system where Pipelines users experienced intermittent issues.
We are continuing to monitor their health.
In case you are facing any issues, please consider contacting JFrog Support at https://support.jfrog.com/] has changed as [We are continuing to monitor for any further issues.].
Statuspage incident component [AWS US East 1 (N. Virginia)] status [operational] has changed as [partial_outage]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"

May 13, 2020 - 08:00 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident impact [MINOR] has changed as [NONE]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"
May 12, 2020 - 20:12 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We are continuing to monitor for any further issues.] has changed as [JFrog Pipelines background services are operating normally for the past 12h.
There was an issue with our underlying message-broker system where Pipelines users experienced intermittent issues.
We are continuing to monitor their health.
In case you are facing any issues, please consider contacting JFrog Support at https://support.jfrog.com/]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"

May 12, 2020 - 18:14 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [A fix has been implemented and we are monitoring the results.] has changed as [We are continuing to monitor for any further issues.].
Statuspage incident component [AWS US East 1 (N. Virginia)] status [partial_outage] has changed as [operational]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"

May 12, 2020 - 07:26 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident name [Pipelines 503 errors in US east 1 (N.Virginia) region] is updated as [JFrog Cloud Platform experiencing intermittent issues with Pipelines in US east 1 (N.Virginia) region]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"
May 12, 2020 - 07:16 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident update request sent with no changes on fields " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"
May 12, 2020 - 07:15 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident impact [MAJOR] has changed as [MINOR]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"
May 12, 2020 - 07:10 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [MONITORING].
Statuspage incident message [We are continuing to investigate this issue.] has changed as [A fix has been implemented and we are monitoring the results.]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"

May 12, 2020 - 07:08 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We are investigating a recurrence of these issues.] has changed as [We are continuing to investigate this issue.]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"
May 11, 2020 - 17:23 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [INVESTIGATING].
Statuspage incident message [A fix has been implemented and we are monitoring the results.] has changed as [We are investigating a recurrence of these issues.]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"

May 11, 2020 - 16:06 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"
May 11, 2020 - 13:44 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING].
Statuspage incident message [The issue has been identified and a fix is being implemented.] has changed as [A fix has been implemented and we are monitoring the results.]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"

May 11, 2020 - 10:44 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident update request sent with no changes on fields " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"
May 11, 2020 - 09:42 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are currently investigating this issue.] has changed as [The issue has been identified and a fix is being implemented.]. " on alert: "Pipelines 503 errors in US east 1 (N.Virginia) region"

May 11, 2020 - 09:33 UTC
Investigating - We are currently investigating this issue.
May 11, 2020 - 06:41 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 14, 2020 - 13:32 UTC
Investigating - Click on [Body.html] attachment for HTML version

Exchange Online service alert












Incident information

Title: Can't access the Exchange Online service
ID: EX212990



Status
Investigating


Details
Title: Can't access the Exchange Online service
User Impact: Users may be unable to sign into the Exchange Online service.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 14, 2020 - 01:42 UTC
Investigating - Click on [Body.html] attachment for HTML version

Exchange Online service alert












Incident information

Title: Emails from iOS devices that are forwarded with an attachment were being quarantined
ID: EX213204



Status
Service Restored


Details
Title: Emails from iOS devices that are forwarded with an attachment were being quarantined
User Impact: Users may have been unable to send emails if they were forwarded with an attachment from an iOS device.
More info: This issue only affected iOS device with the build version 13.4.1.
Final status: We've created and tested a fix to whitelist affected emails, this has deployed throughout the environment, which has remediated impact for future emails. Administrators will need to release any remaining quarantined email messages manually to fully remediate impact.
Scope of impact: This issue impacted users forwarding emails, with attachments, from their iOS device that was on build number 13.4.1.
Start time: Thursday, May 14, 2020, at 4:30 AM UTC
End time: Thursday, May 14, 2020, at 10:31 AM UTC
Root cause: An iOS update, build version 13.4.1, caused forwarded emails with attachments to be caught in quarantine.
This is the final update for the event.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 14, 2020 - 12:26 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 14, 2020 - 11:19 UTC
Investigating - Click on [Body.html] attachment for HTML version

Exchange Online service alert












Incident information

Title: Emails from iOS devices that are forwarded with an attachment are being quarantined
ID: EX213204



Status
Service Degradation


Details
Title: Emails from iOS devices that are forwarded with an attachment are being quarantined
User Impact: Users may be unable to send emails if they are forwarded with an attachment from an iOS device.
More info: This issue only affects iOS device with the build version 13.4.1.
Current status: We've determined that emails being forwarded, with an attachment, from iOS devices with the build version 13.4.1 are the messages that are being caught in quarantine. We're creating a fix to whitelist these emails to prevent future messages being held.
Scope of impact: This issue impacts users forwarding emails, with attachments, from their iOS device that is on build number 13.4.1.
Next update by: Thursday, May 14, 2020, at 12:30 PM UTC



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 14, 2020 - 10:02 UTC
Investigating - Check Name : Ping-Office-Fremont-ISP-Gateway
Hostname : 157.22.218.1
URL :
Check Type : PING

Description : Timeout
Long Description : Time to live exceeded

Time (UTC) : 2020-05-13T21:23:35
Previous State / Current State : UP / DOWN
Tags : [network-office-isp-gw]

Check Params : {basic_auth=false, hostname=157.22.218.1, ipv6=false, responsetime_threshold=30000}

May 13, 2020 - 21:23 UTC
Investigating - Click on [Body.html] attachment for HTML version

Exchange Online service alert












Incident information

Title: Multiple credential prompts in the Outlook client
ID: EX212047



Status
Post-Incident Report Published


Details
A post-incident report has been published.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 13, 2020 - 20:49 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 13, 2020 - 19:56 UTC
Investigating - Click on [Body.html] attachment for HTML version

Exchange Online service alert












Incident information

Title: All users may be unable to access the Exchange Online service
ID: EX212990



Status
Service Restored


Details
Title: All users may be unable to access the Exchange Online service
User Impact: Users may have been unable to sign in to Outlook on the web.
More info: Users may have encountered an error with the following message: "AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: 'e48d4214-364e-4731-b2b6-47dabf529218'" and/or other general AADSTS errors related to sign-in.
Final status: We've completed the rollback of the impacting change successfully and users should now be able to successfully sign in to Outlook on the web.
Scope of impact: This issue may have potentially affected any user.
Start time: Wednesday, May 13, 2020, at 4:22 PM UTC
End time: Wednesday, May 13, 2020, at 6:45 PM UTC
Root cause: A recent change included a code regression that resulted in users experiencing authentication failures.
Next steps:
- We're reviewing our deployment and provisioning procedures to help prevent similar problems in the future.
We'll publish a post-incident report within five business days.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 13, 2020 - 19:46 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "Reports of issues joining meetings"
May 13, 2020 - 17:10 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [Our team has identified the root cause as a capacity issue in a portion of a data center due to extremely high volumes of usage in a particular geographic area, leading some participants to have issues with joining meetings and packet loss. This was resolved by reallocating capacity. We will continue to monitor to ensure no further operational impact.] has changed as [Our team has resolved the issue impacting some Zoom Meetings participants.]. " on alert: "Reports of issues joining meetings"

May 13, 2020 - 16:52 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING].
Statuspage incident message [We have received a few reports that Zoom meetings participants may have experienced intermittent issues joining meetings. Our team has identified and is working to confirm resolution of the issue. We will continue to monitor to ensure no further operational impact.] has changed as [Our team has identified the root cause as a capacity issue in a portion of a data center due to extremely high volumes of usage in a particular geographic area, leading some participants to have issues with joining meetings and packet loss. This was resolved by reallocating capacity. We will continue to monitor to ensure no further operational impact.]. " on alert: "Reports of issues joining meetings"

May 13, 2020 - 16:36 UTC
Investigating - We have received a few reports that Zoom meetings participants may have experienced intermittent issues joining meetings. Our team has identified and is working to confirm resolution of the issue. We will continue to monitor to ensure no further operational impact.
May 13, 2020 - 16:09 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [The issue has been identified and fixed, all services should now be restored. We will continue to monitor this incident for the next 2 hours before resolving.] has changed as [This incident has been resolved.].
Statuspage incident component [Sydney, AU] status [major_outage] has changed as [operational]. " on alert: "Outbound calls from Fuze"

May 13, 2020 - 03:48 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [MONITORING].
Statuspage incident message [We are currently investigating an issue where users can't make or receive calls through Fuze. We are working on identifying the problem, and will update this incident as more information comes to hand.] has changed as [The issue has been identified and fixed, all services should now be restored. We will continue to monitor this incident for the next 2 hours before resolving.]. " on alert: "Outbound calls from Fuze"

May 13, 2020 - 01:23 UTC
Investigating - We are currently investigating an issue where users can't make or receive calls through Fuze. We are working on identifying the problem, and will update this incident as more information comes to hand.
May 13, 2020 - 00:47 UTC
Update - [Comment from Opsgenie]System noted: "Incident [Test] is deleted from Statuspage [Atlassian BitBucket Cloud]. " on alert: "Test"
May 13, 2020 - 03:30 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident impact [MAJOR] has changed as [MINOR]. " on alert: "Test"
May 13, 2020 - 03:27 UTC
Investigating - This is a test
May 13, 2020 - 03:27 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident impact [NONE] has changed as [MINOR]. " on alert: "Slack messages could not be properly sent to slack channels"
May 13, 2020 - 01:16 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident update request sent with no changes on fields " on alert: "Slack messages could not be properly sent to slack channels"
May 13, 2020 - 01:15 UTC
Investigating - Due to an outage in Slack, we could not successfully deliver alert action related messages to relevant slack channels configured via slack integration between May 12, 11:52 pm and May 13, 12:30 am UTC.
May 13, 2020 - 01:12 UTC
Investigating - What are we doing?
Fuze is performing a mandatory update to our SMS/MMS infrastructure to optimize service.

Who is affected?
Users who are attempting to send SMS/MMS messages throughout the specified maintenance window.

When are we doing this?
Start: Monday, May 18th 22:00 EST
End: Monday, May 18th 22:30 EST

What will you experience during the work?
You may experience brief interruptions of SMS/MMS service throughout this 30 minute window.

What do you need to do?
If you experience any issues with SMS/MMS during this time we recommend waiting up to 60 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131

or visit our support page at fuzecommunity.force.com/support.

May 12, 2020 - 21:14 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [RESOLVED].
Statuspage incident message [Our engineering team has identified the issue and has corrected it. The system is working to clear the backlog recording within the next 24 hours.] has changed as [This incident has been resolved].
Statuspage incident component [Cloud Recording] status [degraded_performance] has changed as [operational]. " on alert: "Cloud recording and transcription processing delays"

May 12, 2020 - 17:21 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We are currently seeing higher than normal cloud recording and transcription processing times. The operations and engineering teams are working to resolve the issue.] has changed as [Our engineering team has identified the issue and has corrected it. The system is working to clear the backlog recording within the next 24 hours.]. " on alert: "Cloud recording and transcription processing delays"
May 11, 2020 - 23:42 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident update request sent with no changes on fields " on alert: "Cloud recording and transcription processing delays"
May 11, 2020 - 16:18 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "Cloud recording and transcription processing delays"
May 11, 2020 - 13:43 UTC
Investigating - We are currently seeing higher than normal cloud recording and transcription processing times. The operations and engineering teams are working to resolve the issue.
May 08, 2020 - 18:56 UTC
Investigating - Click on [Body.html] attachment for HTML version

Exchange Online service alert












Incident information

Title: Any user may potentially be unable to receive email through moderated distribution groups intermittently
ID: EX211611



Status
Service Restored


Details
Title: Any user may potentially be unable to receive email through moderated distribution groups intermittently
User Impact: Users may have been unable to receive email sent to distribution groups that require moderator approval.
Final status: We've confirmed that our fix has saturated across all of the remaining affected environments, and confirmed with our automated monitoring system that service is restored.
Scope of impact: This issue may have affected any distribution group moderators attempting to approve emails. This may also have affected users in moderated distribution groups who were attempting to receive emails that required moderator approval.
Start time: Wednesday, April 29, 2020, at 3:55 AM UTC
End time: Tuesday, May 12, 2020, at 12:30 AM UTC
Root cause: An update to a component that digests internet headers was preventing it from reflecting the property that allows delivery of an email to a distribution group owner during the approval process.
Next steps:
-We're reviewing our component update procedures to improve our validation process to prevent similar issues from reoccurring.
This is the final update for the event.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 12, 2020 - 01:50 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "UK and Germany Point of Presence Maintenance - May 23rd 23:00 BST (GMT +1) through May 23rd 24:00 BST (GMT +1)"
May 11, 2020 - 20:30 UTC
Investigating - What are we doing?
Fuze is upgrading various network components for a subset of nodes in the United Kingdom and Germany Points of Presence (PoP) as part of our ongoing global network upgrades to optimize service.

Nodes with 24x7 traffic are scheduled for Saturday, May 23rd 23:00 BST (GMT +1) to May 23rd 24:00 BST (GMT +1). All other nodes will be upgraded in batches over a series of 5 nights, Monday, May 18th - Friday, May 22nd from 23:00-24:00 BST, schedule detailed below.

NOTE: The maintenance activities during each window will be for a distinct set of nodes and unless a maintenance is reverted, no node should be included in more than one maintenance window.

Who is affected?
Customers who are homed to an affected node in either the United Kingdom or Germany Data Centers.

When are we doing this?
Monday, May 18th, 23:00 BST through Monday, May 18th, 24:00 BST
Tuesday, May 19th, 23:00 BST through Tuesday, May 19th, 24:00 BST
Wednesday, May 20th, 23:00 BST through Wednesday, May 20th, 24:00 BST
Thursday, May 21st, 23:00 BST through Thursday, May 21st, 24:00 BST
Friday, May 22nd, 23:00 BST through Friday, May 22nd, 24:00 BST
Saturday, May 23rd, 23:00 BST through Saturday, May 23rd, 24:00 BST

What will you experience during the work?
You may experience brief interruptions of service (up to 30 seconds each time) throughout this 1-hour window while the new configuration is being applied causing peers to move between primary and secondary servers. Fuze Contact Center (FCC) will be unavailable during this time.

What do you need to do?
If you experience any issues with Fuze Voice services during this time we recommend waiting up to 30 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

Open a support case by visiting the Fuze Support Community at fuzecommunity.force.com/support

Or call us at:
U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131

May 11, 2020 - 18:38 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "UK and Germany Point of Presence Maintenance - May 21st 23:00 BST (GMT +1) through May 21st 24:00 BST (GMT +1)"
May 11, 2020 - 20:30 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance message [What are we doing?
Fuze is upgrading various network components for a subset of nodes in the United Kingdom and Germany Points of Presence (PoP) as part of our ongoing global network upgrades to optimize service.

Nodes with 24x7 traffic are scheduled for Saturday, May 23rd 23:00 BST (GMT +1) to May 23rd 24:00 BST (GMT +1). All other nodes will be upgraded in batches over a series of 5 nights, Monday, May 18th - Friday, May 22nd from 23:00-24:00 BST, schedule detailed below.

NOTE: The maintenance activities during each window will be for a distinct set of nodes and unless a maintenance is reverted, no node should be included in more than one maintenance window.

Who is affected?
Customers who are homed to an affected node in either the United Kingdom or Germany Data Centers.

When are we doing this?
Monday, May 18th, 23:00 BST through Monday, May 18th, 24:00 BST
Tuesday, May 19th, 23:00 BST through Tuesday, May 19th, 24:00 BST
Wednesday, May 20th, 23:00 BST through Wednesday, May 20th, 24:00 BST
Thursday, May 21st, 23:00 BST through Thursday, May 21st, 24:00 BST
Friday, May 22nd, 23:00 BST through Friday, May 22nd, 24:00 BST
Saturday, May 23rd, 23:00 BST through Saturday, May23rd, 24:00 BST

What will you experience during the work?
You may experience brief interruptions of service (up to 30 seconds each time) throughout this 1-hour window while the new configuration is being applied causing peers to move between primary and secondary servers. Fuze Contact Center (FCC) will be unavailable during this time.

What do you need to do?
If you experience any issues with Fuze Voice services during this time we recommend waiting up to 30 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

Open a support case by visiting the Fuze Support Community at fuzecommunity.force.com/support

Or call us at:
U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131] has changed as [We will be undergoing scheduled maintenance during this time.]. " on alert: "UK and Germany Point of Presence Maintenance - May 21st 23:00 BST (GMT +1) through May 21st 24:00 BST (GMT +1)"

May 11, 2020 - 18:41 UTC
Investigating - What are we doing?
Fuze is upgrading various network components for a subset of nodes in the United Kingdom and Germany Points of Presence (PoP) as part of our ongoing global network upgrades to optimize service.

Nodes with 24x7 traffic are scheduled for Saturday, May 23rd 23:00 BST (GMT +1) to May 23rd 24:00 BST (GMT +1). All other nodes will be upgraded in batches over a series of 5 nights, Monday, May 18th - Friday, May 22nd from 23:00-24:00 BST, schedule detailed below.

NOTE: The maintenance activities during each window will be for a distinct set of nodes and unless a maintenance is reverted, no node should be included in more than one maintenance window.

Who is affected?
Customers who are homed to an affected node in either the United Kingdom or Germany Data Centers.

When are we doing this?
Monday, May 18th, 23:00 BST through Monday, May 18th, 24:00 BST
Tuesday, May 19th, 23:00 BST through Tuesday, May 19th, 24:00 BST
Wednesday, May 20th, 23:00 BST through Wednesday, May 20th, 24:00 BST
Thursday, May 21st, 23:00 BST through Thursday, May 21st, 24:00 BST
Friday, May 22nd, 23:00 BST through Friday, May 22nd, 24:00 BST
Saturday, May 23rd, 23:00 BST through Saturday, May23rd, 24:00 BST

What will you experience during the work?
You may experience brief interruptions of service (up to 30 seconds each time) throughout this 1-hour window while the new configuration is being applied causing peers to move between primary and secondary servers. Fuze Contact Center (FCC) will be unavailable during this time.

What do you need to do?
If you experience any issues with Fuze Voice services during this time we recommend waiting up to 30 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

Open a support case by visiting the Fuze Support Community at fuzecommunity.force.com/support

Or call us at:
U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131

May 11, 2020 - 18:34 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "UK and Germany Point of Presence Maintenance - May 22nd 23:00 BST (GMT +1) through May 22nd 24:00 BST (GMT +1)"
May 11, 2020 - 20:29 UTC
Investigating - What are we doing?
Fuze is upgrading various network components for a subset of nodes in the United Kingdom and Germany Points of Presence (PoP) as part of our ongoing global network upgrades to optimize service.

Nodes with 24x7 traffic are scheduled for Saturday, May 23rd 23:00 BST (GMT +1) to May 23rd 24:00 BST (GMT +1). All other nodes will be upgraded in batches over a series of 5 nights, Monday, May 18th - Friday, May 22nd from 23:00-24:00 BST, schedule detailed below.

NOTE: The maintenance activities during each window will be for a distinct set of nodes and unless a maintenance is reverted, no node should be included in more than one maintenance window.

Who is affected?
Customers who are homed to an affected node in either the United Kingdom or Germany Data Centers.

When are we doing this?
Monday, May 18th, 23:00 BST through Monday, May 18th, 24:00 BST
Tuesday, May 19th, 23:00 BST through Tuesday, May 19th, 24:00 BST
Wednesday, May 20th, 23:00 BST through Wednesday, May 20th, 24:00 BST
Thursday, May 21st, 23:00 BST through Thursday, May 21st, 24:00 BST
Friday, May 22nd, 23:00 BST through Friday, May 22nd, 24:00 BST
Saturday, May 23rd, 23:00 BST through Saturday, May23rd, 24:00 BST

What will you experience during the work?
You may experience brief interruptions of service (up to 30 seconds each time) throughout this 1-hour window while the new configuration is being applied causing peers to move between primary and secondary servers. Fuze Contact Center (FCC) will be unavailable during this time.

What do you need to do?
If you experience any issues with Fuze Voice services during this time we recommend waiting up to 30 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

Open a support case by visiting the Fuze Support Community at fuzecommunity.force.com/support

Or call us at:
U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131

May 11, 2020 - 18:36 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "UK and Germany Point of Presence Maintenance - May 20th 23:00 BST (GMT +1) through May 20th 24:00 BST (GMT +1)"
May 11, 2020 - 20:29 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance message [What are we doing?
Fuze is upgrading various network components for a subset of nodes in the United Kingdom and Germany Points of Presence (PoP) as part of our ongoing global network upgrades to optimize service.

Nodes with 24x7 traffic are scheduled for Saturday, May 23rd 23:00 BST (GMT +1) to May 23rd 24:00 BST (GMT +1). All other nodes will be upgraded in batches over a series of 5 nights, Monday, May 18th - Friday, May 22nd from 23:00-24:00 BST, schedule detailed below.

NOTE: The maintenance activities during each window will be for a distinct set of nodes and unless a maintenance is reverted, no node should be included in more than one maintenance window.

Who is affected?
Customers who are homed to an affected node in either the United Kingdom or Germany Data Centers.

When are we doing this?
Monday, May 18th, 23:00 BST through Monday, May 18th, 24:00 BST
Tuesday, May 19th, 23:00 BST through Tuesday, May 19th, 24:00 BST
Wednesday, May 20th, 23:00 BST through Wednesday, May 20th, 24:00 BST
Thursday, May 21st, 23:00 BST through Thursday, May 21st, 24:00 BST
Friday, May 22nd, 23:00 BST through Friday, May 22nd, 24:00 BST
Saturday, May 23rd, 23:00 BST through Saturday, May23rd, 24:00 BST

What will you experience during the work?
You may experience brief interruptions of service (up to 30 seconds each time) throughout this 1-hour window while the new configuration is being applied causing peers to move between primary and secondary servers. Fuze Contact Center (FCC) will be unavailable during this time.

What do you need to do?
If you experience any issues with Fuze Voice services during this time we recommend waiting up to 30 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

Open a support case by visiting the Fuze Support Community at fuzecommunity.force.com/support

Or call us at:
U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131] has changed as [We will be undergoing scheduled maintenance during this time.]. " on alert: "UK and Germany Point of Presence Maintenance - May 20th 23:00 BST (GMT +1) through May 20th 24:00 BST (GMT +1)"

May 11, 2020 - 18:41 UTC
Investigating - What are we doing?
Fuze is upgrading various network components for a subset of nodes in the United Kingdom and Germany Points of Presence (PoP) as part of our ongoing global network upgrades to optimize service.

Nodes with 24x7 traffic are scheduled for Saturday, May 23rd 23:00 BST (GMT +1) to May 23rd 24:00 BST (GMT +1). All other nodes will be upgraded in batches over a series of 5 nights, Monday, May 18th - Friday, May 22nd from 23:00-24:00 BST, schedule detailed below.

NOTE: The maintenance activities during each window will be for a distinct set of nodes and unless a maintenance is reverted, no node should be included in more than one maintenance window.

Who is affected?
Customers who are homed to an affected node in either the United Kingdom or Germany Data Centers.

When are we doing this?
Monday, May 18th, 23:00 BST through Monday, May 18th, 24:00 BST
Tuesday, May 19th, 23:00 BST through Tuesday, May 19th, 24:00 BST
Wednesday, May 20th, 23:00 BST through Wednesday, May 20th, 24:00 BST
Thursday, May 21st, 23:00 BST through Thursday, May 21st, 24:00 BST
Friday, May 22nd, 23:00 BST through Friday, May 22nd, 24:00 BST
Saturday, May 23rd, 23:00 BST through Saturday, May23rd, 24:00 BST

What will you experience during the work?
You may experience brief interruptions of service (up to 30 seconds each time) throughout this 1-hour window while the new configuration is being applied causing peers to move between primary and secondary servers. Fuze Contact Center (FCC) will be unavailable during this time.

What do you need to do?
If you experience any issues with Fuze Voice services during this time we recommend waiting up to 30 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

Open a support case by visiting the Fuze Support Community at fuzecommunity.force.com/support

Or call us at:
U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131

May 11, 2020 - 18:31 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "UK and Germany Point of Presence Maintenance - May 19th 23:00 BST (GMT +1) through May 19th 24:00 BST (GMT +1)"
May 11, 2020 - 20:29 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance message [What are we doing?
Fuze is upgrading various network components for a subset of nodes in the United Kingdom and Germany Points of Presence (PoP) as part of our ongoing global network upgrades to optimize service.

Nodes with 24x7 traffic are scheduled for Saturday, May 23rd 23:00 BST (GMT +1) to May 23rd 24:00 BST (GMT +1). All other nodes will be upgraded in batches over a series of 5 nights, Monday, May 18th - Friday, May 22nd from 23:00-24:00 BST, schedule detailed below.

NOTE: The maintenance activities during each window will be for a distinct set of nodes and unless a maintenance is reverted, no node should be included in more than one maintenance window.

Who is affected?
Customers who are homed to an affected node in either the United Kingdom or Germany Data Centers.

When are we doing this?
Monday, May 18th, 23:00 BST through Monday, May 18th, 24:00 BST
Tuesday, May 19th, 23:00 BST through Tuesday, May 19th, 24:00 BST
Wednesday, May 20th, 23:00 BST through Wednesday, May 20th, 24:00 BST
Thursday, May 21st, 23:00 BST through Thursday, May 21st, 24:00 BST
Friday, May 22nd, 23:00 BST through Friday, May 22nd, 24:00 BST
Saturday, May 23rd, 23:00 BST through Saturday, May23rd, 24:00 BST

What will you experience during the work?
You may experience brief interruptions of service (up to 30 seconds each time) throughout this 1-hour window while the new configuration is being applied causing peers to move between primary and secondary servers. Fuze Contact Center (FCC) will be unavailable during this time.

What do you need to do?
If you experience any issues with Fuze Voice services during this time we recommend waiting up to 30 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

Open a support case by visiting the Fuze Support Community at fuzecommunity.force.com/support

Or call us at:
U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131] has changed as [We will be undergoing scheduled maintenance during this time.]. " on alert: "UK and Germany Point of Presence Maintenance - May 19th 23:00 BST (GMT +1) through May 19th 24:00 BST (GMT +1)"

May 11, 2020 - 18:39 UTC
Investigating - What are we doing?
Fuze is upgrading various network components for a subset of nodes in the United Kingdom and Germany Points of Presence (PoP) as part of our ongoing global network upgrades to optimize service.

Nodes with 24x7 traffic are scheduled for Saturday, May 23rd 23:00 BST (GMT +1) to May 23rd 24:00 BST (GMT +1). All other nodes will be upgraded in batches over a series of 5 nights, Monday, May 18th - Friday, May 22nd from 23:00-24:00 BST, schedule detailed below.

NOTE: The maintenance activities during each window will be for a distinct set of nodes and unless a maintenance is reverted, no node should be included in more than one maintenance window.

Who is affected?
Customers who are homed to an affected node in either the United Kingdom or Germany Data Centers.

When are we doing this?
Monday, May 18th, 23:00 BST through Monday, May 18th, 24:00 BST
Tuesday, May 19th, 23:00 BST through Tuesday, May 19th, 24:00 BST
Wednesday, May 20th, 23:00 BST through Wednesday, May 20th, 24:00 BST
Thursday, May 21st, 23:00 BST through Thursday, May 21st, 24:00 BST
Friday, May 22nd, 23:00 BST through Friday, May 22nd, 24:00 BST
Saturday, May 23rd, 23:00 BST through Saturday, May23rd, 24:00 BST

What will you experience during the work?
You may experience brief interruptions of service (up to 30 seconds each time) throughout this 1-hour window while the new configuration is being applied causing peers to move between primary and secondary servers. Fuze Contact Center (FCC) will be unavailable during this time.

What do you need to do?
If you experience any issues with Fuze Voice services during this time we recommend waiting up to 30 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

Open a support case by visiting the Fuze Support Community at fuzecommunity.force.com/support

Or call us at:
U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131

May 11, 2020 - 18:30 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "UK and Germany Point of Presence Maintenance - May 18th 23:00 BST (GMT +1) through May 23rd 24:00 BST (GMT +1)"
May 11, 2020 - 20:29 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance message [What are we doing?
Fuze is upgrading various network components for a subset of nodes in the United Kingdom and Germany Points of Presence (PoP) as part of our ongoing global network upgrades to optimize service.

Nodes with 24x7 traffic are scheduled for Saturday, May 23rd 23:00 BST (GMT +1) to May 23rd 24:00 BST (GMT +1). All other nodes will be upgraded in batches over a series of 5 nights, Monday, May 18th - Friday, May 22nd from 23:00-24:00 BST, schedule detailed below.

NOTE: The maintenance activities during each window will be for a distinct set of nodes and unless a maintenance is reverted, no node should be included in more than one maintenance window.

Who is affected?
Customers who are homed to an affected node in either the United Kingdom or Germany Data Centers.

When are we doing this?
Monday, May 18th, 23:00 BST through Monday, May 18th, 24:00 BST
Tuesday, May 19th, 23:00 BST through Tuesday, May 19th, 24:00 BST
Wednesday, May 20th, 23:00 BST through Wednesday, May 20th, 24:00 BST
Thursday, May 21st, 23:00 BST through Thursday, May 21st, 24:00 BST
Friday, May 22nd, 23:00 BST through Friday, May 22nd, 24:00 BST
Saturday, May 23rd, 23:00 BST through Saturday, May23rd, 24:00 BST

What will you experience during the work?
You may experience brief interruptions of service (up to 30 seconds each time) throughout this 1-hour window while the new configuration is being applied causing peers to move between primary and secondary servers. Fuze Contact Center (FCC) will be unavailable during this time.

What do you need to do?
If you experience any issues with Fuze Voice services during this time we recommend waiting up to 30 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

Open a support case by visiting the Fuze Support Community at fuzecommunity.force.com/support

Or call us at:
U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131] has changed as [We will be undergoing scheduled maintenance during this time.]. " on alert: "UK and Germany Point of Presence Maintenance - May 18th 23:00 BST (GMT +1) through May 23rd 24:00 BST (GMT +1)"

May 11, 2020 - 18:39 UTC
Investigating - What are we doing?
Fuze is upgrading various network components for a subset of nodes in the United Kingdom and Germany Points of Presence (PoP) as part of our ongoing global network upgrades to optimize service.

Nodes with 24x7 traffic are scheduled for Saturday, May 23rd 23:00 BST (GMT +1) to May 23rd 24:00 BST (GMT +1). All other nodes will be upgraded in batches over a series of 5 nights, Monday, May 18th - Friday, May 22nd from 23:00-24:00 BST, schedule detailed below.

NOTE: The maintenance activities during each window will be for a distinct set of nodes and unless a maintenance is reverted, no node should be included in more than one maintenance window.

Who is affected?
Customers who are homed to an affected node in either the United Kingdom or Germany Data Centers.

When are we doing this?
Monday, May 18th, 23:00 BST through Monday, May 18th, 24:00 BST
Tuesday, May 19th, 23:00 BST through Tuesday, May 19th, 24:00 BST
Wednesday, May 20th, 23:00 BST through Wednesday, May 20th, 24:00 BST
Thursday, May 21st, 23:00 BST through Thursday, May 21st, 24:00 BST
Friday, May 22nd, 23:00 BST through Friday, May 22nd, 24:00 BST
Saturday, May 23rd, 23:00 BST through Saturday, May23rd, 24:00 BST

What will you experience during the work?
You may experience brief interruptions of service (up to 30 seconds each time) throughout this 1-hour window while the new configuration is being applied causing peers to move between primary and secondary servers. Fuze Contact Center (FCC) will be unavailable during this time.

What do you need to do?
If you experience any issues with Fuze Voice services during this time we recommend waiting up to 30 seconds and trying again.

What happens if it doesn't go as planned?
Maintenance will be reverted.

Who should you contact with questions?
Please reach out to us; we would be happy to talk to you!

Open a support case by visiting the Fuze Support Community at fuzecommunity.force.com/support

Or call us at:
U.S. Toll Free +1 866 379 9442
United States +1 617.603.2299
Australia +61 2 8607 8029
France +33 97 518 6686
Germany +49 32 22 109 6038
Greece +30 211 198 3039
Ireland +353 76 888 7202
Israel +972 3 763 0658
Italy +39 02 94 75 2581
Japan +81 34 589 4674
Netherlands +31 20 241 0144
United Kingdom +44 330 808 0131

May 11, 2020 - 18:16 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 11, 2020 - 14:55 UTC
Investigating - Click on [Body.html] attachment for HTML version

Microsoft 365 suite service alert












Incident information

Title: Can't access multiple Microsoft 365 services
ID: MO212574



Status
Service Restored


Details
Title: Can't access multiple Microsoft 365 services
User Impact: Users may have been unable to access multiple Microsoft 365 services.
Final status: We've identified that a third-party internet exchange site experienced a power outage, resulting in impact. The third-party corrected the issue and we've confirmed that impact has been remediated after monitoring the service.
Scope of impact: Our telemetry indicated that this issue affected a subset of user connections routed from the UK. If the users' Internet Service Provider (ISP) connections were routed within the affected internet exchange, they would have experienced impact.
Start time: Monday, May 11, 2020, at 1:30 PM UTC
End time: Monday, May 11, 2020, at 1:50 PM UTC
Root cause: A third-party internet exchange site experienced a power outage.
This is the final update for the event.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 11, 2020 - 14:55 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 11, 2020 - 14:24 UTC
Investigating - Click on [Body.html] attachment for HTML version

Microsoft 365 suite service alert












Incident information

Title: Can't access multiple Microsoft 365 services
ID: MO212574



Status
Service Degradation


Details
Title: Can't access multiple Microsoft 365 services
User Impact: Users may be unable to access multiple Microsoft 365 services.
Current status: We're reviewing system telemetry to determine the next troubleshooting steps.
Scope of impact: Reports indicate that impact is specific to the UK.
Next update by: Monday, May 11, 2020, at 3:00 PM UTC



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 11, 2020 - 14:17 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 11, 2020 - 14:24 UTC
Investigating - Click on [Body.html] attachment for HTML version

Microsoft 365 suite service alert












Incident information

Title: Can't access multiple Microsoft 365 services
ID: MO212574



Status
Investigating


Details
Title: Can't access multiple Microsoft 365 services
User Impact: Users may be unable to access multiple Microsoft 365 services.
Current status: We're reviewing system telemetry to determine the next troubleshooting steps.
Scope of impact: Reports indicate that impact is specific to the UK.
Next update by: Monday, May 11, 2020, at 3:00 PM UTC



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 11, 2020 - 14:07 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "Web Backend Update: 05/10/2020 (No Operational Impact)"
May 11, 2020 - 13:44 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [IN_PROGRESS] has changed as [COMPLETED].
Statuspage scheduled maintenance message [Scheduled maintenance is currently in progress. We will provide updates as necessary.] has changed as [The scheduled maintenance has been completed.]. " on alert: "Web Backend Update: 05/10/2020 (No Operational Impact)"

May 10, 2020 - 11:01 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [SCHEDULED] has changed as [IN_PROGRESS].
Statuspage scheduled maintenance message [We will be performing a routine maintenance on our Web Backend. Please refer to https://support.zoom.us/hc/en-us/articles/204758419 for more details. This update includes updated password and security settings for free and basic accounts, managed domain enhancements, and additional admin features.

There is no operational impact. All services will be available during this scheduled update.] has changed as [Scheduled maintenance is currently in progress. We will provide updates as necessary.]. " on alert: "Web Backend Update: 05/10/2020 (No Operational Impact)"

May 10, 2020 - 06:01 UTC
Investigating - We will be performing a routine maintenance on our Web Backend. Please refer to https://support.zoom.us/hc/en-us/articles/204758419 for more details. This update includes updated password and security settings for free and basic accounts, managed domain enhancements, and additional admin features.

There is no operational impact. All services will be available during this scheduled update.

May 08, 2020 - 21:02 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 11, 2020 - 13:43 UTC
Investigating - Click on [Body.html] attachment for HTML version

Exchange Online service alert












Incident information

Title: Multiple credential prompts in the Outlook client
ID: EX212047



Status
Service Restored


Details
Title: Multiple credential prompts in the Outlook client
User Impact: Users may have received repeated credential prompts within the Outlook client.
More info: While we were focused on remediation, users that had access to other protocols such as Outlook on the web or mobile devices could access their email without issue.
This issue only impacted customers using basic authentication. Customers who were able to use Modern Authentication to mitigate impact for affected users; however, this process may have required several hours to take effect for some customers.
For some customers who have disabled Modern Authentication, there was a secondary issue that was causing the client to attempt to use Modern Authentication regardless of the setting.
Final status: We've verified that the fix has been deployed to the affected infrastructure and confirmed via customer reports and service health monitoring that the issue has been resolved.
Scope of impact: This issue affected a subset of customers and users who were connecting to the service using Basic Authentication and utilized service-based search or a Focused inbox.
Start time: Monday, May 4, 2020, at 7:00 AM UTC
End time: Monday, May 11, 2020, at 5:05 AM UTC
Preliminary root cause: A recent update to the Exchange Online service contained a code issue that caused repeated credential prompts for basic authentication users.
Next steps:
- We're reviewing our update and validation procedures to prevent similar issues from reoccurring and to identify issues before initiating deployment.
- We're reviewing our deployment and patching procedures to more quickly identify the source of impact and mitigate impact in a more timely fashion.
We'll publish a post-incident report within five business days.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 11, 2020 - 05:32 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "Bitbucket Cloud is experiencing issues with Billing"
May 11, 2020 - 13:43 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [We are continuing to monitor for any further issues.] has changed as [This incident has been resolved.]. " on alert: "Bitbucket Cloud is experiencing issues with Billing"

May 11, 2020 - 06:33 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [A fix has been implemented and we are monitoring the results.] has changed as [We are continuing to monitor for any further issues.].
Statuspage incident component [Purchasing & Licensing] status [major_outage] has changed as [operational]. " on alert: "Bitbucket Cloud is experiencing issues with Billing"

May 11, 2020 - 06:07 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [MONITORING].
Statuspage incident message [We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected.] has changed as [A fix has been implemented and we are monitoring the results.]. " on alert: "Bitbucket Cloud is experiencing issues with Billing"

May 11, 2020 - 05:56 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident name [Bitbucket Cloud is experiencing issues with Billing] is updated as [Bitbucket Cloud Purchasing and Licensing Outage]. " on alert: "Bitbucket Cloud is experiencing issues with Billing"
May 11, 2020 - 05:30 UTC
Investigating - We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected.
May 11, 2020 - 05:28 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "Infrastructure upgrade"
May 11, 2020 - 13:43 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [IN_PROGRESS] has changed as [COMPLETED].
Statuspage scheduled maintenance message [Scheduled maintenance is still in progress for Azure EU West region only.
We will provide updates as necessary.] has changed as [The scheduled maintenance has been completed.].
Statuspage scheduled maintenance component [Azure EU West] status [under_maintenance] has changed as [operational]. " on alert: "Infrastructure upgrade"

May 10, 2020 - 13:02 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance message [Scheduled maintenance is still in progress for Azure US West and Azure EU West regions only.
We will provide updates as necessary.] has changed as [Scheduled maintenance is still in progress for Azure EU West region only.
We will provide updates as necessary.].
Statuspage scheduled maintenance component [Azure US West] status [under_maintenance] has changed as [operational]. " on alert: "Infrastructure upgrade"

May 10, 2020 - 12:39 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance message [Scheduled maintenance is still in progress. We will provide updates as necessary.] has changed as [Scheduled maintenance is still in progress for Azure US West and Azure EU West regions only.
We will provide updates as necessary.].
Statuspage scheduled maintenance component [Azure US East] status [under_maintenance] has changed as [operational]. " on alert: "Infrastructure upgrade"

May 10, 2020 - 11:46 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance component [Azure AU East (New south, Wales Australia)] status [under_maintenance] has changed as [operational].
Statuspage scheduled maintenance component [Azure Southeast Asia (Singapore)] status [under_maintenance] has changed as [operational]. " on alert: "Infrastructure upgrade"

May 10, 2020 - 11:14 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance message [Scheduled maintenance is currently in progress. We will provide updates as necessary.] has changed as [Scheduled maintenance is still in progress. We will provide updates as necessary.]. " on alert: "Infrastructure upgrade"
May 10, 2020 - 11:12 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance scheduledUntil [2020-05-10T11:00:00.000Z] is updated as [2020-05-10T13:00:00.000Z]. " on alert: "Infrastructure upgrade"
May 10, 2020 - 10:19 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [SCHEDULED] has changed as [IN_PROGRESS].
Statuspage scheduled maintenance message [Maintenance will begin as scheduled in 60 minutes.] has changed as [Scheduled maintenance is currently in progress. We will provide updates as necessary.].
Statuspage scheduled maintenance component [Azure US East] status [operational] has changed as [under_maintenance].
Statuspage scheduled maintenance component [Azure AU East (New south, Wales Australia)] status [operational] has changed as [under_maintenance].
Statuspage scheduled maintenance component [Azure EU West] status [operational] has changed as [under_maintenance].
Statuspage scheduled maintenance component [Azure US West] status [operational] has changed as [under_maintenance].
Statuspage scheduled maintenance component [Azure Southeast Asia (Singapore)] status [operational] has changed as [under_maintenance]. " on alert: "Infrastructure upgrade"

May 10, 2020 - 07:00 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance message [We will be upgrading the system software on our infrastructure layer.
This is a proactive maintenance as recommended by the cloud provider.
It is performed automatically on a rolling basis, There is no planned downtime during this maintenance window, but some users may see very brief service interruptions.] has changed as [Maintenance will begin as scheduled in 60 minutes.]. " on alert: "Infrastructure upgrade"

May 10, 2020 - 06:00 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance name [[Scheduled] Infrastructure upgrade] is updated as [[Scheduled] Azure Infrastructure upgrade]. " on alert: "Infrastructure upgrade"
May 09, 2020 - 08:24 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance name [Infrastructure upgrade] is updated as [[Scheduled] Infrastructure upgrade]. " on alert: "Infrastructure upgrade"
May 09, 2020 - 08:23 UTC
Investigating - We will be upgrading the system software on our infrastructure layer.
This is a proactive maintenance as recommended by the cloud provider.
It is performed automatically on a rolling basis, There is no planned downtime during this maintenance window, but some users may see very brief service interruptions.

May 09, 2020 - 08:22 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "Scheduled maintenance for our Customer Portal"
May 11, 2020 - 13:43 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [IN_PROGRESS] has changed as [COMPLETED].
Statuspage scheduled maintenance message [Scheduled maintenance is currently in progress. We will provide updates as necessary.] has changed as [The scheduled maintenance has been completed.].
Statuspage scheduled maintenance component [MyJFrog - JFrog Customer Portal] status [under_maintenance] has changed as [operational]. " on alert: "Scheduled maintenance for our Customer Portal"

May 10, 2020 - 09:00 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [SCHEDULED] has changed as [IN_PROGRESS].
Statuspage scheduled maintenance message [Maintenance will begin as scheduled in 60 minutes.] has changed as [Scheduled maintenance is currently in progress. We will provide updates as necessary.].
Statuspage scheduled maintenance component [MyJFrog - JFrog Customer Portal] status [operational] has changed as [under_maintenance]. " on alert: "Scheduled maintenance for our Customer Portal"

May 10, 2020 - 07:02 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance message [We will be undergoing scheduled maintenance during this time.] has changed as [Maintenance will begin as scheduled in 60 minutes.]. " on alert: "Scheduled maintenance for our Customer Portal"
May 10, 2020 - 05:59 UTC
Investigating - We will be undergoing scheduled maintenance during this time.
May 09, 2020 - 07:45 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "Mac, Windows, Android, iOS, & Linux Client Update: 05/11/2020 (No Operational Impact)"
May 11, 2020 - 13:43 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [IN_PROGRESS] has changed as [COMPLETED].
Statuspage scheduled maintenance message [Scheduled maintenance is currently in progress. We will provide updates as necessary.] has changed as [The scheduled maintenance has been completed.]. " on alert: "Mac, Windows, Android, iOS, & Linux Client Update: 05/11/2020 (No Operational Impact)"

May 11, 2020 - 10:03 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage scheduled maintenance status [SCHEDULED] has changed as [IN_PROGRESS].
Statuspage scheduled maintenance message [We will be providing a new version of our Mac, Windows, and Linux clients. They will be available for download at https://zoom.us/download. We will also be performing a staggered release for iOS and Android on applicable app stores. This update will include an enhanced privacy design.

Mac - https://support.zoom.us/hc/en-us/articles/201361963
Windows - https://support.zoom.us/hc/en-us/articles/201361953
Android - https://support.zoom.us/hc/en-us/articles/201361973
iOS - https://support.zoom.us/hc/en-us/articles/201361943
Linux - https://support.zoom.us/hc/en-us/articles/205759689

There is no operational impact. All services will be available during this scheduled update.

There is no operational impact. All services will be available during this time.] has changed as [Scheduled maintenance is currently in progress. We will provide updates as necessary.]. " on alert: "Mac, Windows, Android, iOS, & Linux Client Update: 05/11/2020 (No Operational Impact)"

May 11, 2020 - 06:00 UTC
Investigating - We will be providing a new version of our Mac, Windows, and Linux clients. They will be available for download at https://zoom.us/download. We will also be performing a staggered release for iOS and Android on applicable app stores. This update will include an enhanced privacy design.

Mac - https://support.zoom.us/hc/en-us/articles/201361963
Windows - https://support.zoom.us/hc/en-us/articles/201361953
Android - https://support.zoom.us/hc/en-us/articles/201361973
iOS - https://support.zoom.us/hc/en-us/articles/201361943
Linux - https://support.zoom.us/hc/en-us/articles/205759689

There is no operational impact. All services will be available during this scheduled update.

There is no operational impact. All services will be available during this time.

May 08, 2020 - 21:00 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "Atlassian Bitbucket Maintenance - [Scheduled] Storage maintenance - 14 May 2020"
May 11, 2020 - 13:43 UTC
Investigating - Click on [Body.html] attachment for HTML version

[Scheduled] Storage maintenance

Upcoming scheduled maintenance notice
We will be upgrading the system software on our storage layer. This is a proactive maintenance as recommended by the manufacturer. It is performed automatically on a rolling basis and is not expected to cause any disruption.

Start time
May 14, 20:00 UTC

Components Affected
Website, API, SSH, Git via HTTPS, Mercurial via HTTPS and 3 more components.

View full scheduled maintenance details http://u12100069.ct.sendgrid.net/ls/click?upn=C6Nzbj60PuO4nniwccQoJ76lrTqOKn7gOHfRF7i3OjFc49MyiqBrSWZV-2F5WZsdSUaM2I_fLeEsHn8Z57gzk1greiCVXTRHqQkY4QWy7DpyggS-2FS50HG8XFH4iA5CRvfEhPBYflgTVS0gbhwsZGFNsNt2nLfPTSO4HGV6gigGAyI3J5HOXSBdUC9rdwoBjuNZRwenzk8kN-2BREZhisZOPc7H2bp6JGdn1rG8M0dg-2F3XrjDpZV9JIbHbLdHp-2BG8IiJdRrfefbF4v-2BXTQYSw0QS7ivRodZFR7qk9oxCQxensk0ZfwZYUyZm4B57Wx4P7eqLFxBrSh

You received this email because you are subscribed to Atlassian Bitbucket's service status notifications.
Manage your subscription: http://u12100069.ct.sendgrid.net/ls/click?upn=JsK1Y6Qkg9vM2veJ-2BgHikH6Ap7YZlzBlcuJ8jIIiNe17s5jQRj74g8k5ZRgfKIVhwReeTtT6Z5WQd8IaY2qtDcfR1khlzGF5F4bdiBZqrjY-3DSw5w_fLeEsHn8Z57gzk1greiCVXTRHqQkY4QWy7DpyggS-2FS50HG8XFH4iA5CRvfEhPBYflgTVS0gbhwsZGFNsNt2nLeR-2BTmOGjNf4TZalZmQJipvJS6plIHQYN5NlTtGp1tX1rwZt1l64Bq63XJyM24j-2FGDpwX8yP2fvx-2Fpu2sDCdhxgt8-2FZhx7WD112rU6h-2BX5wtiXM9hGSIOgGZ-2BIYtm2u-2BT0r7P4ePwqvRNVrVNQEY3WAFkffQZt4Kv-2FKoTVArdupM

May 08, 2020 - 17:50 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "[Scheduled] Storage maintenance"
May 11, 2020 - 13:43 UTC
Investigating - We will be upgrading the system software on our storage layer. This is a proactive maintenance as recommended by the manufacturer. It is performed automatically on a rolling basis and is not expected to cause any disruption.
May 08, 2020 - 17:49 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 08, 2020 - 13:51 UTC
Investigating - Click on [Body.html] attachment for HTML version

Exchange Online service alert












Incident information

Title: Multiple credential prompts in the Outlook client
ID: EX212047



Status
Restoring Service


Details
Title: Multiple credential prompts in the Outlook client
User Impact: Users may receive repeated credential prompts within the Outlook client.
More info: While we're focused on remediation, users that have access to other protocols such as Outlook on the web or mobile devices can access their email without issue.
This issue only impacts customers using basic authentication. Customers who are able to use Modern Authentication may enable it to mitigate impact for affected users; however, this process can require several hours to take effect for some customers.
While we understand this may not be a viable workaround for all customers we're committed to identifying and provided all potential solutions. Details on how to enable Modern Authentication can be found here: https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/enable-or-disable-modern-authentication-in-exchange-online.
Current status: We've initiated deployment of our solution and users should experience service restoration as the fix reaches their environment. We will provide an estimated resolution timeline as soon as one is available.
Scope of impact: This issue affects a subset of customers and users who are connecting to the service using Basic Authentication and utilize service-based search or a Focused inbox.
Start time: Tuesday, May 5, 2020, at 4:00 AM UTC
Preliminary root cause: A recent update to the Exchange Online service contains a code issue that is causing repeated credential prompts for basic authentication users.
Next update by: Friday, May 8, 2020, at 3:00 AM UTC



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 07, 2020 - 23:42 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 08, 2020 - 13:51 UTC
Investigating - Click on [Body.html] attachment for HTML version

Microsoft Teams service alert












Incident information

Title: Incoming calls can't be answered in Microsoft Teams intermittently
ID: TM212147



Status
Service Restored


Details
Title: Incoming calls can't be answered in Microsoft Teams intermittently
User Impact: Incoming calls to users may have been intermittently dropped upon answering.
Final status: We've confirmed that the new Teams iOS client build 2.0.010 which contains the fix for the problem is now available for download in the iOS App Store. As the auto-update feature for the app remains disabled at this time, we encourage affected users to manually update to the latest version of the Teams iOS client to resolve the problem.
Scope of impact: Impact was intermittent and specific to users who were signed in to the Teams iOS app alongside any other version of the Teams client with the same account.
Start time: Tuesday, May 5, 2020, at 5:30 AM UTC
End time: Friday, May 8, 2020, at 4:00 AM UTC
Root cause: The Teams iOS client build 2.0.9 contained an error that would intermittently cause incoming calls to drop upon answering.
Next steps:
- We're working to identify additional testing methodologies to better ensure the efficacy of our iOS client builds.
We'll publish a post-incident report within five business days.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 08, 2020 - 05:29 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are continuing to investigate the problems.] has changed as [Our engineering team has identified the issue and is actively working on resolving it.]. " on alert: "Issues displaying meeting information in Dashboard"

May 07, 2020 - 17:19 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We are currently seeing higher than normal dashboard delays. The operations and engineering teams are investigating and working to resolve the issue. Hosts and participants will still be able to successfully connect into Zoom meetings and webinars.] has changed as [We are continuing to investigate the problems.]. " on alert: "Issues displaying meeting information in Dashboard"
May 05, 2020 - 17:44 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "Issues displaying meeting information in Dashboard"
May 05, 2020 - 17:33 UTC
Investigating - We are currently seeing higher than normal dashboard delays. The operations and engineering teams are investigating and working to resolve the issue. Hosts and participants will still be able to successfully connect into Zoom meetings and webinars.
May 05, 2020 - 16:37 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [We have identified the root cause of the purchasing and licensing issues and have mitigated the problem. We are now monitoring closely.] has changed as [Between 5:47 UTC to 12:05 UTC, all customers experienced issues related to purchasing and licensing for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. The root cause was a database auditing issue resulting in errors when trying to create quotes, view billing details and action changes in subscriptions. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we are actively working on a permanent fix. The issue has been resolved and the service is operating normally.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 12:51 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING].
Statuspage incident message [We are continue to work on resolving the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix and expect to recover shortly.] has changed as [We have identified the root cause of the purchasing and licensing issues and have mitigated the problem. We are now monitoring closely.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 12:09 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We continue to work on resolving the the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix. We will provide more details within the next hour.] has changed as [We are continue to work on resolving the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix and expect to recover shortly.]. " on alert: "Purchasing and Licensing Outage"
May 07, 2020 - 10:01 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected. We will provide more details within the next hour.] has changed as [We continue to work on resolving the the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix. We will provide more details within the next hour.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 08:37 UTC
Investigating - We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected. We will provide more details within the next hour.
May 07, 2020 - 07:11 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [We have identified the root cause of the purchasing and licensing issues and have mitigated the problem. We are now monitoring closely.] has changed as [Between 5:47 UTC to 12:05 UTC, all customers experienced issues related to purchasing and licensing for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. The root cause was a database auditing issue resulting in errors when trying to create quotes, view billing details and action changes in subscriptions. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we are actively working on a permanent fix. The issue has been resolved and the service is operating normally.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 12:51 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING].
Statuspage incident message [We are continue to work on resolving the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix and expect to recover shortly.] has changed as [We have identified the root cause of the purchasing and licensing issues and have mitigated the problem. We are now monitoring closely.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 12:10 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We continue to work on resolving the the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix. We will provide more details within the next hour.] has changed as [We are continue to work on resolving the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix and expect to recover shortly.]. " on alert: "Purchasing and Licensing Outage"
May 07, 2020 - 10:01 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected. We will provide more details within the next hour.] has changed as [We continue to work on resolving the the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix. We will provide more details within the next hour.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 08:37 UTC
Investigating - We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected. We will provide more details within the next hour.
May 07, 2020 - 07:11 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [We have identified the root cause of the purchasing and licensing issues and have mitigated the problem. We are now monitoring closely.] has changed as [Between 5:47 UTC to 12:05 UTC, all customers experienced issues related to purchasing and licensing for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. The root cause was a database auditing issue resulting in errors when trying to create quotes, view billing details and action changes in subscriptions. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we are actively working on a permanent fix. The issue has been resolved and the service is operating normally.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 12:51 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING].
Statuspage incident message [We are continue to work on resolving the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix and expect to recover shortly.] has changed as [We have identified the root cause of the purchasing and licensing issues and have mitigated the problem. We are now monitoring closely.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 12:09 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We continue to work on resolving the the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix. We will provide more details within the next hour.] has changed as [We are continue to work on resolving the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix and expect to recover shortly.]. " on alert: "Purchasing and Licensing Outage"
May 07, 2020 - 10:01 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected. We will provide more details within the next hour.] has changed as [We continue to work on resolving the the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix. We will provide more details within the next hour.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 08:39 UTC
Investigating - We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected. We will provide more details within the next hour.
May 07, 2020 - 07:11 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [We have identified the root cause of the purchasing and licensing issues and have mitigated the problem. We are now monitoring closely.] has changed as [Between 5:47 UTC to 12:05 UTC, all customers experienced issues related to purchasing and licensing for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. The root cause was a database auditing issue resulting in errors when trying to create quotes, view billing details and action changes in subscriptions. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we are actively working on a permanent fix. The issue has been resolved and the service is operating normally.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 12:50 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING].
Statuspage incident message [We are continue to work on resolving the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix and expect to recover shortly.] has changed as [We have identified the root cause of the purchasing and licensing issues and have mitigated the problem. We are now monitoring closely.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 12:09 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We continue to work on resolving the the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix. We will provide more details within the next hour.] has changed as [We are continue to work on resolving the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix and expect to recover shortly.]. " on alert: "Purchasing and Licensing Outage"
May 07, 2020 - 10:01 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected. We will provide more details within the next hour.] has changed as [We continue to work on resolving the the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix. We will provide more details within the next hour.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 08:37 UTC
Investigating - We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected. We will provide more details within the next hour.
May 07, 2020 - 07:11 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [We have identified the root cause of the purchasing and licensing issues and have mitigated the problem. We are now monitoring closely.] has changed as [Between 5:47 UTC to 12:05 UTC, all customers experienced issues related to purchasing and licensing for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. The root cause was a database auditing issue resulting in errors when trying to create quotes, view billing details and action changes in subscriptions. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we are actively working on a permanent fix. The issue has been resolved and the service is operating normally.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 12:50 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING].
Statuspage incident message [We are continue to work on resolving the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix and expect to recover shortly.] has changed as [We have identified the root cause of the purchasing and licensing issues and have mitigated the problem. We are now monitoring closely.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 12:10 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We continue to work on resolving the the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix. We will provide more details within the next hour.] has changed as [We are continue to work on resolving the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix and expect to recover shortly.]. " on alert: "Purchasing and Licensing Outage"
May 07, 2020 - 10:02 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected. We will provide more details within the next hour.] has changed as [We continue to work on resolving the the issue with our purchasing and licensing services for Confluence, Jira Core, Jira Service Desk, Jira Software, and Atlassian Bitbucket. We have identified the root cause and are working on a fix. We will provide more details within the next hour.]. " on alert: "Purchasing and Licensing Outage"

May 07, 2020 - 08:39 UTC
Investigating - We are investigating an issue with our purchasing and licenses services that is impacting all Cloud customers. Sign ups, purchases and payments are affected. We will provide more details within the next hour.
May 07, 2020 - 07:11 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [The issue has been resolved and artifact access should be back to normal. The team is monitoring the situation.] has changed as [This incident has been resolved.]. " on alert: "Issues uploading and downloading artifacts"

May 07, 2020 - 08:49 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [MONITORING].
Statuspage incident message [We are aware of an incident that causes issues with uploading and downloading artifacts in Bitbucket Pipelines. The team is investigating the issue.] has changed as [The issue has been resolved and artifact access should be back to normal. The team is monitoring the situation.].
Statuspage incident component [Pipelines] status [partial_outage] has changed as [operational]. " on alert: "Issues uploading and downloading artifacts"

May 07, 2020 - 08:22 UTC
Investigating - We are aware of an incident that causes issues with uploading and downloading artifacts in Bitbucket Pipelines. The team is investigating the issue.
May 07, 2020 - 08:09 UTC
Investigating - Click on [Body.html] attachment for HTML version

Error when accepting a request to transfer ownership of repository.

Incident resolved
This incident has been resolved.

Time posted
May 7, 02:16 UTC

Components Affected
Website

View 2 previous incident updates http://stspg.io/wb7tcbtjxhc5

You received this email because you are subscribed to Atlassian Bitbucket's service status notifications.
Manage your subscription: https://bitbucket.status.atlassian.com/subscriptions/wzd3bxhvf137/edit

May 07, 2020 - 02:17 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [RESOLVED].
Statuspage incident message [The Bitbucket team is working on deploying a fix for this issue.] has changed as [This incident has been resolved.]. " on alert: "Error when accepting a request to transfer ownership of repository."

May 07, 2020 - 02:17 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We are aware of an error customers are getting when accepting a request to transfer ownership of repository. The Bitbucket team is currently working on a fix to address this issue.] has changed as [The Bitbucket team is working on deploying a fix for this issue.]. " on alert: "Error when accepting a request to transfer ownership of repository."
May 07, 2020 - 02:02 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident impact [NONE] has changed as [MINOR]. " on alert: "Error when accepting a request to transfer ownership of repository."
May 06, 2020 - 22:52 UTC
Investigating - We are aware of an error customers are getting when accepting a request to transfer ownership of repository. The Bitbucket team is currently working on a fix to address this issue.
May 06, 2020 - 22:49 UTC
Investigating - Click on [Body.html] attachment for HTML version

Exchange Online service alert












Incident information

Title: Multiple credential prompts in the Outlook client
ID: EX212047



Status
Service Degradation


Details
Title: Multiple credential prompts in the Outlook client
User impact: Users may receive repeated credential prompts within the Outlook client.
More info: While we're focused on remediation, users that have access to other protocols such as Outlook on the web or mobile devices can access their email without issue. Additionally, customers who are able to use Modern Authentication may enable it to mitigate impact for affected users. Details on how to enable Modern Authentication can be found here: https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/enable-or-disable-modern-authentication-in-exchange-online
Current status: We've determined that a recent Exchange Online update contains a code issue which is resulting in repeated credential prompts. We've halted deployment of the build to prevent further spread of impact and we're discussing mitigation steps for this event. We've confirmed that this issue appears to only affect basic authentication configuration users.
Scope of impact: This issue may affect any user that has service-based search or Focused Inbox. Additionally, this issue only affects users that are attempting to connect via basic authentication.
Preliminary root cause: A recent update to the Exchange Online service contains a code issue that is causing repeated credential prompts for basic authentication users.
Next update by: Thursday, May 7, 2020, at 3:30 AM UTC



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 07, 2020 - 01:16 UTC
Investigating - Click on [Body.html] attachment for HTML version

Error when accepting a request to transfer ownership of repository.

New incident: Identified
We are aware of an error customers are getting when accepting a request to transfer ownership of repository. The Bitbucket team is currently working on a fix to address this issue.

Time posted
May 6, 22:49 UTC

Components Affected
Website

View full incident details http://u12100069.ct.sendgrid.net/ls/click?upn=C6Nzbj60PuO4nniwccQoJxWppSynawzbejJ9DWnsHchuDC972bnwRXWJWvhIhAD1zQkW_fLeEsHn8Z57gzk1greiCVXTRHqQkY4QWy7DpyggS-2FS50HG8XFH4iA5CRvfEhPBYfA7AhXXZnCEQhavcTZ0gJCb5V-2BvOtCy5ukYq8sVrXMNkhfSMiD94mnGDNn2B4i95J24gWlRfoLc6V0uqmsFlW51RkVYMS08zwoahp2PsojWbEvGsL-2BXEKjd4-2Bmb6Ysr0AGbLyzSrGuRR1CjMD4IkQKizMNupmiJGdIYqkjAD1rZEGrN-2FpvrA5wlHiUsLJ7IYd

You received this email because you are subscribed to Atlassian Bitbucket's service status notifications.
Manage your subscription: http://u12100069.ct.sendgrid.net/ls/click?upn=JsK1Y6Qkg9vM2veJ-2BgHikH6Ap7YZlzBlcuJ8jIIiNe17s5jQRj74g8k5ZRgfKIVhwReeTtT6Z5WQd8IaY2qtDcfR1khlzGF5F4bdiBZqrjY-3DlErm_fLeEsHn8Z57gzk1greiCVXTRHqQkY4QWy7DpyggS-2FS50HG8XFH4iA5CRvfEhPBYfA7AhXXZnCEQhavcTZ0gJCTCHg5pkHEZWK0wZVWEDZQUITk7XH4BqDBhSYUG-2BhRrbHfKx00CGEETkIaSQ-2B754KyBkpdvpgbyyy0uNrfYokyLFymRD9XK5HGkxFCt4qfK2yTheF38wBr9h3nRilV2EhzuYibq6luqPzD1G-2FRC-2B-2FHIidp-2Fi6I4fKffQPaHJHbLs

May 06, 2020 - 22:51 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [RESOLVED].
Statuspage incident message [We have identified the cause and are actively restoring the data. We expect all data to be fully recovered.] has changed as [We have finished restoring the data and expect all data to be fully recovered.

Again, we apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.].
Statuspage incident component [Fuze Data, Reporting, and/or Discover Services] status [degraded_performance] has changed as [operational]. " on alert: "May 1st Data"

May 06, 2020 - 21:12 UTC
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED].
Statuspage incident message [Fuze has identified an issue where a subset of customers are unable to view queue summary data for May 1st in Fuze View. We are working diligently to identify the issue and reload the data. We will provide regular updates until the issue has been resolved. We apologize for any inconvenience caused and appreciate your patience.] has changed as [We have identified the cause and are actively restoring the data. We expect all data to be fully recovered.]. " on alert: "May 1st Data"

May 06, 2020 - 16:58 UTC
Investigating - Fuze has identified an issue where a subset of customers are unable to view queue summary data for May 1st in Fuze View. We are working diligently to identify the issue and reload the data. We will provide regular updates until the issue has been resolved. We apologize for any inconvenience caused and appreciate your patience.
May 06, 2020 - 15:41 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 06, 2020 - 20:20 UTC
Investigating - Click on [Body.html] attachment for HTML version

Microsoft Teams service alert












Incident information

Title: Affected users can't join or produce Teams live events
ID: TM212166



Status
Service Restored


Details
Title: Affected users can't join or produce Teams live events
User Impact: Users may be unable to join or produce Microsoft Teams live events.
Final status: We've redirected traffic to an alternate infrastructure, allowing users to access Microsoft Teams live events and remediating impact.
Scope of impact: Impact was specific to any user served through the affected infrastructure in Europe.
Start time: Wednesday, May 6, 2020, at 12:45 PM UTC
End time: Wednesday, May 6, 2020, at 5:00 PM UTC
Root cause: Part of the infrastructure that serves Microsoft Teams live events encountered a failure, resulting in impact if producers or presenters attempted to join the live events between Wednesday, May 6, 2020, at 12:45 PM UTC, and Wednesday, May 6, 2020, at 5:00 PM UTC.
Next steps:
- We're analyzing performance data and trends on the affected systems to help prevent this problem from happening again.
This is the final update for the event.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 06, 2020 - 19:39 UTC
Update - [Comment from Opsgenie]System noted: "Incident [May 1st Data] is deleted from Statuspage [TeamIT_Fuze]. " on alert: "May 1st Data"
May 06, 2020 - 15:39 UTC
Investigating - Fuze has identified an issue where a subset of customers are unable to view queue data for May 1st in Fuze View. We are working diligently to identify the issue and will provide regular updates until the issue has been resolved. We apologize for any inconvenience caused and appreciate your patience.
May 06, 2020 - 15:32 UTC
Investigating - Click on [Body.html] attachment for HTML version

Microsoft Teams service alert












Incident information

Title: Can't join Teams Live Events
ID: TM212166



Status
Service Degradation


Details
Title: Can't join Teams Live Events
User Impact: Users may be unable to join Microsoft Teams Live Events.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to any user served through the affected infrastructure in Europe.
Start time: Wednesday, May 6, 2020, at 12:45 PM UTC
Next update by: Wednesday, May 6, 2020, at 3:30 PM UTC



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 06, 2020 - 15:01 UTC
Investigating - Click on [Body.html] attachment for HTML version

Microsoft Teams service alert












Incident information

Title: Can't join Teams Live Events
ID: TM212166



Status
Investigating


Details
Title: Can't join Teams Live Events
User Impact: Users may be unable to join Microsoft Teams Live Events.
Current status: We're investigating a potential issue with Microsoft Teams Live Events. We'll provide an update within 30 minutes.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 06, 2020 - 13:44 UTC
Update - [Comment from Opsgenie]Barb O'Connell acknowledged alert: "M365 Service Health Notification"
May 05, 2020 - 21:43 UTC
Investigating - Click on [Body.html] attachment for HTML version

Microsoft Teams service alert












Incident information

Title: All users can't view user presence in Microsoft Teams
ID: TM212081



Status
Service Degradation


Details
Title: All users can't view user presence in Microsoft Teams
User Impact: Users are unable to view or update user presence in Microsoft Teams.
Current status: We're investigating a subset of infrastructure responsible for processing presence request traffic.
Scope of impact: This issue may potentially affect any of your users attempting to look up or update user presence.
Start time: Tuesday, May 5, 2020, at 7:21 PM UTC
Next update by: Tuesday, May 5, 2020, at 9:30 PM UTC



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 05, 2020 - 20:30 UTC
Update - [Comment from Opsgenie]Jason Redd acknowledged alert: "M365 Service Health Notification"
May 05, 2020 - 20:17 UTC
Investigating - Click on [Body.html] attachment for HTML version

Microsoft Teams service alert












Incident information

Title: All users can't view user presence in Microsoft Teams
ID: TM212081



Status
Investigating


Details
Title: All users can't view user presence in Microsoft Teams
User Impact: Users may be unable to view user presence in Microsoft Teams.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.



Thank you,
The Microsoft team















To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.


Microsoft respects your privacy. Review our online Privacy Statement.


Microsoft Corporation


One Microsoft Way


Redmond, WA USA 98052

May 05, 2020 - 20:06 UTC
IT Managed Properties Operational
90 days ago
100.0 % uptime
Today
Fuze-Dialer-Staging ? Operational
90 days ago
100.0 % uptime
Today
Meltwater SSO Major Outage
90 days ago
0.98 % uptime
Today
SSO - HTTPS Major Outage
90 days ago
0.98 % uptime
Today
Google Operational
Gmail Operational
Drive Operational
Calendar Operational
Docs Operational
Sheets Operational
Slides Operational
Hangouts Operational
Analytics Operational
Groups Operational
Sync for Mobile Operational
Vault Operational
Voice Operational
Admin Console Operational
Fuze - Voice Services ? Operational
90 days ago
100.0 % uptime
Today
North America Operational
90 days ago
100.0 % uptime
Today
Europe Operational
90 days ago
100.0 % uptime
Today
Asia Pacific Operational
90 days ago
100.0 % uptime
Today
Africa Operational
90 days ago
100.0 % uptime
Today
Latin America Operational
90 days ago
100.0 % uptime
Today
Fuze - Contact Center Services Operational
90 days ago
100.0 % uptime
Today
North America Operational
90 days ago
100.0 % uptime
Today
Europe Operational
90 days ago
100.0 % uptime
Today
Asia Pacific Operational
90 days ago
100.0 % uptime
Today
Africa Operational
90 days ago
100.0 % uptime
Today
Latin America Operational
90 days ago
100.0 % uptime
Today
Slack Operational
90 days ago
100.0 % uptime
Today
Slack Login/SSO Operational
Slack Messaging Operational
90 days ago
100.0 % uptime
Today
Slack Posts/Files Operational
90 days ago
100.0 % uptime
Today
Slack Notifications Operational
Slack Apps/Integrations Operational
90 days ago
100.0 % uptime
Today
Slack Apps/Integrations/APIs Operational
90 days ago
100.0 % uptime
Today
Slack Calls Operational
90 days ago
100.0 % uptime
Today
Slack Connections Operational
90 days ago
100.0 % uptime
Today
Slack Link Previews Operational
90 days ago
100.0 % uptime
Today
Slack Search Operational
90 days ago
100.0 % uptime
Today
Slack Workspace/Org Administration Operational
90 days ago
100.0 % uptime
Today
Atlassian - Valiantys Major Outage
90 days ago
0.98 % uptime
Today
Jira - Production ? Major Outage
90 days ago
0.98 % uptime
Today
Jira - Staging Major Outage
90 days ago
0.98 % uptime
Today
Confluence Prod Major Outage
90 days ago
0.98 % uptime
Today
Atlassian Cloud Operational
Confluence Administration Operational
Confluence Authentication and User Management Operational
Confluence Comments Operational
Confluence Create and Edit Operational
Confluence Marketplace Apps Operational
Confluence iOS App Operational
Confluence Android App Operational
Confluence Notifications Operational
Confluence Search Operational
Confluence View Content Operational
Jira Core Administration Operational
Jira Core Authentication and User Management Operational
Jira Core Create and edit Operational
Jira Core Marketplace Operational
Jira Core Mobile Operational
Jira Core Notifications Operational
Jira Core Search Operational
Jira Core Viewing content Operational
Jira Service Desk Authentication and User Management Operational
Jira Service Desk Service Desk Email Requests Operational
Jira Service Desk Service Desk Portal Operational
Jira Service Desk Service Desk Web Operational
Jira Software Administration Operational
Jira Software Authentication and User Management Operational
Jira Software Create and edit Operational
Jira Software Marketplace Operational
Jira Software Mobile Operational
Jira Software Notifications Operational
Jira Software Search Operational
Jira Software Viewing content Operational
MS Exchange and Office 365 Operational
90 days ago
100.0 % uptime
Today
Artifactory Operational
Artifactory Cloud AWS Asia Pacific South 1 (Mumbai) Operational
Artifactory Cloud AWS Asia Pacific NorthEast 1 (Tokyo) Operational
Artifactory Cloud GCP US West 1 (Oregon) Operational
Artifactory Cloud AWS Asia Pacific SouthEast 1 (Singapore) Operational
Artifactory Cloud AWS Asia Pacific SouthEast 2 (Sydney) Operational
Artifactory Cloud AWS Europe Central 1 (Frankfurt) Operational
Artifactory Cloud AWS Europe West (Ireland) Operational
Artifactory Cloud AWS US East 1 (N. Virginia) Operational
Artifactory Cloud AWS US West 1 (California) Operational
Artifactory Cloud AWS US West 2 (Oregon) Operational
Artifactory Cloud Azure AU East (New south, Wales Australia) Operational
Artifactory Cloud Azure EU West Operational
Artifactory Cloud Azure US East Operational
Artifactory Cloud Azure US West Operational
Artifactory Cloud GCP Asia East 2 (Hong Kong) Operational
Artifactory Cloud GCP Europe West 2 (London) Operational
Artifactory Cloud GCP OSS Us East 1 (S. Carolina) Operational
Artifactory Cloud GCP US East 1 (S. Carolina) Operational
Artifactory Cloud GCP US Central 1 (Iowa) Operational
Zoom Operational
Zoom Zoom Meetings Operational
Zoom Zoom Software Operational
test Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Dec 27, 2024

No incidents reported today.

Dec 26, 2024

No incidents reported.

Dec 25, 2024

No incidents reported.

Dec 24, 2024

No incidents reported.

Dec 23, 2024

No incidents reported.

Dec 22, 2024

No incidents reported.

Dec 21, 2024

No incidents reported.

Dec 20, 2024

No incidents reported.

Dec 19, 2024

No incidents reported.

Dec 18, 2024

No incidents reported.

Dec 17, 2024

No incidents reported.

Dec 16, 2024

No incidents reported.

Dec 15, 2024

No incidents reported.

Dec 14, 2024

No incidents reported.

Dec 13, 2024

No incidents reported.