Day: December 18, 2024

Cloudflare – LAX (Los Angeles) on 2024-12-18

by

Dec 18, 21:30 UTC
Completed – The scheduled maintenance has been completed.

Dec 18, 09:00 UTC
In progress – Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dec 16, 20:55 UTC
Update – We will be performing scheduled maintenance in LAX (Los Angeles) datacenter on 2024-12-18 between 09:00 and 21:30 UTC.

Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.

You can now subscribe to these notifications via Cloudflare dashboard and receive these updates directly via email, PagerDuty and webhooks (based on your plan): https://developers.cloudflare.com/notifications/notification-available/#cloudflare-status.

Dec 13, 22:32 UTC
Scheduled – We will be performing scheduled maintenance in LAX (Los Angeles) datacenter on 2024-12-18 between 09:00 and 14:00 UTC.

Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.

You can now subscribe to these notifications via Cloudflare dashboard and receive these updates directly via email, PagerDuty and webhooks (based on your plan): https://developers.cloudflare.com/notifications/notification-available/#cloudflare-status.

GitLab – Redis Cluster Saturation

by
December 18, 2024 15:05 UTC
Investigating – We’re experiencing saturation in our Redis cluster. The investigation is still ongoing. Users might get 500 errors intermittently. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19025

December 18, 2024 15:48 UTC
Monitoring – We have identified the cause of the issue and have taken the necessary measures to mitigate it. We are now monitoring Redis before marking the incident as resolved. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19025

December 18, 2024 16:30 UTC
Resolved – We have confirmed our mitigation efforts were successful. We are now marking this incident as resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19025

Supabase – Maintenance required on Supavisor in multiple regions.

by

Dec 18, 14:00 UTC
Completed – The scheduled maintenance has been completed.

Dec 18, 12:00 UTC
In progress – Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dec 17, 11:46 UTC
Scheduled – We will be performing maintenance on Supavisor on 2024-12-18 at 12:00UTC.

The following regions will be affected:

* ap-east-1
* ca-central-1
* eu-west-3
* sa-east-1

Connections to Supavisor in the effected regions may be temporarily disconnected during this period as we perform this required maintenance.

Jira Work Management – Issues with attachments, including viewing previews, downloading and uploading

by

Dec 18, 13:36 UTC
Resolved – This incident has been resolved.

Dec 18, 13:13 UTC
Monitoring – A fix has been implemented and we are monitoring the result.

Dec 18, 12:58 UTC
Update – We are continuing to work on a fix for this issue.

Dec 18, 12:54 UTC
Identified – We have identified the issue and we are working to fix the issue.

Bitbucket – Issues with attachments, including viewing previews, downloading and uploading

by

Dec 18, 13:35 UTC
Resolved – This incident has been resolved.

Dec 18, 13:15 UTC
Monitoring – A fix has been implemented and we are monitoring the result.

Dec 18, 12:53 UTC
Update – We are continuing to work on a fix for this issue.

Dec 18, 12:51 UTC
Identified – We have identified the issue and we are working to fix the issue.