Status Tracker v0.23
Dec 14, 02:18 UTC
Completed – The scheduled maintenance has been completed.
Dec 14, 01:18 UTC
In progress – Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 14, 01:17 UTC
Scheduled – On Friday, December 13, 2024, at 5:00 PM PST, Figma began scheduled maintenance, which will continue for a few more minutes. During this time, customers may experience brief periods of downtime.
Dec 14, 01:10 UTC
Completed – The scheduled maintenance has been completed.
Dec 14, 01:00 UTC
In progress – Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 13, 20:14 UTC
Scheduled – On Friday Dec 13, 2024 at 5pm PST Figma will be undergoing planned maintenance. There may be a brief period (few minutes) of downtime customers may face while using Figma.
Dec 13, 16:03 PST
Resolved – The issue has been resolved.
Starting at 6:35 AM PT, some customers experienced elevated error rates in the Vision API. A fix was implemented, and the issue was fully resolved at 3:58 PM PT.
Dec 13, 14:57 PST
Monitoring – A fix has been implemented and we are monitoring the results
Dec 13, 12:47 PST
Investigating – We are currently experiencing degraded performance for the Vision API. We are currently investigating and will post an update as soon as possible.
Dec 13, 23:49 UTC
Resolved – Between 08:30 UTC and 22:19 UTC, we experienced an issue that caused “View Remaining XX comments” not to load for Jira Service Management and Jira. The issue has been resolved and the service is operating normally.
Dec 13, 22:17 UTC
Update – We are finalizing a fix and will deploy it soon.
Workaround:
Users can navigate to the All tab and then revisit the Comments tab. This resolves the issue, allowing the remaining comments to be viewed.
Dec 13, 20:50 UTC
Update – We are actively working on a hotfix for this incident. The update is taking longer than expected; we will provide an update in one hour.
Workaround:
Users can navigate to the All tab and then revisit the Comments tab. This resolves the issue, allowing the remaining comments to be viewed.
Dec 13, 16:17 UTC
Update – We are actively working on a hotfix for this incident. The process of building and progressively rolling out the fix is expected to take approximately 4 hours. We will update here if there are any changes in the timeline
Workaround:
Users can navigate to the All tab and then revisit the Comments tab. This resolves the issue, allowing the remaining comments to be viewed.
Dec 13, 14:45 UTC
Update – We continue to work on the HOT-fix for this incident.
We will post another update in one hour.
Dec 13, 13:27 UTC
Identified – We have identified the cause for the issue where users are not able to load more comments through View Remaining XX comments.
A Hot-fix is being applied at the moment.
This is currently affecting Jira Service Management, and Jira Cloud customers.
As a workaround: users need to go to All tab and visit comments tab again. This resolves the issue and then remaining comments can be viewed
We will provide more details within the next hour.
Dec 13, 23:49 UTC
Resolved – Between 08:30 UTC and 22:19 UTC, we experienced an issue that caused “View Remaining XX comments” not to load for Jira Service Management and Jira. The issue has been resolved and the service is operating normally.
Dec 13, 22:17 UTC
Update – We are finalizing a fix and will deploy it soon.
Workaround:
Users can navigate to the All tab and then revisit the Comments tab. This resolves the issue, allowing the remaining comments to be viewed.
Dec 13, 20:50 UTC
Update – We are actively working on a hotfix for this incident. The update is taking longer than expected; we will provide an update in one hour.
Workaround:
Users can navigate to the All tab and then revisit the Comments tab. This resolves the issue, allowing the remaining comments to be viewed.
Dec 13, 16:17 UTC
Update – We are actively working on a hotfix for this incident. The process of building and progressively rolling out the fix is expected to take approximately 4 hours. We will update here if there are any changes in the timeline
Workaround:
Users can navigate to the All tab and then revisit the Comments tab. This resolves the issue, allowing the remaining comments to be viewed.
Dec 13, 14:45 UTC
Update – We continue to work on the HOT-fix for this incident.
We will post another update in one hour.
Dec 13, 13:27 UTC
Identified – We have identified the cause for the issue where users are not able to load more comments through View Remaining XX comments.
A Hot-fix is being applied at the moment.
This is currently affecting Jira Service Management, and Jira Cloud customers.
As a workaround: users need to go to All tab and visit comments tab again. This resolves the issue and then remaining comments can be viewed
We will provide more details within the next hour.
Dec 13, 13:45 PST
Resolved – The issue affecting the loading of Logs ( Beta ) feature in Zap history has been resolved. The incident occurred at approximately 16:00 UTC, and was successfully fixed by 21:30 UTC.
Our team promptly identified and solved the problem, ensuring that all Zap History logs are now displaying correctly.
If you encounter any further issues, please don’t hesitate to contact our Support Team.
We thank you for your understanding and patience during this time.
Dec 13, 11:33 PST
Monitoring – Our team has now implemented a fix for our log reporting tools to clear up this Logs ( Beta ) readout.
Kindly be assured that your Zaps and runs have not been affected, this problem was only with the visuals.
We want to assure you that no data has been lost during this incident. While there was a Contact support error message popping up earlier, this has now been addressed, and the issue is resolving. However, there might be an occurrence of one-off errors, but these should be rare.
We’re keeping a close eye on the situation and continue to monitor the status. If you do encounter any further issues, please do not hesitate to contact our Support Team here:
https://zapier.com/app/get-help
Dec 13, 10:45 PST
Identified – We have identified an issue affecting the Logs ( Beta ) feature in Zap history.
As a result of this problem, logs may not be displaying as expected and users might encounter an error message or an unresponsive blank panel when trying to access these logs.
The issue we have identified is related to our log reporting tools and how this displays in the history. We want to reassure you that there is no data loss associated with this incident. All Zaps and operations are functioning as normal. This issue is primarily affecting the viewing of logs in the history dashboard.
We are actively working on resolving the matter as quickly as possible. However, the issue might still occur sporadically as we enhance the log reporting function.
If you have further questions, please reach out to our Support Team here:
https://zapier.com/app/get-help
Dec 13, 10:20 PST
Investigating – As of 4:04 PM UTC, you may be seeing issues when loading the Logs ( Beta ) feature in your runs within Zap History.
Our Team is currently investigating this, and we appreciate your patience as we work to resolve this issue.
If you need further assistance, please do not hesitate to reach out to our Support Team: https://zapier.com/app/get-help.
The issue with Vertex Gemini API has been resolved for all affected users as of Friday, 2024-12-13 09:00 US/Pacific.
Incident began at 2024-12-13 01:07 and ended at 2024-12-13 11:01 (all times are US/Pacific).
Affected products: Vertex Gemini API
We thank you for your patience while we worked on resolving the issue.
Affected locations: Singapore (asia-southeast1), Iowa (us-central1), South Carolina (us-east1), Las Vegas (us-west4)
The issue with Vertex Gemini API has been resolved for all affected users as of Friday, 2024-12-13 09:00 US/Pacific.
Incident began at 2024-12-11 18:00 and ended at 2024-12-13 10:54 (all times are US/Pacific).
Affected products: Vertex Gemini API
We thank you for your patience while we worked on resolving the issue.
The issue with Vertex Gemini API has been resolved for all affected users as of Friday, 2024-12-13 09:00 US/Pacific.
Incident began at 2024-12-11 18:00 and ended at 2024-12-13 10:54 (all times are US/Pacific).
Affected products: Vertex Gemini API
We thank you for your patience while we worked on resolving the issue.
The issue with Google Cloud Support has been resolved for all affected projects as of Friday, 2024-12-13 10:14 US/Pacific.
Incident began at 2024-12-13 04:21 and ended at 2024-12-13 10:28 (all times are US/Pacific).
Affected products: Google Cloud Support
We thank you for your patience while we worked on resolving the issue.
Affected locations: Global