Jan 9, 21:55 UTC
Investigating – We have identified an incident that caused the components to disappear from the field and affected our Jira, Jira work management and Jira Service Desk Cloud customers. As of now, we do not have a root cause for the incident. We are investigating and will post updates within the next hour.
Day: January 9, 2025
Jira Work Management – Component field value not available
Jan 9, 21:53 UTC
Investigating – We have identified an incident that caused the components to disappear from the field and affected our Jira, Jira work management, and Jira Service Desk Cloud customers. As of now, we do not have a root cause for the incident. We are investigating and will post updates within the next hour.
GitLab – Packages on GitLab.com (packages.gitlab.com) become unavailable sporadically with 502 errors.
January 9, 2025 11:45 UTC
Investigating – We are currently investigating an incident that is causing packages on GitLab.com (packages.gitlab.com) to become unavailable sporadically with 502 errors.
Investigating – We are currently investigating an incident that is causing packages on GitLab.com (packages.gitlab.com) to become unavailable sporadically with 502 errors.
More about the incident can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 12:02 UTC
Investigating – We’re still investigating the root cause for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com).
More about the incident and its updates can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 12:17 UTC
Investigating – We’re still investigating the root cause for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com).
More about the incident and its updates can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 12:33 UTC
Investigating – We’re still investigating the root cause for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com).
More about the incident and its updates can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 12:48 UTC
Investigating – We’re still investigating the root cause for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com).
More about the incident and its updates can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 13:09 UTC
Identified – We’ve identified the root cause for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com) and working on a fix.
More about the incident and its updates can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 13:43 UTC
Identified – We’re working on implementing the fix for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com).
More about the incident and its updates can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 14:17 UTC
Identified – We’re still working on implementing the fix for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com).
More about the incident and its updates can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 14:49 UTC
Identified – We’re still working on implementing the fix for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com).
More about the incident and its updates can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 15:22 UTC
Identified – We’re still working on implementing the fix for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com).
More about the incident and its updates can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 15:54 UTC
Identified – We’re still working on implementing the fix for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com).
More about the incident and its progress can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 16:30 UTC
Identified – We’re still working on implementing the fix for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com).
More about the incident and its progress can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 18:13 UTC
Monitoring – The fix for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com) has been implemented, and is processing now.
More about the incident and its progress can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 19:53 UTC
Monitoring – No updates at this time. The fix for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com) is still processing.
More about the incident and its progress can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
January 9, 2025 21:55 UTC
Monitoring – The fix for the sporadic unavailability of packages on GitLab.com (packages.gitlab.com) is ongoing. We expect it to take about 20 hours, and will post updates every 4 hours.
More about the incident and its progress can be read here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19091
Docusign – A subset of customers may experience delayed envelopes in Navigator and errors with Bulk Send (DIRCA-2068)
Jan 9, 21:08 UTC
Monitoring – Errors with Bulk Send were mitigated with the earlier updates. A subset of customers may not be able to re-use Bulk Send recipient lists. A subset of customers are still experiencing delays with envelopes populating in Navigator. New envelopes are populating normally
Jan 9, 19:31 UTC
Identified – A subset of customers may experience errors with Bulk Send. This is being investigated
Jan 9, 17:37 UTC
Monitoring – A subset of eSign customers may experience delays in envelopes showing in Navigator. An update was made and new envelopes are no longer affected. We are working to process a small number still affected
Make – Delays on queue processing
Jan 9, 21:38 CET
Resolved – This incident has been resolved
Jan 8, 22:21 CET
Monitoring – We have applied a fix and we are currently monitoring the zone.
Jan 8, 19:13 CET
Investigating – We are currently facing an issue where some of the users might experience a delay on the processing of the queues records on their scenarios. That does not affects all scenarios.