I can confirm this, the same thing is happening for api.mojang.com:
szymon@szymon-Laptop:~$ curl -v https://api.mojang.com/users/profiles/minecraft/tirex * Trying 13.107.213.44:443... * TCP_NODELAY set * Trying 2620:1ec:bdf::44:443... * TCP_NODELAY set * Immediate connect fail for 2620:1ec:bdf::44: Network is unreachable * Trying 2620:1ec:46::44:443... * TCP_NODELAY set * Immediate connect fail for 2620:1ec:46::44: Network is unreachable * Connected to api.mojang.com (13.107.213.44) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=api.mojang.com * start date: Nov 2 00:00:00 2023 GMT * expire date: May 2 23:59:59 2024 GMT * subjectAltName: host "api.mojang.com" matched cert's "api.mojang.com" * issuer: C=US; O=DigiCert, Inc.; CN=GeoTrust Global TLS RSA4096 SHA256 2022 CA1 * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x55bb0751f320) > GET /users/profiles/minecraft/tirex HTTP/2 > Host: api.mojang.com > user-agent: curl/7.68.0 > accept: */* > * Connection state changed (MAX_CONCURRENT_STREAMS == 128)! < HTTP/2 429 < date: Fri, 12 Jan 2024 11:18:32 GMT < content-type: text/html < content-length: 1261 < cache-control: no-store < x-azure-ref: 20240112T111832Z-r01er4yt1t40r4kg0rxrnnhrfc0000000d400000000037bc < x-cache: PRIVATE_NOSTORE < <!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'> <html xmlns='http://www.w3.org/1999/xhtml'><head> <meta content='text/html; charset=utf-8' http-equiv='content-type' /> <style type='text/css'> body { font-family: Arial; margin-left: 40px; } img { border: 0 none; } #content { margin-left: auto; margin-right: auto } #message h2 { font-size: 20px; font-weight: normal; color: #000000; margin: 34px 0px 0px 0px } #message p { font-size: 13px; color: #000000; margin: 7px 0px 0px0px } #errorref { font-size: 11px; color: #737373; margin-top: 41px } </style> <title>Service unavailable</title> </head><body> <div id='content'> <div id='message'> <h2>The request is blocked.</h2> </div> <div id='errorref'> <span>20240112T111832Z-qha6wpw8h52wz6sr6nac337spn0000000xs00000000066hb </span> </div> </div> </body> </html> * Connection #0 to host api.mojang.com left intact
This proved most problematic in the first few days, but recently I have not noticed a problem
What is the ETA for this issue?
tirex
I can confirm this, the same thing is happening for api.mojang.com: