Status Tracker v0.23
Oct 25, 12:24 PDT
Resolved – This incident has been resolved.
Oct 25, 11:51 PDT
Monitoring – A fix has been implemented and we are monitoring the results.
Oct 25, 11:30 PDT
Identified – The issue has been identified and a fix is being implemented.
Oct 25, 11:16 PDT
Investigating – External links are currently not unfurling, investigating.
Oct 25, 17:23 UTC
Resolved – Between 25-Oct-2024 at 9:50 AM UTC to 25-Oct-2024 at 4:52 PM UTC, we identified intermittent errors in external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations that impacted all Atlassian Guard cloud customers. The issue has been resolved and the service is operating normally.
Oct 25, 16:16 UTC
Update – We continue to investigate the intermittent errors in external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations that are impacting all Atlassian Guard cloud customers. As the investigation proceeds, we will provide more updates.
Oct 25, 14:37 UTC
Update – We are continuing to investigate intermittent errors in external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations that are impacting all Guard Cloud customers. We will provide updates as we learn more.
Oct 25, 13:39 UTC
Investigating – We are again investigating intermittent errors for external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations that are impacting all Guard Cloud customers. We will provide more details within the next hour.
Oct 25, 12:20 UTC
Monitoring – On 25-Oct-2024 at 9:50 AM UTC, we identified intermittent errors for external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations that are impacting all Guard Cloud customers.
We have taken action to mitigate this issue and we are now monitoring it closely.
Oct 25, 11:37 UTC
Investigating – We are investigating reports of intermittent errors for external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations, which are curerntly not loading.
Guard Cloud customers are affected by this issue.
We will provide more details once we identify the root cause.
Oct 25, 04:09 PDT
Resolved – We have addressed the issue affecting users’ interaction with Facebook Lead Ads on Zapier. Previously, users encountered an error message: “Unsupported get request. Object with ID ‘XXXXX’ does not exist, cannot be loaded due to missing permissions, or does not support this operation.”
This issue also affected testing of Facebook Lead Ads triggers, where users might have seen this error: “Error Code: Error while retrieving: The app returned “A test lead was already created for this leadgen form. Delete the existing lead before creating a new one. To retrieve the lead id, use the GET call on /test_leads edge.”.”
Please note that this incident only impacted users utilizing Facebook Lead Ads.
Our team has reached out and worked with Meta to resolve the issue and replayed tasks for Facebook Lead Ads. Tasks for Facebook Lead Ads(For Business Admins) and Facebook Conversions will be replayed by Friday, 25th Oct, 2024. Any users still encountering issues are advised to reach out to our support team at: https://zapier.com/app/get-help.
We appreciate your understanding and patience during this incident. If you run into any further issues, kindly reach out to us for assistance.
Oct 24, 12:22 PDT
Monitoring – Meta has implemented a fix for the issue. Our team is actively monitoring the situation to ensure it is fully resolved. All affected runs have been successfully replayed.
If you do experience any more problems, please don’t hesitate to reach out to the support team here: https://zapier.com/app/get-help
Oct 24, 03:08 PDT
Identified – Due to an error, the Status page was set to resolved.
However, we are still investigating an ongoing issue affecting Facebook Lead Ads on Zapier. The problem is causing hydration errors, and we have traced this to a specific error message: “Unsupported get request. Object with ID ‘XXXXX’ does not exist, cannot be loaded due to missing permissions, or does not support this operation.”
This is also effecting testing of Facebook Lead Ads triggers where users may see an error similar to: “Error Code: Error while retrieving: The app returned “A test lead was already created for this leadgen form. Delete the existing lead before creating a new one. To retrieve the lead id, use the GET call on /test_leads edge.”.”
Users may encounter this issue while attempting to interact with Facebook Lead Ads. Please note that this incident does not impact users who are not utilizing Facebook Lead Ads.
We are actively working on identifying the root cause of this problem to resolve it as soon as possible. As of now, we do not have an estimated time for resolution, and we regret any inconvenience this issue may cause.
We encourage you to contact our Support Team should you need any assistance with other matters: https://zapier.com/app/get-help. We will continue to provide updates on this incident as we have more information. Please stay tuned.
Oct 24, 14:53 UTC
Resolved – From 7 AM – 3 PM UTC time, there was a problem with signing up to Asana. This issue has now been resolved, and users should be able to sign up again.
Oct 24, 04:00 UTC
Resolved – The issue is now solved
Oct 24, 03:48 UTC
Monitoring – We’ve applied a fix, and the issue appears to be resolved. We’re continuing to monitor it.
Oct 24, 03:32 UTC
Update – The team is still investigating the issue,
Oct 24, 03:06 UTC
Update – We believe this is related to our Edge Functions layer alone. We’re still investigating.
Oct 24, 02:41 UTC
Update – The team continues to investigate the issue. We started seeing the errors happening around 1AM UTC.
Oct 24, 02:22 UTC
Investigating – We are seeing increased latency and errors on the High-Performance Edge Network. The team is investigating
Oct 23, 18:59 UTC
Resolved – We’re back! Dropbox should be up and running. Thanks for bearing with us.
Oct 23, 18:36 UTC
Monitoring – A fix has been implemented and we are monitoring the results.
Oct 23, 18:24 UTC
Update – We are continuing to investigate this issue.
Oct 23, 18:24 UTC
Investigating – Dropbox may not be working as expected for some users. We are working to fix the problem as quickly as we can. We’ll share another update shortly.
Oct 23, 13:04 UTC
Resolved – The fix for this issue has been deployed to production and testing was successfully completed. We have been monitoring for the past 30 minutes and are seeing no new instances of this issue.
Oct 23, 12:27 UTC
Update – We have identified an issue with https://home.atlassian.com that impacts authentication of users who do not have Projects or Goals and have a fix now deployed to production.
We are testing this issue now but expect that this incident has been concluded.
Oct 23, 11:45 UTC
Investigating – We are investigating reports of intermittent errors for some users on Atlas for Cloud customers. When being redirected to home.atlassian.com, customers are landing in an error page (Something went wrong).
We are working on resolving the issue.
At 12:52 PM PDT on October 10, 2024, the Engineering team became aware of a provisioning setup issue with Office365 affecting customers on all cells. SSO and federation services are not impacted.
The Engineering team is investigating the root cause to mitigate the issue. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.
Oct 18, 17:38 UTC
Resolved – Between 2024-10-18 05:40 UTC-7 to 2024-10-18 08:40 UTC-7, we experienced an outage affecting user/group memberships in AdminHub for Confluence, Jira Work Management, Jira Service Management, Jira, and Guard. The issue has been resolved and the service is operating normally.
Oct 18, 14:09 UTC
Identified – We have received reports of intermittent errors for some Cloud customers, specifically admins who are unable to see group memberships in AdminHub. We have identified the root cause and expect recovery shortly.
Oct 18, 03:09 UTC
Resolved – This incident has been resolved.
Oct 18, 02:58 UTC
Monitoring – We’ve applied a fix and the issue appears to be resolved. We’re continuing to monitor the issue.
Oct 18, 02:52 UTC
Update – We are continuing to investigate this issue.
Oct 18, 01:25 UTC
Investigating – We’re investigating reports of HTTP 431 on sites using Edge Functions.