Our monitoring have detected increased latency on API responsible for issuing OAuth impersonation tokens. After detailed investigation we have confirmed that service is operating withing expected boundaries. The monitoring configuration will be corrected to match the expected service latency and not cause false alerts.
May 19, 14:14 UTC
We are investigating cases of increased latency for Connect apps requesting an auth token from the oath-2-authorization-server for user impersonation.
May 19, 05:56 UTC
This doesn't qualify as an incident. This is an expected behaviour. The analytics job runs every Monday. In this case it ran on May 2nd, and then on Wednesday(May 5th) we received another event for new cloud version. However we ignore this event as we already received analytics events from jira/confluences etc instances prior in the week. We do not show the count till the next Monday because it can be partial and might sometimes update later in the week. The new data should appear in the next week(16 May).
May 13, 04:22 UTC
We see installs missing for this week starting 9th of May. We are looking into it.
May 11, 16:12 UTC