Skip to content

Official documentation can't open #5511

Open
Open
Official documentation can't open#5511
Labels
needs investigation

Description

@sourav-18
sourav-18
opened on Jun 11, 2026

Official documentation can't open
https://socket.io/

Activity

  1. sourav-18
    added
    to triageWaiting to be triaged by a member of the team
    on Jun 11, 2026

  2. darrachequesne commented on Jun 11, 2026

    @darrachequesne
    darrachequesne
    on Jun 11, 2026
    Member

    Hi! Is it up again for you?

    Weirdly, Uptime robot did not detect any downtime:

    Image

    And there seems to be no incident on Vercel: https://www.vercel-status.com/

  3. darrachequesne
    added
    needs investigation
    and removed
    to triageWaiting to be triaged by a member of the team
    on Jun 11, 2026

  4. sourav-18 commented on Jun 11, 2026

    @sourav-18
    sourav-18
    on Jun 11, 2026
    Author
    Screencast.from.2026-06-11.13-31-49.webm

  5. darrachequesne commented on Jun 16, 2026

    @darrachequesne
    darrachequesne
    on Jun 16, 2026
    Member

    Still not solved? Where are you from? Could you please provide an IP address that fails to load the website?

    I think we'll have to escalate to the Vercel support...

  6. Sakibdevlekar commented on Jun 17, 2026

    @Sakibdevlekar
    Sakibdevlekar
    on Jun 17, 2026

    Root Cause Analysis

    Thank you @darrachequesne for the previous investigation. I've traced the issue further and identified that the problem is in a separate repository, not the main socket.io repo.

    Key Finding

    The actual source of the documentation site: socketio/socket.io-website
    Not: socketio/socket.io (main repo)

    📸 Evidence

    Error Screenshot from https://socket.io:
    Image

    This is a Docusaurus 2 configuration/deployment error, not a Socket.io library issue.

    🔍 Technical Analysis

    Repository Structure:

    • socketio/socket.io = Node.js library & source code ❌ (Wrong repo for docs issue)
    • socketio/socket.io-website = Docusaurus 2 website (Built at https://socket.io) ✅ (Correct repo)

    File Verified:

    • docusaurus.config.js exists in socketio/socket.io-website
    • baseUrl: "/" is correctly configured for root domain
    • Issue is likely: Build failure, deployment error, or runtime error

    ✅ Recommendation: Close This Issue

    Since this is a documentation site issue, not a Socket.io library issue:

    Suggested Action:

    Reason:

    • Documentation site issues ≠ Library code issues
    • Different repositories, different maintainers
    • Root cause is in website build/deployment infrastructure, not library code
    • Keeps Socket.io repo focused on the library itself

    Related Issue: 📌 socketio/socket.io-website#539

    📚 References

    Next Step: Tracking detailed investigation in socketio/socket.io-website#539 repository.

    Thank you for maintaining Socket.IO! 🙏

  7. sourav-18 commented on Jun 17, 2026

    @sourav-18
    sourav-18
    on Jun 17, 2026
    Author

    Hi @darrachequesne

    I'm located in West Bengal, India.

  8. darrachequesne commented on Jun 17, 2026

    @darrachequesne
    darrachequesne
    on Jun 17, 2026
    Member

    Update: it might be a DNS issue, which could explain the location-specific failures.

    Does the fallback domain (https://socket-io-website.vercel.app/) work?

  9. kishanranaghosh commented on Jun 17, 2026

    @kishanranaghosh
    kishanranaghosh
    on Jun 17, 2026

    I'm also located in West Bengal, India .. I'll share exact location details ... this is my current ip 223.181.55.101 ...and this is my exact location lat, long -> 25.017147, 88.154572 ....socket.io is not reachable from here only I tried to ping from a vps in located in Mumbai, India its works fine from that but not from west bengal

  10. Sakibdevlekar commented on Jun 18, 2026

    @Sakibdevlekar
    Sakibdevlekar
    on Jun 18, 2026

    Update: it might be a DNS issue, which could explain the location-specific failures.

    Does the fallback domain (https://socket-io-website.vercel.app/) work?

    Yes, it works!

    The Vercel domain loads fine: https://socket-io-website.vercel.app/

    But https://socket.io/ still doesn't load from my location (Pune, India).

  11. kishanranaghosh commented on Jun 18, 2026

    @kishanranaghosh
    kishanranaghosh
    on Jun 18, 2026

    https://socket-io-website.vercel.app/ ...yes vercel domain is working fine....I think some proxy issue happened

  12. darrachequesne commented on Jun 18, 2026

    @darrachequesne
    darrachequesne
    on Jun 18, 2026
    Member

    yes vercel domain is working fine

    OK, thanks.

    The Vercel support asks to run the following script:

    curl -s https://raw.githubusercontent.com/vercel-support/vercel-connect-debug/main/vercel-debug.sh | bash | tee vercel-debug.txt

    Or on Windows:

    Invoke-RestMethod -Uri https://raw.githubusercontent.com/vercel-support/vercel-connect-debug/main/vercel-debug.ps1 | Invoke-Expression | tee vercel-debug.txt

    Could you please provide the vercel-debug.txt output so we can forward it to the support?

  13. kishanranaghosh commented on Jun 18, 2026

    @kishanranaghosh
    kishanranaghosh
    on Jun 18, 2026

    this is the response ->

    krg@krgs-Mac-mini ~ % curl -s https://raw.githubusercontent.com/vercel-support/vercel-connect-debug/main/vercel-debug.sh | bash | tee vercel-debug.txt
    Domain to test (e.g. example.com):
    socket.io
    ┌───────────────────────────────────────
    ├─────── Fetching IP Addresses
    │
    │ socket.io IP range: 76.76.21.21, 76.76.21.9, 76.76.21.22, 76.76.21.241, 76.76.21.164, 76.76.21.142, 76.76.21.61, 76.76.21.93, 76.76.21.123, 76.76.21.98, 76.223.126.88, 66.33.60.33, 66.33.60.65, 66.33.60.129, 66.33.60.193, 66.33.60.34, 66.33.60.66, 66.33.60.130, 66.33.60.194, 66.33.60.35, 66.33.60.67
    └───────────────────────────────────────

    ┌───────────────────────────────────────
    ├─────── STARTING
    │
    │ Domain to test: socket.io
    │ Timestamp (UTC): Thu Jun 18 13:25:16 UTC 2026
    │ Timestamp (Local): Thu Jun 18 18:55:16 IST 2026
    └───────────────────────────────────────

    ┌───────────────────────────────────────
    ├─────── IP Information

    {
    "ip": "223.181.48.165",
    "city": "Kolkata",
    "region": "West Bengal",
    "country": "IN",
    "loc": "22.5626,88.3630",
    "org": "AS24560 Bharti Airtel Ltd., Telemedia Services",
    "postal": "700001",
    "timezone": "Asia/Kolkata",
    "readme": "https://ipinfo.io/missingauth"
    }
    └───────────────────────────────────────

    ┌───────────────────────────────────────
    ├─────── Testing 76.76.21.21
    Checking headers via 76.76.21.21

    • Connecting to hostname: 76.76.21.21
    • Trying 76.76.21.21:443...
    • Connected to 76.76.21.21 (76.76.21.21) port 443
    • ALPN: curl offers h2,http/1.1
    • (304) (OUT), TLS handshake, Client hello (1):
      } [314 bytes data]
    • (304) (IN), TLS handshake, Server hello (2):
      { [122 bytes data]
    • (304) (IN), TLS handshake, Unknown (8):
      { [19 bytes data]
    • (304) (IN), TLS handshake, Certificate (11):
      { [2570 bytes data]
    • (304) (IN), TLS handshake, CERT verify (15):
      { [264 bytes data]
    • (304) (IN), TLS handshake, Finished (20):
      { [36 bytes data]
    • (304) (OUT), TLS handshake, Finished (20):
      } [36 bytes data]
    • SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
    • ALPN: server accepted h2
    • Server certificate:
    • subject: CN=socket.io
    • start date: May 23 07:12:37 2026 GMT
    • expire date: Aug 21 07:12:36 2026 GMT
    • issuer: C=US; O=Let's Encrypt; CN=R13
    • SSL certificate verify ok.
    • using HTTP/2
    • [HTTP/2] [1] OPENED stream for https://socket.io/
    • [HTTP/2] [1] [:method: GET]
    • [HTTP/2] [1] [:scheme: https]
    • [HTTP/2] [1] [:authority: socket.io]
    • [HTTP/2] [1] [:path: /]
    • [HTTP/2] [1] [user-agent: curl/8.7.1]
    • [HTTP/2] [1] [accept: /]

    GET / HTTP/2
    Host: socket.io
    User-Agent: curl/8.7.1
    Accept: /

    • Request completely sent off
      < HTTP/2 200
      < accept-ranges: bytes
      < access-control-allow-origin: *
      < age: 96
      < cache-control: public, max-age=0, must-revalidate
      < content-disposition: inline
      < content-type: text/html; charset=utf-8
      < date: Thu, 18 Jun 2026 13:25:17 GMT
      < etag: "69535912fca89b1312fec3c26cbbaf82"
      < last-modified: Thu, 18 Jun 2026 13:23:41 GMT
      < server: Vercel
      < strict-transport-security: max-age=63072000
      < x-vercel-cache: HIT
      < x-vercel-id: bom1::8w48n-1781789117418-3ed8206c9588
      < content-length: 61501
      <
      { [3163 bytes data]
    • Connection #0 to host 76.76.21.21 left intact

    Checking ping to 76.76.21.21
    PING 76.76.21.21 (76.76.21.21): 56 data bytes
    64 bytes from 76.76.21.21: icmp_seq=0 ttl=249 time=25.313 ms
    64 bytes from 76.76.21.21: icmp_seq=1 ttl=249 time=25.182 ms
    64 bytes from 76.76.21.21: icmp_seq=2 ttl=249 time=22.222 ms
    64 bytes from 76.76.21.21: icmp_seq=3 ttl=249 time=23.950 ms

    --- 76.76.21.21 ping statistics ---
    4 packets transmitted, 4 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 22.222/24.167/25.313/1.242 ms
    └───────────────────────────────────────

    ┌───────────────────────────────────────
    ├─────── Testing 76.76.21.9
    Checking headers via 76.76.21.9

    • Connecting to hostname: 76.76.21.9
    • Trying 76.76.21.9:443...
    • Connected to 76.76.21.9 (76.76.21.9) port 443
    • ALPN: curl offers h2,http/1.1
    • (304) (OUT), TLS handshake, Client hello (1):
      } [314 bytes data]
    • (304) (IN), TLS handshake, Server hello (2):
      { [122 bytes data]
    • (304) (IN), TLS handshake, Unknown (8):
      { [19 bytes data]
    • (304) (IN), TLS handshake, Certificate (11):
      { [2570 bytes data]
    • (304) (IN), TLS handshake, CERT verify (15):
      { [264 bytes data]
    • (304) (IN), TLS handshake, Finished (20):
      { [36 bytes data]
    • (304) (OUT), TLS handshake, Finished (20):
      } [36 bytes data]
    • SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
    • ALPN: server accepted h2
    • Server certificate:
    • subject: CN=socket.io
    • start date: May 23 07:12:37 2026 GMT
    • expire date: Aug 21 07:12:36 2026 GMT
    • issuer: C=US; O=Let's Encrypt; CN=R13
    • SSL certificate verify ok.
    • using HTTP/2
    • [HTTP/2] [1] OPENED stream for https://socket.io/
    • [HTTP/2] [1] [:method: GET]
    • [HTTP/2] [1] [:scheme: https]
    • [HTTP/2] [1] [:authority: socket.io]
    • [HTTP/2] [1] [:path: /]
    • [HTTP/2] [1] [user-agent: curl/8.7.1]
    • [HTTP/2] [1] [accept: /]

    GET / HTTP/2
    Host: socket.io
    User-Agent: curl/8.7.1
    Accept: /

    • Request completely sent off
      < HTTP/2 200
      < accept-ranges: bytes
      < access-control-allow-origin: *
      < age: 99
      < cache-control: public, max-age=0, must-revalidate
      < content-disposition: inline
      < content-type: text/html; charset=utf-8
      < date: Thu, 18 Jun 2026 13:25:20 GMT
      < etag: "69535912fca89b1312fec3c26cbbaf82"
      < last-modified: Thu, 18 Jun 2026 13:23:41 GMT
      < server: Vercel
      < strict-transport-security: max-age=63072000
      < x-vercel-cache: HIT
      < x-vercel-id: bom1::ntdxj-1781789120758-772daffcc077
      < content-length: 61501
      <
      { [3163 bytes data]
    • Connection #0 to host 76.76.21.9 left intact

    Checking ping to 76.76.21.9
    PING 76.76.21.9 (76.76.21.9): 56 data bytes
    64 bytes from 76.76.21.9: icmp_seq=0 ttl=249 time=23.951 ms
    64 bytes from 76.76.21.9: icmp_seq=1 ttl=249 time=27.286 ms

  14. darrachequesne commented on Jun 18, 2026

    @darrachequesne
    darrachequesne
    on Jun 18, 2026
    Member

    Thanks! I'm awaiting response from the support, I'll keep you updated.

  15. kishanranaghosh commented on Jun 18, 2026

    @kishanranaghosh
    kishanranaghosh
    on Jun 18, 2026

    ok....Thank you so much

  16. kishanranaghosh commented on Jun 25, 2026

    @kishanranaghosh
    kishanranaghosh
    on Jun 25, 2026

    sir is anything get from vercel support??

  17. darrachequesne commented on Jun 26, 2026

    @darrachequesne
    darrachequesne
    on Jun 26, 2026
    Member

    Here is the response from Vercel support:

    Image

    Screenshot:

    Image

    Given the number of reports, I don't think this could be caused by a browser plugin though...

  18. sourav-18 commented on Jul 1, 2026

    @sourav-18
    sourav-18
    on Jul 1, 2026
    Author

    @darrachequesne
    Yes this uri work fine https://socket-io-website.vercel.app/
    but this still not work https://socket.io/

  19. kishanranaghosh commented on Jul 2, 2026

    @kishanranaghosh
    kishanranaghosh
    on Jul 2, 2026

    this is the curl response and socket.io works from Mumbai I tried from a VPS but not work from west bengal....

    krg@krgs-Mac-mini ~ % curl -s https://raw.githubusercontent.com/vercel-support/vercel-connect-debug/main/vercel-debug.sh | bash | tee vercel-debug.txt
    krg@krgs-Mac-mini ~ % curl -s https://raw.githubusercontent.com/vercel-support/vercel-connect-debug/main/vercel-debug.sh | bash | tee vercel-debug.txt
    Domain to test (e.g. example.com):
    socket.io
    ┌───────────────────────────────────────
    ├─────── Fetching IP Addresses
    │
    │ socket.io IP range: 76.76.21.21, 76.76.21.9, 76.76.21.22, 76.76.21.241, 76.76.21.164, 76.76.21.142, 76.76.21.61, 76.76.21.93, 76.76.21.123, 76.76.21.98, 76.223.126.88, 66.33.60.33, 66.33.60.65, 66.33.60.129, 66.33.60.193, 66.33.60.34, 66.33.60.66, 66.33.60.130, 66.33.60.194, 66.33.60.35, 66.33.60.67
    └───────────────────────────────────────

    ┌───────────────────────────────────────
    ├─────── STARTING
    │
    │ Domain to test: socket.io
    │ Timestamp (UTC): Thu Jul 2 15:58:00 UTC 2026
    │ Timestamp (Local): Thu Jul 2 21:28:00 IST 2026
    └───────────────────────────────────────

    ┌───────────────────────────────────────
    ├─────── IP Information

    {
    "ip": "223.181.54.36",
    "city": "Kolkata",
    "region": "West Bengal",
    "country": "IN",
    "loc": "22.5626,88.3630",
    "org": "AS24560 Bharti Airtel Ltd., Telemedia Services",
    "postal": "700001",
    "timezone": "Asia/Kolkata",
    "readme": "https://ipinfo.io/missingauth"
    }
    └───────────────────────────────────────

    ┌───────────────────────────────────────
    ├─────── Testing 76.76.21.21
    Checking headers via 76.76.21.21

    • Connecting to hostname: 76.76.21.21
    • Trying 76.76.21.21:443...
    • Connected to 76.76.21.21 (76.76.21.21) port 443
    • ALPN: curl offers h2,http/1.1
    • (304) (OUT), TLS handshake, Client hello (1):
      } [314 bytes data]
    • (304) (IN), TLS handshake, Server hello (2):
      { [122 bytes data]
    • (304) (IN), TLS handshake, Unknown (8):
      { [19 bytes data]
    • (304) (IN), TLS handshake, Certificate (11):
      { [2570 bytes data]
    • (304) (IN), TLS handshake, CERT verify (15):
      { [264 bytes data]
    • (304) (IN), TLS handshake, Finished (20):
      { [36 bytes data]
    • (304) (OUT), TLS handshake, Finished (20):
      } [36 bytes data]
    • SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
    • ALPN: server accepted h2
    • Server certificate:
    • subject: CN=socket.io
    • start date: May 23 07:12:37 2026 GMT
    • expire date: Aug 21 07:12:36 2026 GMT
    • issuer: C=US; O=Let's Encrypt; CN=R13
    • SSL certificate verify ok.
    • using HTTP/2
    • [HTTP/2] [1] OPENED stream for https://socket.io/
    • [HTTP/2] [1] [:method: GET]
    • [HTTP/2] [1] [:scheme: https]
    • [HTTP/2] [1] [:authority: socket.io]
    • [HTTP/2] [1] [:path: /]
    • [HTTP/2] [1] [user-agent: curl/8.7.1]
    • [HTTP/2] [1] [accept: /]

    GET / HTTP/2
    Host: socket.io
    User-Agent: curl/8.7.1
    Accept: /

    • Request completely sent off
      < HTTP/2 200
      < accept-ranges: bytes
      < access-control-allow-origin: *
      < age: 38759
      < cache-control: public, max-age=0, must-revalidate
      < content-disposition: inline
      < content-type: text/html; charset=utf-8
      < date: Thu, 02 Jul 2026 15:58:01 GMT
      < etag: "6db3e5ed92d159b3da02b36527dffedc"
      < last-modified: Thu, 02 Jul 2026 05:12:02 GMT
      < server: Vercel
      < strict-transport-security: max-age=63072000
      < x-vercel-cache: HIT
      < x-vercel-id: bom1::wxjcf-1783007881347-1014f895079d
      < content-length: 62435
      <
      { [3160 bytes data]
    • Connection #0 to host 76.76.21.21 left intact

    Checking ping to 76.76.21.21
    PING 76.76.21.21 (76.76.21.21): 56 data bytes
    64 bytes from 76.76.21.21: icmp_seq=0 ttl=249 time=25.929 ms
    64 bytes from 76.76.21.21: icmp_seq=1 ttl=249 time=30.093 ms
    64 bytes from 76.76.21.21: icmp_seq=2 ttl=249 time=28.972 ms
    64 bytes from 76.76.21.21: icmp_seq=3 ttl=249 time=30.778 ms

    --- 76.76.21.21 ping statistics ---
    4 packets transmitted, 4 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 25.929/28.943/30.778/1.856 ms
    └───────────────────────────────────────

    ┌───────────────────────────────────────
    ├─────── Testing 76.76.21.9
    Checking headers via 76.76.21.9

    • Connecting to hostname: 76.76.21.9
    • Trying 76.76.21.9:443...
    • Connected to 76.76.21.9 (76.76.21.9) port 443
    • ALPN: curl offers h2,http/1.1
    • (304) (OUT), TLS handshake, Client hello (1):
      } [314 bytes data]
    • (304) (IN), TLS handshake, Server hello (2):
      { [122 bytes data]
    • (304) (IN), TLS handshake, Unknown (8):
      { [19 bytes data]
    • (304) (IN), TLS handshake, Certificate (11):
      { [2570 bytes data]
    • (304) (IN), TLS handshake, CERT verify (15):
      { [264 bytes data]
    • (304) (IN), TLS handshake, Finished (20):
      { [36 bytes data]
    • (304) (OUT), TLS handshake, Finished (20):
      } [36 bytes data]
    • SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
    • ALPN: server accepted h2
    • Server certificate:
    • subject: CN=socket.io
    • start date: May 23 07:12:37 2026 GMT
    • expire date: Aug 21 07:12:36 2026 GMT
    • issuer: C=US; O=Let's Encrypt; CN=R13
    • SSL certificate verify ok.
    • using HTTP/2
    • [HTTP/2] [1] OPENED stream for https://socket.io/
    • [HTTP/2] [1] [:method: GET]
    • [HTTP/2] [1] [:scheme: https]
    • [HTTP/2] [1] [:authority: socket.io]
    • [HTTP/2] [1] [:path: /]
    • [HTTP/2] [1] [user-agent: curl/8.7.1]
    • [HTTP/2] [1] [accept: /]

    GET / HTTP/2
    Host: socket.io
    User-Agent: curl/8.7.1
    Accept: /

    • Request completely sent off
      < HTTP/2 200
      < accept-ranges: bytes
      < access-control-allow-origin: *
      < age: 38762
      < cache-control: public, max-age=0, must-revalidate
      < content-disposition: inline
      < content-type: text/html; charset=utf-8
      < date: Thu, 02 Jul 2026 15:58:04 GMT
      < etag: "6db3e5ed92d159b3da02b36527dffedc"
      < last-modified: Thu, 02 Jul 2026 05:12:02 GMT
      < server: Vercel
      < strict-transport-security: max-age=63072000
      < x-vercel-cache: HIT
      < x-vercel-id: bom1::2vs2f-1783007884669-830531404ffa
      < content-length: 62435
      <
      { [3160 bytes data]
    • Connection #0 to host 76.76.21.9 left intact

    Checking ping to 76.76.21.9
    PING 76.76.21.9 (76.76.21.9): 56 data bytes
    64 bytes from 76.76.21.9: icmp_seq=0 ttl=249 time=25.694 ms
    64 bytes from 76.76.21.9: icmp_seq=1 ttl=249 time=27.426 ms
    64 bytes from 76.76.21.9: icmp_seq=2 ttl=249 time=25.802 ms
    64 bytes from 76.76.21.9: icmp_seq=3 ttl=249 time=21.233 ms

    --- 76.76.21.9 ping statistics ---
    4 packets transmitted, 4 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 21.233/25.039/27.426/2.302 ms
    └───────────────────────────────────────

    ┌───────────────────────────────────────
    ├─────── Testing 76.76.21.22
    Checking headers via 76.76.21.22

    • Connecting to hostname: 76.76.21.22
    • Trying 76.76.21.22:443...
    • Connected to 76.76.21.22 (76.76.21.22) port 443
    • ALPN: curl offers h2,http/1.1
    • (304) (OUT), TLS handshake, Client hello (1):
      } [314 bytes data]
    • (304) (IN), TLS handshake, Server hello (2):
      { [122 bytes data]
    • (304) (IN), TLS handshake, Unknown (8):
      { [19 bytes data]
    • (304) (IN), TLS handshake, Certificate (11):
      { [2570 bytes data]
    • (304) (IN), TLS handshake, CERT verify (15):
      { [264 bytes data]
    • (304) (IN), TLS handshake, Finished (20):
      { [36 bytes data]
    • (304) (OUT), TLS handshake, Finished (20):
      } [36 bytes data]
    • SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
    • ALPN: server accepted h2
    • Server certificate:
    • subject: CN=socket.io
    • start date: May 23 07:12:37 2026 GMT
    • expire date: Aug 21 07:12:36 2026 GMT
    • issuer: C=US; O=Let's Encrypt; CN=R13
    • SSL certificate verify ok.
    • using HTTP/2
    • [HTTP/2] [1] OPENED stream for https://socket.io/
    • [HTTP/2] [1] [:method: GET]
    • [HTTP/2] [1] [:scheme: https]
    • [HTTP/2] [1] [:authority: socket.io]
    • [HTTP/2] [1] [:path: /]
    • [HTTP/2] [1] [user-agent: curl/8.7.1]
    • [HTTP/2] [1] [accept: /]

    GET / HTTP/2
    Host: socket.io
    User-Agent: curl/8.7.1
    Accept: /

    • Request completely sent off
      < HTTP/2 200
      < accept-ranges: bytes
      < access-control-allow-origin: *
      < age: 38765
      < cache-control: public, max-age=0, must-revalidate
      < content-disposition: inline
      < content-type: text/html; charset=utf-8
      < date: Thu, 02 Jul 2026 15:58:07 GMT
      < etag: "6db3e5ed92d159b3da02b36527dffedc"
      < last-modified: Thu, 02 Jul 2026 05:12:02 GMT
      < server: Vercel
      < strict-transport-security: max-age=63072000
      < x-vercel-cache: HIT
      < x-vercel-id: bom1::45qrn-1783007887940-f29cf544bcb9
      < content-length: 62435
      <
      { [3160 bytes data]
    • Connection #0 to host 76.76.21.22 left intact

    Checking ping to 76.76.21.22
    PING 76.76.21.22 (76.76.21.22): 56 data bytes
    64 bytes from 76.76.21.22: icmp_seq=0 ttl=249 time=22.999 ms
    64 bytes from 76.76.21.22: icmp_seq=1 ttl=249 time=25.859 ms
    64 bytes from 76.76.21.22: icmp_seq=2 ttl=249 time=24.889 ms
    64 bytes from 76.76.21.22: icmp_seq=3 ttl=249 time=28.901 ms

    --- 76.76.21.22 ping statistics ---
    4 packets transmitted, 4 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 22.999/25.662/28.901/2.134 ms
    └───────────────────────────────────────

    ┌───────────────────────────────────────
    ├─────── Testing 76.76.21.241
    Checking headers via 76.76.21.241

    • Connecting to hostname: 76.76.21.241
    • Trying 76.76.21.241:443...
    • Connected to 76.76.21.241 (76.76.21.241) port 443
    • ALPN: curl offers h2,http/1.1
    • (304) (OUT), TLS handshake, Client hello (1):
      } [314 bytes data]
    • (304) (IN), TLS handshake, Server hello (2):
      { [122 bytes data]
    • (304) (IN), TLS handshake, Unknown (8):
      { [19 bytes data]
    • (304) (IN), TLS handshake, Certificate (11):
      { [2570 bytes data]
    • (304) (IN), TLS handshake, CERT verify (15):
      { [264 bytes data]
    • (304) (IN), TLS handshake, Finished (20):
      { [36 bytes data]
    • (304) (OUT), TLS handshake, Finished (20):
      } [36 bytes data]
    • SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
    • ALPN: server accepted h2
    • Server certificate:
    • subject: CN=socket.io
    • start date: May 23 07:12:37 2026 GMT
    • expire date: Aug 21 07:12:36 2026 GMT
    • issuer: C=US; O=Let's Encrypt; CN=R13
    • SSL certificate verify ok.
    • using HTTP/2
    • [HTTP/2] [1] OPENED stream for https://socket.io/
    • [HTTP/2] [1] [:method: GET]
    • [HTTP/2] [1] [:scheme: https]
    • [HTTP/2] [1] [:authority: socket.io]
    • [HTTP/2] [1] [:path: /]
    • [HTTP/2] [1] [user-agent: curl/8.7.1]
    • [HTTP/2] [1] [accept: /]

    GET / HTTP/2
    Host: socket.io
    User-Agent: curl/8.7.1
    Accept: /

    • Request completely sent off
      < HTTP/2 200
      < accept-ranges: bytes
      < access-control-allow-origin: *
      < age: 38769
      < cache-control: public, max-age=0, must-revalidate
      < content-disposition: inline
      < content-type: text/html; charset=utf-8
      < date: Thu, 02 Jul 2026 15:58:11 GMT
      < etag: "6db3e5ed92d159b3da02b36527dffedc"
      < last-modified: Thu, 02 Jul 2026 05:12:02 GMT
      < server: Vercel
      < strict-transport-security: max-age=63072000
      < x-vercel-cache: HIT
      < x-vercel-id: bom1::fzx94-1783007891226-7d58381a2f45
      < content-length: 62435
      <
      { [3160 bytes data]
    • Connection #0 to host 76.76.21.241 left intact

    Checking ping to 76.76.21.241
    PING 76.76.21.241 (76.76.21.241): 56 data bytes
    64 bytes from 76.76.21.241: icmp_seq=0 ttl=249 time=24.010 ms
    64 bytes from 76.76.21.241: icmp_seq=1 ttl=249 time=21.794 ms
    ^C
    krg@krgs-Mac-mini ~ %

  20. AdnanAftab1 commented on Jul 15, 2026

    @AdnanAftab1
    AdnanAftab1
    on Jul 15, 2026

    Hi @darrachequesne

    I'm located in West Bengal, India.

    I am from the exact same place and its not working in here....Precisely a DNS issue

  21. kaspra commented on Aug 25, 2026

    @kaspra
    kaspra
    on Aug 25, 2026

    We’re from Chennai, India, and we’re also facing the same issue. The official website, https://socket.io/, isn’t opening.

  22. darrachequesne
    pinned this issue on Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs investigation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions