Customers using Freshservice webhook triggers may not receive new updates in their Zaps. We are investigating the disruption with Freshservice and will share further information as it becomes available.
We are investigating increased API error rates in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region.
We are investigating issues with AWS services in the ME-CENTRAL-1 Region.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.
Cloudflare is investigating an issue with the Browser Isolation service that is preventing some users from keyboard input. Other Cloudflare services are not affected. We are working to mitigate this problem and will provide further updates shortly.
We are aware of an issue with direct record sharing for enterprise users as a result of yesterday's Vault 18.3 update. We will issue a patch before 12PM PST. To work around the issue, you can click the "Can share to users outside the enterprise" option in Role enforcements, or just use the Desktop App.
We have identified an issue causing some users to be unable to access ChatGPT on chatgpt.com "chatgpt.com": http://chatgpt.com. We are working on implementing a mitigation. In the meantime, please try clearing the cache.
We have identified an issue causing some users to be unable to access ChatGPT on chatgpt.com "chatgpt.com": http://chatgpt.com. We are working on implementing a mitigation. In the meantime, please try clearing the cache.
We’re currently experiencing an issue where some Zapier Agents runs may fail or be missed. This may affect: • Zapier Agents • Agent-triggered workflow runs Zapier’s core automation systems are otherwise continuing to process normally. If you need help, contact Support: https://zapier.com/app/get-help
Title: Some users may be intermittently unable to access Outlook on the web User impact: Users may be intermittently unable to access Outlook on the web. Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
We are currently investigating an issue causing delays in the processing of webhook-based triggers. As a result, some Zaps that rely on trigger events may run later than usual. This may affect trigger events across a range of apps. No trigger data is being lost — affected events are delayed, not dropped, and will be processed once the system catches up. Our team is actively investigating and working to restore normal processing times. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience.
We're received reports of missed leads for Facebook Lead Ads triggers. We're currently working with our Partners at Meta to figure out the root cause and implement a fix as soon as possible. We'll be updating this status page with our progress. Many thanks for your patience! If you have any questions, feel free to reach us at zapier.com/get-help.
We are investigating the issue for the listed services.
We are investigating the issue for the listed services.
We are investigating the issue for the listed services.
We are investigating the issue for the listed services.
Some workspace admins on standalone (non-Enterprise Grid) workspaces may be experiencing an issue where the SSO and authentication configuration page does not display current settings as expected. Admins may see a blank value for the "Require SSO authentication for" field on the admin SSO settings page, which does not accurately reflect the actual backend configuration — SSO settings remain intact and in effect.We are actively investigating this issue and will provide an update as soon as we have more information to share. We apologize for the inconvenience.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
Cloudflare is investigating an issue with the Browser Isolation service. Impact is limited to customers accessing websites secured with Cloudflare Turnstile, who may observe errors when attempting to load these sites through the service. Other Cloudflare services are not affected. We are working to mitigate this problem and will provide further updates shortly.
Some users may be experiencing issues performing certain actions in Slack, channel creation, invitation, and join operations may result in a degraded experience. Thank you for your patience while we continue to investigate the situation.
Customers may not see invoice payment status accurately reflected in the Cloudflare UI for payments made since June 11. Impacted customers will see paid Invoices shown as Unpaid via the Cloudflare Dashboard.
We are aware that some users on the Slack Android app are unable to submit workflow forms that contain a required file upload field. After a file is selected, the Submit button becomes disabled and the form cannot be completed. Users on Slack for iOS and Slack for web are not affected. We are actively investigating the issue and working to identify the root cause. We'll provide an update in 60 minutes or sooner if additional information becomes available.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
We are investigating the issue for the listed services.
We are investigating the issue for the listed services.
What happened?Between 21:45 UTC and 23:23 UTC on 15 June 2026, Azure customers leveraging services which depend upon Microsoft Artifact Registry (MAR) may have experienced 401 authentication errors when attempting to pull images from MAR . This incident is now mitigated. Further details will be provided directly to impacted customers through the Azure Portal.
Impact Statement: Starting at 21:45 UTC on 15 June 2026, a subset of Azure customers leveraging services which depend upon MCR (Microsoft Container Registry) for storing images may experience 401 authentication errors for requests attempting to pull Microsoft images from mcr.microsoft.com.Current Status: We detected this issue via internal service monitoring upon identifying a spike of 401 errors. We’ve identified a potential underlying factor to be a recent update which introduced a code regression, and we've completed roll out of a hotfix to address the code regression and mitigate impact for affected customers. We are closely monitoring internal telemetry to validate full mitigation and prevent further occurrences. The next update will be provided within 60 minutes, or as events warrant.
We are actively investigating customer alerts of 401 authentication errors when pulling images from mcr.microsoft.com. We’ve identified a potential underlying factor related to a recent update made to a backed service and we are actively working on determining mitigation workstreams. More information will be provided shortly.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
We are receiving customer reports that Zap workflows using Facebook Lead Ads or Facebook Pages are returning the following error when Zap runs occur. "An unknown error occurred." Users are also unable to connect to existing or create new app connections, with those connections instantly expiring. We're looking into the issue to identify its root cause.
We have identified that users are experiencing an error when attempting to create an account or logging in using Google OAuth for the impacted services. We are working on implementing a mitigation.
We have identified that users are experiencing an error when attempting to create an account or logging in using Google OAuth for the impacted services. We are working on implementing a mitigation.
We are investigating an issue where some Zoom Rooms Scheduling Displays may incorrectly appear as offline in the Zoom Dashboard, despite the devices remaining online and operational. This issue is limited to the status displayed in the Dashboard and does not impact the functionality of the affected scheduling displays. As a workaround, users may perform a physical reboot of the affected scheduling display device to restore the correct status in the Dashboard. Our team is actively working to identify the impact and root cause and will provide further updates as more information becomes available. We appreciate your patience as we work to resolve this issue.
We are currently investigating a service degradation affecting Zoom Meeting Recordings. Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available. We appreciate your patience as we work to resolve this issue.
We are currently investigating a service degradation affecting Zoom Web AIC Docs creation. Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available. We appreciate your patience as we work to resolve this issue.
On 06/15/2026, between 04:31 UTC to 05:01 UTC, a subset of users might have experienced service degradation with Zoom Contact Center’s Agent Experience. This incident has been resolved and the affected services have been restored.
We are currently investigating a service degradation affecting My Notes. Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available. We appreciate your patience as we work to resolve this issue.
We’re investigating an issue causing intermittent errors when loading Zapier Templates pages "Zapier Templates pages": https://zapier.com/templates, including some template detail/category pages (for example, Lead Management). You may see pages fail to load or display server errors intermittently. Our team is actively working to identify and resolve the root cause. We will provide updates as soon as we have more information. If you require any assistance, please contact our Support Team: https://zapier.com/app/get-help