drupal.org-is-down-terminal.txt

HTTP/1.1 200 OK
Accept-Ranges: bytes
Age: 96
Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0
Connection: keep-alive
Content-Encoding: gzip
Content-Length: 26
Content-Security-Policy: frame-ancestors 'self'
Content-Type: text/html; charset=utf-8
Date: Sat, 13 Feb 2016 11:06:49 GMT
Fastly-Debug-Digest: 09a5a16ab4c6a17739170a964b2b8cdcf5e3ef6581199295c42914f8dab9a7c1
Server: Apache
Strict-Transport-Security: max-age=10886400; includeSubDomains; preload
Vary: Accept-Encoding
Via: 1.1 varnish
Via: 1.1 varnish
Via: 1.1 varnish
X-Cache: MISS, HIT, HIT
X-Cache-Hits: 3, 16
X-Cache-Svr: www7.drupal.org
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Served-By: cache-sea1927-SEA, cache-ams4133-AMS
x-host: www.drupal.org
x-url: /

This is the entire response.

Same here, white page, a bit different the bottom values

X-Cache:MISS, MISS, MISS
X-Cache-Hits:0, 0
X-Cache-Svr:www2.drupal.org
X-Content-Type-Options:nosniff
X-Frame-Options:SAMEORIGIN
x-host:www.drupal.org
X-Served-By:cache-sea1925-SEA, cache-lhr6324-LHR
x-url:/

So it appears that the response goes through three (!) layers of Varnish, and in my case it was miss → hit → hit, in your case miss → miss → miss. Different page probably, but still, wow, that seems entirely unnecessary.

@wimleers 2 of those are fastly. I'm going to guess that's a feature they call Shield: https://docs.fastly.com/guides/performance-tuning/shielding. where they route all requests from all their different locations through a single location. Resulting in fewer requests to origin.

I guess the third is then drupal.org's own varnish server, which at this point probably only serves as a load balancer ;)