Skip to content

Incident detail

Performance degradation in APAC/Singapore

At this time we are resolving this incident. If you continue to experience performance degradation in the Singapore area, please open a support ticket. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

Resolved incidentMinor

Timeline window

to

Get alerted the next time GitLab breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We're experiencing degraded package, artifact, and registry download speed in APAC/Singapore region due to elevated CDN/Cloudflare latency. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  2. Investigating

    We're experiencing degraded package, artifact, and registry download speed in APAC/Singapore region due to elevated CDN/Cloudflare latency. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  3. Investigating

    We are still investigating the cause for the performance degradation. There are no material updates at the moment. The problem is tracked under https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  4. Investigating

    We are still investigating the cause for the performance degradation. There are no material updates at the moment. The problem is tracked under https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  5. Monitoring

    Cloudflare confirmed the traffic degradation was resolved, with recovery observed at approximately 13:40 UTC. Our application and backend checks remained healthy during the degradation, supporting that the impact was outside the GitLab application stack. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  6. Monitoring

    Cloudflare confirmed the traffic degradation was resolved, with recovery observed at approximately 13:40 UTC. Our application and backend checks remained healthy during the degradation, supporting that the impact was outside the GitLab application stack. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  7. Monitoring

    No material updates at this time. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  8. Monitoring

    No material updates at this time. We will continue to monitor the situation. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  9. Monitoring

    At this time the situation is unchanged. We will continue to monitor. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  10. Monitoring

    At this time the situation is unchanged. We will continue to monitor. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  11. Monitoring

    We're still monitoring this incident. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  12. Monitoring

    We're still monitoring this incident. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

  13. Resolved

    At this time we are resolving this incident. If you continue to experience performance degradation in the Singapore area, please open a support ticket. More details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22981.

Keep exploring

More from GitLab

Neighboring incidents on GitLab's timeline and the rest of their record on OutageDeck.