Jun 7, 15:41 UTC
Resolved - This incident has been resolved.
Jun 7, 14:57 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 7, 14:42 UTC
Identified - The issue has been identified and a fix is being implemented.
Jun 7, 14:35 UTC
Investigating - We are currently investigating this issue.
Jun 7, 04:28 UTC
Resolved - We have resolved an issue resulting in elevated errors on requests to some Claude Models.
Jun 7, 03:41 UTC
Identified - We have identified the cause of elevated errors on requests to several Claude models and are working to resolve these issues.
Jun 7, 03:31 UTC
Investigating - We are investigating elevated errors on requests to Claude Opus 4.7. We will provide an update as soon as possible.
Jun 6, 19:05 UTC
Resolved - From 18:12–18:55, we saw elevated errors on requests to Claude Opus 4.8. This issue has been resolved.
Jun 6, 18:37 UTC
Identified - We are experiencing elevated error rates on Claude Opus 4.8. Our team has identified the issue and is working to fully resolve these errors.
Jun 6, 10:14 UTC
Resolved - This incident has been resolved.
Jun 6, 09:59 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 6, 09:43 UTC
Identified - The issue has been identified and a fix is being implemented.
Jun 6, 09:27 UTC
Investigating - We are currently investigating this issue.
Jun 5, 18:28 UTC
Resolved - This incident has been resolved.
Jun 5, 18:27 UTC
Update - The incident started at 8:08 PT / 15:08 UTC. Recovery times per model were:
Opus 4.6 - 8:25 PT / 15:25 UTC
Sonnet 4.6 — 9:23 PT / 16:23 UTC
Opus 4.8 — 9:59 PT / 16:59 UTC
Opus 4.7 — 10:12 PT / 17:12 UTC
Opus 4.5 — 10:29 PT / 17:29 UTC
All models have now fully recovered.
Jun 5, 17:13 UTC
Monitoring - Success rates across all models have returned to expected levels. We are continuing to monitor closely to ensure no further issues will recur.
Jun 5, 16:46 UTC
Update - We are continuing to work to resolve issues affecting success rates on Opus 4.7 and 4.8, and will provide additional updates as soon as possible.
Jun 5, 15:43 UTC
Identified - We have identified the issue and we are working to mitigate the issue. Current ongoing issues with frontier models are with Opus 4.7 and Opus 4.8 and other models have recovered.
Jun 5, 15:19 UTC
Investigating - We are currently investigating this issue.
Jun 7, 04:44 UTC
Resolved - This issue has been resolved and macOS jobs across all resource classes are starting normally again. Customers whose jobs failed to start during this window may rerun them. We thank you for your patience while our team worked on implementing a fix.
Jun 7, 04:20 UTC
Identified - We have identified an issue causing macOS jobs to fail to start and are working to restore service. This impacts customers running macOS jobs across all resource classes.
Thank you for your patience while our engineers work to resolve this. We will provide another update within 30 minutes.
Jun 2, 13:11 UTC
Resolved - This incident has been resolved.
Jun 2, 13:06 UTC
Monitoring - We identified the issue and have deployed a fix and are now monitoring.
Jun 2, 12:52 UTC
Investigating - We are noticing an increase in errors when pulling Docker images. We are investigating.
Jun 1, 03:26 UTC
Resolved - All Mac jobs are running successfully.
Our infrastructure provider has confirmed that the DDoS attack has been mitigated and that services have been restored.
Thank you for your patience during this incident.
Jun 1, 02:05 UTC
Update - Mac jobs are running successfully, and we are continuing to monitor the performance of our Mac fleet.
Thank you for your patience.
Jun 1, 01:36 UTC
Monitoring - We are seeing Mac jobs starting successfully and improved network connectivity to the Mac fleet, however our infrastructure provider is continuing to experience a DDoS attack.
We will continue to monitor the recovery while bringing additional capacity to our platform.
Jun 1, 01:05 UTC
Update - We are continuing to investigate this issue.
Jun 1, 01:04 UTC
Investigating - Mac jobs are continuing to experience failures. Our infrastructure provider is continuing to report that they are experiencing a DDoS attack causing high network latency and packet loss for our Mac fleet. We are working to bring up additional capacity to restore service.
Jun 1, 00:45 UTC
Resolved - Mac jobs have now fully recovered.
Thank you for your patience during this incident.
Jun 1, 00:42 UTC
Update - We have processed the backlog of Mac jobs and job start times are recovering to normal parameters.
Jun 1, 00:24 UTC
Monitoring - We are seeing Mac jobs starting successfully and improved network connectivity to the Mac fleet. We will continue to monitor the recovery.
May 31, 22:38 UTC
Update - Mac jobs are continuing to experience failures. Our infrastructure provider is reporting they are experiencing a DDoS attack causing high network latency and packet loss for our Mac fleet. We are working to bring up additional capacity to restore service.
We will continue to update as more information is available.
May 31, 21:24 UTC
Update - We are continuing to investigate failures with Mac jobs starting due to high network latency and packet loss. Our engineers remain engaged with our infrastructure provider to restore service.
We will provide another update within the hour, or sooner if circumstances change. We thank you for your patience while our engineers work to resolve this.
May 31, 20:05 UTC
Update - We are still seeing failures with Mac jobs starting due to high network latency and packet loss. We will continue to update as we have more information on a resolution.
May 31, 19:09 UTC
Update - We are continuing to work on resolving the networking issue for Mac jobs.
May 31, 18:15 UTC
Identified - We have identified a network outage that is preventing Mac jobs from starting. This include m4pro.medium and m4pro.large resource types.
We are working with our infrastructure provider to restore service.
We will update this incident as we work to resolve the issue.
May 29, 18:10 UTC
Resolved - The Usage API incident has been resolved.
May 29, 14:57 UTC
Update - We've identified a small number of duplicate records in the Usage API data. Data is available, but may be inaccurate. We continue to investigate.
May 29, 14:51 UTC
Investigating - We are currently investigating this issue.
Jun 8, 16:34 UTC
Investigating - Some RealtimeKit users may not join meetings, team is investigating.
Jun 8, 16:14 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 8, 15:47 UTC
Investigating - Cloudflare has identified an issue where some customers may experience latency querying the GraphQL API. We are working to analyze and mitigate this problem. More updates to follow shortly.
Jun 8, 16:00 UTC
Resolved - Cloudflare R2 users may have seen increased errors when reading data from buckets stored in WEUR.
Jun 8, 13:30 UTC
Resolved - This incident has been resolved.
Jun 8, 12:42 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 8, 10:06 UTC
Update - We are continuing to work on a fix for this issue.
Jun 8, 10:05 UTC
Identified - Starting June 5, 2026 (~12:00 UTC), users adding R2 and Teams products see "An unexpected error occurred while processing your payment." blocking them from creating subscriptions.
Jun 8, 11:10 UTC
Resolved - This incident has been resolved.
Jun 8, 10:52 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 8, 10:46 UTC
Investigating - Cloudflare is investigating issues with Cloudflare Dashboard and related APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.
Jun 6, 05:04 UTC
Resolved - Our upstream provider, Vultr, has resolved the network connectivity issue affecting their Chicago location.
Jun 6, 00:37 UTC
Investigating - Our upstream provider Vultr is currently experiencing a partial outage in their Chicago - United States location. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.
Jun 3, 06:50 UTC
Resolved - This incident has been resolved.
Jun 2, 17:37 UTC
Monitoring - A fix has been implemented by the Cloudlfare and they are monitoring the results.
Jun 1, 15:21 UTC
Investigating - Cloudflare is currently investigating issues related to the SaaS Custom Hostname API. Customers may experience slow responses when adding new domains, and newly added domains may also encounter SSL-related errors. Existing domains or applications using Cloudflare remain unaffected and are operating normally.
We will provide further updates as soon as more information becomes available.
May 28, 12:26 UTC
Resolved - This incident has been resolved.
May 25, 13:04 UTC
Investigating - We are currently receiving multiple reports from customers who are unable to add mailboxes or log in to their Rackspace mailboxes.
The issue has already been identified by the Rackspace team, and they are actively working toward a resolution. We will update our status page with further information as soon as we receive additional updates from Rackspace. We sincerely apologize for the inconvenience caused and appreciate your patience and understanding.
May 20, 12:40 UTC
Resolved - This incident has been resolved.
May 20, 02:48 UTC
Monitoring - DO team has implemented mitigation measures for the infrastructure issue affecting Block Storage Volumes in the NYC3 region. The team is monitoring the situation, and we will share another update once the issue is fully resolved
May 20, 01:31 UTC
Investigating - We are observing an issue with some of the Block Storage Volume Performance in the New York region on Digital Ocean. During this time, users may experience degraded write performance and intermittent impact to services dependent on the affected storage infrastructure. Our Engineering team is working closely with DO team to resolve this issue. We apologize for the inconvenience and will share an update once we have more information.
May 19, 17:58 UTC
Resolved - This incident has been resolved.
May 19, 14:21 UTC
Investigating - Our upstream provider, Vultr, is currently experiencing a partial outage at their Seoul, Korea location. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.
Jun 2, 14:51 UTC
Resolved - We think the impact from the issue is over, however, uploads using 3rd cloud providers (Google Drive, Instagram, Box, Dropbox etc) are temporarily disabled.
Jun 2, 13:27 UTC
Identified - Uploads via 3rd party cloud integrations are affected. We are working on a resolution.
Jun 2, 13:02 UTC
Investigating - Some customers are experiencing issues uploading files. We are investigating.
May 26, 17:17 UTC
Resolved - The issue has been resolved.
May 26, 17:08 UTC
Monitoring - We have addressed the issue and are monitoring the situation.
May 26, 17:02 UTC
Investigating - Some customers are experiencing issues with the Contentful Web App. We are investigating.
May 19, 20:17 UTC
Resolved - We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
May 19, 16:57 UTC
Investigating - We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
May 19, 16:29 UTC
Resolved - We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
May 19, 16:28 UTC
Monitoring - We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
May 13, 13:57 UTC
Resolved - The issue has been resolved.
May 13, 13:52 UTC
Monitoring - We have resolved the issue and are monitoring the situation.
May 13, 13:47 UTC
Investigating - Customers are experiencing errors on CMA and within the Web App, we are investigating.
May 21, 01:30 EDT
Resolved - Earlier today, one of our sending IPs was listed on a third-party blocklist, causing some outbound email notifications to be blocked or delayed by recipient mail servers. The IP has since been delisted, and email delivery has returned to normal. We apologize for the disruption.
May 20, 15:30 EDT
Resolved - This incident has been resolved. Please note that responses received during the downtime may need to be reprocessed for the connector run to complete. Please check your response log to confirm.
May 20, 11:43 EDT
Update - We are continuing to investigate this issue.
May 20, 11:41 EDT
Investigating - Our team is currently investigating reports of loss of access to a small subset of Team and Enterprise accounts. We will update here with more information shortly.
Apr 17, 00:30 EDT
Resolved - Earlier this morning, some accounts hosted on our Sydney servers experienced errors when loading forms, including “There was a problem on our end trying to load forms” and “An unknown error occurred.”
The issue has been resolved, and services have returned to normal. We will continue to monitor.
Apr 8, 10:49 EDT
Resolved - The issue affecting email notification delivery has been resolved. A temporary third-party blocklist listing was identified and removed. Email notifications are now functioning normally.
If you continue to experience issues, please contact support.
Apr 7, 19:56 EDT
Monitoring - We have identified the cause of the email notification delivery issue as a temporary listing of one of our sending IPs on a third-party blocklist, which resulted in email rejections for some customers.
The listing has since been removed, and we have not observed any new rejection logs since 2:21 PM ET. Email notifications should now be functioning normally.
We are continuing to monitor the situation to ensure stability. We will provide another update once we confirm the issue is fully resolved.
Apr 7, 15:35 EDT
Investigating - Some customers are reporting that email notifications aren't being sent as expected upon form completion, and our team is investigating now.
We will post more information as it becomes available.
Mar 26, 11:57 EDT
Resolved - This incident has been resolved.
Mar 26, 11:18 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 26, 10:50 EDT
Investigating - We are investigating reports of inaccessible form lists affecting accounts in the Frankfurt region. We understand the disruption this may cause and are actively working to resolve it as quickly as possible. We will provide updates as more information becomes available.
Jun 8, 10:03 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 8, 09:49 UTC
Update - We are experiencing degraded availability for the Claude Opus 4.7 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue, and starting to see recovery.
Jun 8, 09:08 UTC
Update - We are experiencing degraded availability for the Claude Opus 4.7 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Jun 8, 09:05 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Jun 8, 08:36 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 8, 08:35 UTC
Monitoring - The degradation affecting Actions, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
Jun 8, 08:27 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
Jun 8, 08:13 UTC
Update - Following investigation, we are seeing that impact is limited to unauthenticated users when accessing Pull Requests, Issues, or Actions. Our team continues to work towards mitigation with more updates to follow as we have them.
Jun 8, 07:32 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Jun 8, 07:31 UTC
Update - Issues is experiencing degraded performance. We are continuing to investigate.
Jun 8, 07:14 UTC
Update - Issues is experiencing degraded availability. We are continuing to investigate.
Jun 8, 07:11 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 6, 17:07 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 6, 16:56 UTC
Update - Packages is experiencing degraded performance. We are continuing to investigate.
Jun 6, 16:53 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 5, 22:21 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 5, 22:21 UTC
Update - Affected Slack and Teams subscriptions have been restored. Please contact support if you encounter any additional issues.
Jun 5, 20:34 UTC
Update - Additional detail on the scope of impact during the 14:49 UTC to 16:45 UTC window: a small but elevated percentage of authenticated requests to GitHub.com received incorrect authorization failures. We saw a 1 to 2% increase in 4xx responses for a small number of endpoints (/repos/{owner}/{repo}/pulls/{pull_number}, /repos/{owner}/{repo}, /repos/{owner}/{repo}/contents/{path}). The vast majority of requests completed normally; customers who saw errors during the window can retry now and should see them succeed.
Jun 5, 18:43 UTC
Update - We are still exploring options to restore the deleted subscriptions, and we will provide another update soon. In the meantime, customers can manually re-subscribe their Slack and Teams channels to repositories.
Jun 5, 18:05 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 5, 18:04 UTC
Update - During 14:49 UTC to 16:45 UTC, customers may have experienced authorization failures for legitimate requests. This was caused by a recently enabled feature flag, which has now been turned off as a mitigation. Customers should now see normal authorization behavior. This is also the cause of the chat integration issue, and we are exploring options to restore it. In the meantime, customers can manually re-subscribe their repo.
Jun 5, 17:25 UTC
Update - Customers may see unexpected repo unsubscription events in their Slack or Teams channels.
Jun 5, 17:20 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
May 12, 10:55 EDT
Resolved - Between 02:47 PM (UTC +01:00) and 03:15 PM (UTC +01:00), some customers in all affected regions experienced issues with all impaired tools. This was caused by a database impairment. As of 03:15 PM (UTC +01:00), our all impaired tools are working properly and the incident has been fully resolved.
HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability.
The information on this page reflects our understanding of the incident and impact at the time of the update.
May 12, 09:57 EDT
Investigating - We're investigating reports that HubSpot may be unavailable for some users. We'll update this page when we have more information.
May 7, 23:14 EDT
Resolved - Between 05:23 PM (UTC -07:00) and 07:56 PM (UTC -07:00), HubSpot experienced degradation in portals in the U.S. . This was related to an AWS outage. HubSpot is now working properly and the incident has been resolved.
HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability.
The information on this page reflects our understanding of the incident and impact at the time of the update
May 7, 22:07 EDT
Update - We are experiencing degradation in portals in the U.S. which is related to AWS outage. We are working with AWS on the full resolution.
We will be back with an update within 30 minutes
The information on this page reflects our understanding of the incident and impact at the time of the update.
May 7, 21:36 EDT
Identified - We are experiencing degradation in portals in the U.S. which we believe is related to AWS outage.
We are working with AWS to resolve the issue. We will be back with an update within 30 minutes.
The information on this page reflects our understanding of the incident and impact at the time of the update.
May 2, 15:31 EDT
Resolved - HubSpot has continued to monitor the fix and believe we have addressed the underlying issue. Some messages deployed before May 1, 5 pm EDT may still experience delayed deliveries or failures over the next ~48 hours as retries and queues fully clear.
May 1, 12:34 EDT
Update - In April, some customers may have experienced intermittent DMARC failures on messages to Microsoft-hosted inboxes. Impact was most visible for senders with a DMARC policy of p=reject or p=quarantine. The root cause was related to how certain email headers were being handled.
We have implemented a fix and will continue to monitor closely. While there may still be some residual impact to messages with elongated headers and as outstanding retries and queue delays clear over the next ~72 hours, we expect impact to remain limited.
May 1, 11:52 EDT
Monitoring - In April, some customers may have experienced intermittent DMARC failures on messages to Microsoft-hosted inboxes. Impact was most visible for senders with a DMARC policy of p=reject or p=quarantine. The root cause was related to how certain email headers were being handled.
We have implemented a fix and will continue to monitor closely. While there may still be some residual impact to messages as outstanding retries and queue delays clear over the next ~72 hours, we expect impact to remain limited.
Apr 30, 11:10 EDT
Resolved - Between April 23 and April 29, some customers in experienced issues with publishing Instagram posts. This was caused by an integration issue. As of April 29 6:17 PM, our social publishing tools are working properly and the incident has been fully resolved.
HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Apr 29, 22:15 EDT
Monitoring - We have mitigated an issue with publishing of some Instagram posts since April 23. We're monitoring performance closely to make sure the tools recover properly.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Apr 29, 16:02 EDT
Identified - We estimate that we will restore service in the next several days.
We are mitigating impact from an issue with a third-party integration, and monitoring the situation closely. If you have trouble posting, please retry or post directly on Instagram.
We will be back with an update within 6 hours.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Apr 30, 10:44 EDT
Resolved - Between 9:45 AM EDT (UTC -04:00) on Apr 30, 2026 and 10:30 AM EDT (UTC -04:00) on Apr 30, 2026, some customers experienced errors when creating or updating workflows. The root cause has been resolved, and no data was lost. We apologize for any inconvenience and appreciate your patience as we resolved the issue.
Apr 30, 09:59 EDT
Investigating - We are investigating an issue impacting Workflows. We will provide an update when we have more information.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Jun 8, 02:56 UTC
Resolved - On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions.
We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.
Jun 8, 02:36 UTC
Identified - We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions.
Our engineering team is actively working on a resolution. We will provide an update within the next hour.
Jun 8, 01:53 UTC
Investigating - We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.
Jun 2, 16:51 UTC
Resolved - On June 2, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours.
Jun 2, 15:32 UTC
Investigating - We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an update here within the next hour, or sooner if new information becomes available.
Jun 1, 13:23 UTC
Resolved - This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence.
If you continue to experience issues, please contact Atlassian Support.
We apologise for the disruption and thank you for your patience.
Jun 1, 09:08 UTC
Monitoring - We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring the stability.
Jun 1, 08:06 UTC
Identified - We have identified an issue causing degraded performance for Jira Software, Jira Work Management, and Jira Service Management in the EU region. affected users may experience 5XX errors when accessing issues, boards, and navigation.
Our engineering team is actively working on a resolution. We will provide an update within the next hour.
Jun 1, 08:06 UTC
Investigating - We are investigating cases of partial-outage for Jira-software in the EU Region.
We will provide more details within the next hour.
May 14, 09:41 UTC
Resolved - This incident has been resolved.
During the incident window, some customers using Atlassian Assist experienced excessive notifications as our team replayed delayed events caused by this prior incident:
https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7
Our engineering team identified and addressed the issue. All services have fully recovered, and notification delivery is operating normally. No data loss occurred as a result of this incident.
We apologize for the disruption and any confusion caused by the excessive notifications.
May 14, 03:52 UTC
Update - Some of the users continue to experience an excessive number of notifications arriving from JSM (Assist) as our team replays delayed events experienced in this prior incident:
https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7
At this time we expect that these notifications will be arriving for the next few hours, until the recovery of the delayed events are processed which is taking longer than expected (ETA approx. 4 hours). We will provide further updates within 6 hours or sooner if the recovery occurs.
May 14, 01:15 UTC
Investigating - We are aware that some users are experiencing an excessive number of notifications arriving from Jira Service Management (Assist) as our team replays delayed events experienced in this prior incident:
https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7
At this time we expect that the vast majority of these notifications will be arriving within the next two hours.
We will provide further update at that time or sooner if further information becomes available.
May 14, 06:48 UTC
Resolved - All products and services impacted by this incident should now be fully recovered, and this incident is resolved.
May 14, 06:41 UTC
Update - We are approaching full system recovery at this time, and are performing final confirmations that services are restored.
May 14, 06:40 UTC
Update - We are now able to see recovery for all impacted products, and users should be able to access their products as expected.
Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.
May 14, 05:43 UTC
Monitoring - Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products.
We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.
May 14, 05:34 UTC
Update - Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.
At this time, Atlassian customers should also be able to once again raise support requests with our team.
We will provide further update within an hour as we are able to progress mitigating this issue.
May 14, 05:24 UTC
Update - It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.
We are continuing to receive reports about expanded product impact resulting from this incident.
While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.
We will provide further update within one hour, or sooner as further information becomes available.
May 14, 05:11 UTC
Identified - Further confirmations of impacted products have now been added to the incident.
Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.
May 14, 05:03 UTC
Investigating - We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time.
We will provide further update within one hour or sooner as information is available.
Jun 4, 20:59 UTC
Resolved - This incident has been resolved. Between approximately 17:00 and 20:30 UTC, a subset of sites using Edge Functions experienced elevated 504 error rates. We applied a mitigation and error rates have remained at normal levels since. We apologize for the impact to your sites and visitors.
Jun 4, 20:42 UTC
Monitoring - We have applied a mitigation and error rates for affected sites have returned to normal levels as of approximately 20:30 UTC. We are continuing to monitor the situation and will provide a final update once we have confirmed full recovery
Jun 4, 20:34 UTC
Identified - We have identified an issue with a subset of our Edge Functions infrastructure causing elevated 504 errors for some sites beginning at approximately 17:00 UTC. We are applying mitigations and error rates are improving. Customers do not need to take any action. We will continue to provide updates here.
Jun 4, 20:24 UTC
Investigating - Our team is investigating an increase in observed error rates affecting a subset of sites that use Edge Functions. Affected sites may see elevated 504 responses or slow page loads beginning at approximately 17:00 UTC. We are actively working to identify the cause and will provide updates here.
May 29, 15:30 UTC
Resolved - Between May 29th at 15:30 UTC till June 2 6:08 UTC, we experienced sporadic issues with Blobs in our Sydney region, affecting any Function using Blobs, including the ones that are generated by the framework runtimes. Our team has deployed a fix and the errors have subsided.
May 27, 14:17 UTC
Resolved - This incident has been resolved, and builds have returned to functioning normally.
May 27, 12:58 UTC
Identified - In addition to delayed builds, we are also experiencing build failures due to the current incident at Github.
May 27, 12:13 UTC
Investigating - We are currently experiencing delays in our build pipeline due to a current incident at Github.
May 26, 13:44 UTC
Resolved - This incident has been resolved.
May 26, 13:23 UTC
Monitoring - We have implemented a fix and are monitoring results. Some customers may have experienced slow or failed image requests. We will continue to monitor image delivery and provide an update once the issue is fully resolved.
May 26, 13:14 UTC
Investigating - We are continuing to investigate issues affecting image delivery. Some customers may continue to see slow or failed image requests. We are working to identify the cause and will share more information when available.
May 25, 17:32 UTC
Resolved - This incident has been resolved.
May 25, 15:53 UTC
Monitoring - outbound email delivery has been restored and emails are now processing successfully. Some delays may continue while queued messages are delivered. We are continuing to monitor the recovery closely
May 25, 15:31 UTC
Identified - We are currently investigating an issue affecting outbound email delivery for some Netlify services, including support-related communications. Our team is working with our email provider to restore service as quickly as possible
Apr 29, 20:49 UTC
Resolved - This incident has been resolved.
Apr 29, 20:49 UTC
Update - We are continuing to investigate this issue.
Apr 29, 20:07 UTC
Investigating - We are currently investigating this issue.
Apr 29, 19:35 UTC
Resolved - This incident has been resolved.
Apr 29, 18:47 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 29, 16:48 UTC
Investigating - We are currently investigating this issue.
Apr 28, 22:24 UTC
Resolved - This incident has been resolved.
Apr 28, 21:04 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 28, 19:55 UTC
Investigating - We are currently investigating this issue.
Apr 27, 22:30 UTC
Resolved - This incident has been resolved.
Apr 27, 22:28 UTC
Update - We are continuing to investigate this issue.
Apr 27, 21:06 UTC
Investigating - We are currently investigating this issue.
Apr 1, 13:12 UTC
Resolved - This incident has been resolved.
Apr 1, 12:20 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 1, 10:05 UTC
Investigating - We are observing increased errors in viewing packages and authentication on npmjs website. We are investigating this issue.
All impacted services have now fully recovered.
Affected components
- Conversations (Operational)
All impacted services have now fully recovered.
Affected components
- Conversations (Operational)
Incorrectly suspended users have been restored access and received an email about their account and subscription information, if relevant. Impacted services have recovered.
Affected components
- VS Code extension (Operational)
- Codex API (Operational)
- Login (Operational)
- Codex Web (Operational)
- CLI (Operational)
- App (Operational)
All impacted services have now fully recovered.
Affected components
- Voice mode (Operational)
May 29, 07:30 PDT
Resolved - Customers have experienced elevated latency occurring in US East region from 6:30 AM to 8:58 AM Pacific time. Our engineers have investigated and resolved the issue. All impacted services are operating normally.
May 22, 11:50 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with SenderAuth and Whitelabel domains has been resolved. All services are now operating normally at this time.
May 22, 10:51 PDT
Monitoring - Our engineers have implemented a fix and are monitoring system performance. We will provide another update in an hour or as soon as more information becomes available.
May 22, 10:30 PDT
Investigating - Starting around 10:17AM on May 22 2026, our engineers began investigating an issue affecting SenderAuth and Whitelabel domains. A subset of customers may be experiencing errors when attempting to make updates to their whitelabel domains. Mail send is not impacted. We will provide another update as soon as more information becomes available.
May 14, 10:47 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with Sender Engagement Quality (SEQ) API endpoint has been resolved. All services are now operating normally at this time.
May 14, 10:12 PDT
Monitoring - Our engineers have implemented a fix and are monitoring system performance. SendGrid Engagement Quality API endpoint is now working as expected with API keys. We will provide another update in 30 minutes or as soon as more information becomes available.
May 14, 09:53 PDT
Identified - Our engineers have identified the issue and are working toward a fix. We will provide another update in 1 hour or as soon as more information becomes available.
May 14, 09:45 PDT
Investigating - Starting around 9:34 AM on May 14th 2026, our engineers began investigating an issue with the Sender Engagement Quality (SEQ) API endpoint not working as expected. Users may experience the Sender Engagement Quality (SEQ) API endpoint not working with the correct permission keys. This does not impact mail send. We will provide another update in 1 hour or as soon as more information becomes available.
May 13, 08:30 PDT
Resolved - Customers in US-East may have experienced intermittent high mail send latency from 5/13/2026 to 5/27/2026. Our engineers have investigated and resolved the issue. All impacted services are operating normally.
May 12, 17:22 PDT
Resolved - Our engineers have monitored the fix and confirmed all services are now operating normally.
May 12, 16:48 PDT
Monitoring - Between 16:10 PDT and 16:27 PDT on 05/12/2026, our engineers began investigating an issue with a subset of services experiencing 5xx errors. Users may have experienced issues when accessing subusers, authenticating domains and link branding records, accessing the account, and checking account stats.
This does not impact mail send.
Our engineers have implemented a fix and are monitoring system performance. We will provide another update in an hour or as soon as more information becomes available.
Jun 2, 07:45 UTC
Resolved - Between 06:00-07:00 UTC, we saw increased numbers of API errors in the EU region. The largest impact was between 06:46-07:00. We've implemented a fix and we're no longer seeing elevated errors.
May 28, 14:28 UTC
Resolved - The issue has been resolved
May 28, 14:20 UTC
Monitoring - The fix has been deployed and we are monitoring the situation
May 28, 13:55 UTC
Identified - We have identified the cause of the issue and are deploying a fix
May 28, 13:40 UTC
Investigating - We are currently investigating the issue
May 26, 08:28 UTC
Resolved - Access to sentry.io is now fully operational
May 26, 08:19 UTC
Monitoring - We have implemented a fix and are monitoring.
May 26, 08:11 UTC
Investigating - We are currently investigating an issue causing 500 errors and preventing access to Sentry.io organizations in the DE region. The US region remains fully operational.
May 22, 08:23 UTC
Resolved - Latency for sentry.io has returned to normal.
May 22, 08:08 UTC
Monitoring - We have implemented a fix and are monitoring.
May 22, 07:42 UTC
Investigating - We are currently investigating slow page loads on sentry.io.
May 19, 18:48 UTC
Resolved - Ingestion for symbolicated issues is back to normal.
May 19, 17:41 UTC
Update - We are implementing a fix and monitoring the situation. Non-symbolicated issues are not experiencing delays.
May 19, 15:58 UTC
Investigating - We are experiencing ingestion delays for errors in the US region.
Jun 4, 16:07 EDT
Resolved - This incident has been resolved.
Jun 4, 16:00 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 4, 15:18 EDT
Identified - The issue has been identified and a fix is being implemented.
Jun 4, 14:52 EDT
Investigating - We are currently investigating errors on submitting translations feedback form
May 27, 19:41 EDT
Resolved - This incident has been resolved.
May 27, 19:28 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
May 27, 18:51 EDT
Investigating - We are currently investigating reports of issues with content asignments
May 8, 00:09 EDT
Resolved - This incident has been resolved.
May 7, 21:13 EDT
Monitoring - There is an ongoing AWS outage impacting some of the services.
Our platform and APIs remain fully operational and stable.
We're keeping a close eye on the situation as AWS work through recovery.
May 7, 20:18 EDT
Investigating - We're experiencing an elevated level of API errors and are currently looking into the issue.
Apr 27, 12:44 EDT
Resolved - This incident has been resolved.
Apr 27, 10:52 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 27, 06:36 EDT
Investigating - Our Engineering team is currently investigating intermittent performance degradations to the Smartling translation platform and API. We will provide more information as it becomes available. Global Delivery Network services remain operational.
Feb 19, 12:53 EST
Resolved - This incident has been resolved.
Feb 19, 12:16 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 19, 11:18 EST
Identified - The issue has been identified and a fix is being implemented.
Feb 19, 10:45 EST
Investigating - We are currently investigating delays in processing file published callbacks and webhooks.
Our customers are reporting that they're able to access Tempo now.
Affected components
- Capacity Planner (Operational)
- Timesheets (Operational)
- Financial Manager (Operational)
Incident has been resolved.
Affected components
- Capacity Planner (Operational)
- Timesheets (Operational)
- Financial Manager (Operational)
The migration of Timesheets, Capacity Planner, and Financial Manager to Forge: https://www.tempo.io/product-news/tempo-moves-to-forge is underway, but the automatic rollout did not start on March 31, 2026 as planned. The automatic migration to Forge is tentatively scheduled to begin on June 15, 2026. You have the option to do either of the following: • Perform a manual update Review the expected changes (see links below) and assess any impacts to your workflows. If the impact is manageable, we recommend updating manually to control the timing of your instance’s migration. • Wait for automatic update The automatic rollout will occur gradually, so we are unable to confirm the exact date your instance will be updated. It will not be possible to schedule, delay, or opt out once started. After your instance is updated, you will receive an in-app notification confirming the change. You can also verify if your instance has migrated to Forge by checking the app versions: https://tempo-io.atlassian.net/wiki/spaces/DRAFTTIMESHEETS/pages/5679415354/Timesheets+Migration+to+Forge+FAQs#How-to-Check-Your-Current-Version. Breaking changes Most of the migration is seamless, but a few things will change that may affect you, particularly around JQL filters: • JQL filter syntax – issueInternal, Account, Tempo Team, and custom field IDs • Tempo Panels in Jira issue view • Keyboard shortcuts • OAuth app URLs Please review the relevant documentation to prepare for changes that might affect you: • Expected Changes in Timesheets on Forge: https://help.tempo.io/timesheets/latest/expected-changes-in-timesheets-on-forge • Expected Changes in Capacity Planner on Forge: https://help.tempo.io/planner/latest/expected-changes-in-capacity-planner-on-forge • Expected Changes in Financial Manager on Forge: https://help.tempo.io/financialmanager/latest/expected-changes-in-financial-manager-on-forge
We have identified and addressed the root cause of the delays. The issue is now resolved.
Affected components
- Timesheets (Operational)
Jun 4, 14:09 UTC
Resolved - This incident has been resolved.
Jun 4, 12:56 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 4, 10:10 UTC
Investigating - We are currently experiencing a service disruption affecting Upstash Vector in the IAD region.
Initial investigation indicates that the issue is related to a Fly.io networking/routing problem impacting connectivity in the region. The Fly.io team is actively investigating the underlying cause.
We will continue to monitor the situation and provide updates as more information becomes available.
May 30, 07:51 UTC
Resolved - The issue affecting some Upstash Vector indexes in the US-EAST-1 region has been resolved.
Our team investigated the incident and identified the conditions that were contributing to elevated memory pressure on the affected servers. We mitigated those conditions by reducing memory utilization on the impacted nodes, rebalancing affected workloads where needed, and increasing available headroom capacity across the region.
All affected indexes should now be operating normally, and based on the mitigations applied, we do not expect this issue to recur. We apologize for any inconvenience this may have caused.
May 29, 23:44 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 29, 20:18 UTC
Investigating - Some Upstash Vector indexes in the US-EAST-1 region may be experiencing intermittent slowness. Initial investigation indicates this may be related to memory pressure on the affected servers.
Our team is actively investigating the root cause and working to restore normal performance. We will provide updates as soon as more information is available.
May 23, 00:00 UTC
Resolved - This incident has been resolved.
May 22, 23:48 UTC
Monitoring - Upstream issue resolved — new database creation is working again. We're monitoring to confirm full recovery.
May 22, 23:27 UTC
Investigating - New database provisioning is currently failing due to an ongoing upstream provider issue affecting DNS. Existing databases and connections are unaffected — only the creation flow is impacted. We're monitoring the situation and will update once the upstream issue is resolved.
May 14, 17:31 UTC
Resolved - Earlier today, unexpected load on our proxies caused intermittent connection issues for Upstash Redis in the following regions:
us-east-1, us-west-1, ap-southeast-2, and ap-south-1.
During this period, some clients may have seen connection timeouts or elevated error rates when reaching their databases.
Our team identified the issue quickly and applied workarounds to relieve pressure on the affected proxies. Connection health has since been restored and we've been monitoring the regions to confirm everything is stable. All systems are now operating normally.
We appreciate your patience and apologize for any disruption this may have caused.
May 14, 16:00 UTC
Monitoring - A fix has been implemented and we are monitoring.
May 14, 15:49 UTC
Identified - The issue has been identified and a fix is being implemented.
May 14, 15:47 UTC
Monitoring - We identified intermittent connection issues affecting some regions. Fix is being deployed. We'll update the list of affected regions shortly.
May 12, 13:48 UTC
Resolved - This incident has been resolved.
May 12, 12:05 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 12, 10:50 UTC
Identified - The issue has been identified and the fix is being implemented.
May 12, 09:49 UTC
Investigating - Some regions are experiencing connectivity issues due to an ongoing network problem. We are currently investigating
Jun 1, 20:02 UTC
Resolved - This incident has been resolved.
Jun 1, 19:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 1, 19:50 UTC
Identified - The issue has been identified and a fix is being implemented.
Jun 1, 19:21 UTC
Investigating - We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.
May 28, 16:59 UTC
Resolved - This incident has been resolved.
May 28, 16:37 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 28, 16:18 UTC
Identified - The issue has been identified and a fix is being implemented.
May 28, 16:00 UTC
Investigating - We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.
May 27, 05:02 UTC
Resolved - This incident has been resolved.
We've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC.
May 27, 04:50 UTC
Investigating - We are currently investigating this issue.
May 25, 16:22 UTC
Resolved - This incident has been resolved.
May 25, 16:05 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 25, 15:25 UTC
Identified - The issue has been identified and a fix is being implemented.
May 25, 14:58 UTC
Investigating - We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.
May 23, 18:44 UTC
Resolved - This incident has been resolved.
Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt
May 23, 18:21 UTC
Monitoring - GitHub has implemented a fix, and we are monitoring the results.
May 23, 15:46 UTC
Identified - We have identified the issue and are working closely with GitHub to resolve it.
May 23, 14:30 UTC
Update - We are working closely with GitHub to resolve this issue. Failures are intermittent — if your deployment fails, redeploying should resolve it in the meantime. We will provide updates as the situation develops.
May 23, 12:15 UTC
Update - We are continuing to investigate this issue.
May 23, 11:09 UTC
Update - We've been observing increased failures of git operations with GitHub since around 06:00 UTC. Some deployments triggered by GitHub commits might have seen git-related errors in failed build logs.
CLI deployments are unaffected at this time.
May 23, 10:43 UTC
Investigating - We are currently investigating this issue.
Jun 8, 01:55 PDT
Resolved - This incident has been resolved.
Jun 8, 01:41 PDT
Monitoring - Our carrier partner has resolved the issue where a subset of users experiencing issues with Inbound and Outbound Calls for Zoom Phone and Zoom Contact Center in Singapore region. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Jun 8, 01:28 PDT
Identified - We have identified the root cause affecting Inbound and Outbound Calls for Zoom Phone and Zoom Contact Center in Singapore region.
We are working with our carrier partner on a resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Jun 8, 01:06 PDT
Investigating - We are currently investigating an issue related to our carrier which is affecting Inbound and Outbound Calls for Zoom Phone and Zoom Contact Center in Singapore region.
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.
Jun 4, 21:46 PDT
Resolved - This incident has been resolved.
Jun 4, 21:36 PDT
Monitoring - On 06/05/2026, Between 01:28 UTC to 03:23 UTC, Users may have experienced inbound call failures in Unites States.
This incident has been resolved and the affected services have been restored.
Jun 4, 19:44 PDT
Resolved - This incident has been resolved and GIF functionality has been restored for client versions below 7.0.0 and above 7.0.4. Users may need to re-login to send GIFs. Users on affected versions (7.0.0 – 7.0.4) should refer to the support article: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0086088
Jun 2, 11:58 PDT
Update - GIFs are re-enabled for clients on versions below 7.0.0 and above 7.0.4, but users may need to re-login to send GIFs. Users on affected versions (7.0.0 – 7.0.4) can upgrade to 7.0.5 to send GIFs.
Jun 1, 07:04 PDT
Monitoring - GIFs remain enabled for unaffected clients (versions below 7.0.0 and above 7.0.4). Users may need to re-login to use GIFs. We will provide updates as more information becomes available.
May 31, 19:44 PDT
Update - GIFs remains enabled for unaffected clients (versions below 7.0.0 and above 7.0.4). We will provide updates as more information becomes available.
May 30, 19:35 PDT
Update - GIFs have been re-enabled for unaffected clients (versions below 7.0.0 and above 7.0.4). We will provide updates as more information becomes available.
Thank you for your patience.
May 30, 09:00 PDT
Update - We have narrowed down the GIF issue to Zoom client versions 7.0.0 – 7.0.4. We will begin re-enabling the GIF feature on unaffected client versions through this weekend.
We will provide updates as more information becomes available.
Thank you for your patience.
May 29, 21:00 PDT
Update - We have narrowed down the GIF issue to Zoom client versions 7.0.0 – 7.0.4. We will begin re-enabling the GIF feature on unaffected client versions through this weekend.
We will provide updates as more information becomes available.
Thank you for your patience.
May 29, 09:00 PDT
Update - We have narrowed down the GIF issue to Zoom client versions 7.0.0 – 7.0.4. We will begin re-enabling the GIF feature on unaffected client versions starting today through this weekend.
We will provide updates as more information becomes available.
Thank you for your patience.
May 28, 18:13 PDT
Update - We have narrowed down the GIF issue to Zoom client versions 7.0.0 – 7.0.4. We will begin re-enabling the GIF feature on unaffected client versions starting today through this weekend.
We will provide updates as more information becomes available.
Thank you for your patience.
May 28, 16:30 PDT
Update - We continue to investigate the issue with Giphy in Zoom Chat and Zoom In-Meeting Chat. Users may be unable to search or send GIFs. Some users may also experience re-login prompts.
We will provide updates as more information becomes available.
Thank you for your patience.
May 28, 04:39 PDT
Update - We continue to investigate the issue with Giphy in Zoom Chat and Zoom In-Meeting Chat. Users may be unable to search or send GIFs. Some users may also experience re-login prompts.
We will provide updates as more information becomes available.
Thank you for your patience.
May 27, 16:38 PDT
Update - We continue to investigate the issue with Giphy in Zoom Chat and Zoom In-Meeting Chat. Users may be unable to search or send GIFs. Some users may also experience re-login prompts.
We will provide updates as more information becomes available.
Thank you for your patience.
May 27, 09:50 PDT
Identified - We are still investigating the issue with Giphy in Zoom Chat and Zoom In-Meeting Chat.
Users may be unable to search or send GIFs.
Some users may also experience re-login prompts.
We will provide updates as more information becomes available.
Thank you for your patience.
May 27, 06:08 PDT
Monitoring - The issue affecting Giphy in Zoom Chat and Zoom In-Meeting Chat has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
May 27, 02:42 PDT
Update - We are still investigating issue with Giphy in Zoom Chat and Zoom In-Meeting Chat. Users may be unable to search or send GIFs. Some users may also experience re-login prompts.
We will provide updates as more information becomes available.
Thank you for your patience.
May 26, 22:38 PDT
Update - Our team continues to work on the resolution for the service degradation affecting Giphy in Zoom Chat and Zoom In-Meeting Chat. Users may be unable to search or send GIFs. Some users may also experience re-login prompts.
We will provide updates as more information becomes available.
Thank you for your patience.
May 26, 20:29 PDT
Update - We are still investigating issue with Giphy in Zoom Chat and Zoom In-Meeting Chat. Users may be unable to search or send GIFs. Some users may also experience re-login prompts.
We will provide updates as more information becomes available.
Thank you for your patience.
May 26, 19:06 PDT
Update - Our team continues to work on the resolution for the service degradation affecting Giphy in Zoom chat and Zoom in-meeting chat.
We will keep you informed with timely updates as progress is made.
Thank you for your patience.
May 26, 16:08 PDT
Update - Our team continues to work on the resolution for the service degradation affecting Giphy in Zoom chat and Zoom in-meeting chat.
We will keep you informed with timely updates as progress is made.
Thank you for your patience.
May 26, 11:25 PDT
Identified - We have successfully identified the root cause affecting Giphy In Zoom Chat and Zoom In-Meeting Chat.
Our team is actively working on a resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
May 26, 11:22 PDT
Investigating - We are currently investigating a service degradation with Giphy.
Users may be unable to search or send GIFs In Zoom Chat and Zoom In-Meeting Chat.
We appreciate your patience as we work to resolve this issue.
Jun 3, 19:08 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Jun 3, 18:44 PDT
Monitoring - The issue affecting Slides and Sheets has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Jun 3, 18:43 PDT
Identified - We have identified the service degradation affecting Slides and Sheets.
Our team is actively working on a resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Jun 3, 18:12 PDT
Investigating - We are currently investigating a service degradation with Slides and Sheets
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.
Jun 1, 09:47 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Jun 1, 08:50 PDT
Monitoring - On 1 June 2026, between 11:00 and 14:50 UTC, a subset of customers experienced intermittent issues submitting inquiries through our Contact Sales pages. The issue has been resolved, and all services are operating normally.
Our team will continue to monitor the situation closely and keep you informed of any further developments.