Investigate CF 520 during large generic package upload

In an effort to crack down on the 5XX errors, I created a Google Form to capture the requests times, ray IDs and other metadata. I shared this with some people in support already. If you see more cases being reported, please redirect them to that form. Issues clearly do not scale for this type of thing. This is safe to be shared on public issues, the Form requires a GitLab Google sign-in

The responses are captures in this spreadsheed which is readable by everyone in the infrastructure group.

Current Status

We have received an update from Cloudflare, that there was indeed an issue. We have received an RCA on this. Before posting anything concrete on that here I would like to check back with them about what is safe to share from that document.

But since 2022-04-01 23:42 UTC they have deployed a fix.

There are still some requests failing. This is being investigated.

More information will be added as we investigate the issue.

Timeline

View recent production deployment and configuration events (internal only)

All times UTC.

2021-04-15

  • 21:35 - @calebw declares incident in Slack.

Corrective Actions

Corrective actions should be put here as soon as an incident is mitigated, ensure that all corrective actions mentioned in the notes below are included.

  • ...

Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in out handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.


Click to expand or collapse the Incident Review section.

Incident Review

Summary

  1. Service(s) affected:
  2. Team attribution:
  3. Time to detection:
  4. Minutes downtime or degradation:

Metrics

Customer Impact

  1. Who was impacted by this incident? (i.e. external customers, internal customers)
    1. ...
  2. What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
    1. ...
  3. How many customers were affected?
    1. ...
  4. If a precise customer impact number is unknown, what is the estimated impact (number and ratio of failed requests, amount of traffic drop, ...)?
    1. ...

What were the root causes?

  • ...

Incident Response Analysis

  1. How was the incident detected?
    1. ...
  2. How could detection time be improved?
    1. ...
  3. How was the root cause diagnosed?
    1. ...
  4. How could time to diagnosis be improved?
    1. ...
  5. How did we reach the point where we knew how to mitigate the impact?
    1. ...
  6. How could time to mitigation be improved?
    1. ...
  7. What went well?
    1. ...

Post Incident Analysis

  1. Did we have other events in the past with the same root cause?
    1. ...
  2. Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
    1. ...
  3. Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
    1. ...

Lessons Learned

  • ...

Guidelines

Resources

  1. If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)
Edited by Hendrik Meyer (xLabber)