Nabeel S (Feb 06 2026 at 05:13): Nabeel S (Feb 06 2026 at 05:13):Is it just me, or is the website down? https://changelog.com/
Nabeel S (Feb 06 2026 at 05:33):Ping is resolving, so maybe not DNS this time? :-D
Jarvis (Feb 06 2026 at 05:35):Nabeel S said:
Is it just me, or is the website down? https://changelog.com/
Still working for me:
nslookup changelog.com
Server: 192.168.3.1
Address: 192.168.3.1#53
Non-authoritative answer:
Name: changelog.com
Address: 137.66.16.250
Nabeel S (Feb 06 2026 at 05:36):It started working again for me finally. But my browser was just spinning for a good 30 minutes :shrug:
Nabeel S (Feb 06 2026 at 05:36):Other sites were still working fine.
Brett Cannon (Feb 06 2026 at 22:21):@Nabeel S are you using a VPN by any chance? I had to turn off Mullvad in order to get the site to load.
Nabeel S (Feb 07 2026 at 03:36):I was on a VPN! I wonder if @Gerhard is experimenting with some anti-abuse algorithms that VPN users are getting caught in :slight_smile:
Gerhard (Feb 07 2026 at 07:36):Not experimenting with any anti-abuse, but issues limited to a single region is something that we have been working through: https://community.fly.io/t/response-body-timing-out-in-iad-ewr-all-good-in-13-other-regions/26727
There is more context here in case you want to try alternative curl commands and help report these isolated incidents that we are still not at the bottom of: https://github.com/thechangelog/changelog.com/issues/553
FWIW: https://status.changelog.com/
Dragan Milic (Feb 09 2026 at 20:48):During the Github outage today (don't know if this is just a coincidence), website wasn't serving any content. Even with curl:
% curl -v https://changelog.com/
* Host changelog.com:443 was resolved.
* IPv6: 2a09:8280:1::bf:736b:0
* IPv4: 137.66.16.250
* Trying 137.66.16.250:443...
* Connected to changelog.com (137.66.16.250) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: CN=changelog.com
* start date: Dec 31 16:52:47 2025 GMT
* expire date: Mar 31 16:52:46 2026 GMT
* subjectAltName: host "changelog.com" matched cert's "changelog.com"
* issuer: C=US; O=Let's Encrypt; CN=E8
* SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://changelog.com/
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: changelog.com]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> GET / HTTP/2
> Host: changelog.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/2 200
< cache-control: no-store, must-revalidate
< content-security-policy: base-uri 'self'; frame-ancestors 'self';
< content-type: text/html; charset=utf-8
< date: Mon, 09 Feb 2026 16:33:57 GMT
< fly-request-id: 01KH1M45MCHPSJG47N2NJAWFK2-fra
< referrer-policy: strict-origin-when-cross-origin
< server: Fly/cacd25bc (2026-02-09)
< surrogate-control: max-age=60, stale-while-revalidate=60, stale-if-error=604800
< surrogate-key: pages
< x-content-type-options: nosniff
< x-permitted-cross-domain-policies: none
< vary: Accept-Encoding
< x-varnish: 9374661 12519472
< age: 92
< via: 2 fly.io, 2 fly.io, 1.1 2873241a63e328 (Varnish/7.7), 2 fly.io
< accept-ranges: bytes
< x-request-id: 01KH1M45MCHPSJG47N2NJAWFK2-fra
< cache-status: region=fra; origin=app(localhost:5000),changelog-2025-05-05.fly.dev; ttl=-32.604; grace=86400.000; keep=604800.000; storage=storage.memory; hit; stale; hits=1
< content-length: 49427
<
* Recv failure: Operation timed out
* LibreSSL SSL_read: LibreSSL/3.3.6: error:02FFF03C:system library:func(4095):Operation timed out, errno 60
* Failed receiving HTTP2 data: 56(Failure when receiving data from the peer)
* Connection #0 to host changelog.com left intact
curl: (56) Recv failure: Operation timed out
That's a coincidence, since we are not tied to GitHub or Azure in any way.
In your curl response - thank you for sharing it - the response headers are served, but not the body. We have narrowed it down to a Fly.io Proxy HTTP/2 issue specifically. All the context is centralised here: https://github.com/thechangelog/changelog.com/issues/553
Gerhard (Feb 11 2026 at 11:47):FYI https://github.com/thechangelog/changelog.com/issues/553#issuecomment-3883928477
Dragan Milic (Feb 11 2026 at 12:02):Awesome, thank you!
Sometimes loading time of the web page was a tad delayed - didn't do any measurements, so can't give you any numbers, but atm loading times of changelog.com are better (could be biased because this is just how it 'feels').
Last updated: Feb 17 2026 at 17:33 UTC