anybody else having issues with hyperliquid now? Got an error message saying "error occured while fetching delgations data", i can see my position and balances within HL but Rabby cant pick it up
anybody else having issues with hyperliquid now? Got an error message saying "error occured while fetching delgations data", i can see my position and balances within HL but Rabby cant pick it up
same
same
Looking into it
Looking into it
userFills endpoint down
userFills endpoint down
Yeah, I think a lot of the user endpoints are down. I am getting a lot of 500s
Yeah, I think a lot of the user endpoints are down. I am getting a lot of 500s
Hey, is userNonFundingLedgerUpdates down? Getting 500
Hey, is userNonFundingLedgerUpdates down? Getting 500
Same, userFills is down
Same, userFills is down
Yup HTTP 500
Yup HTTP 500
Any admin here? Userfill API endpoint seems to be down. Getting HTTP 500 error code.
Any admin here? Userfill API endpoint seems to be down. Getting HTTP 500 error code.
^
^
came to find this out lol
came to find this out lol
is there any network update? its not working as usual
is there any network update? its not working as usual
Hi builders how are you? Im also getting a 500 while trying to query orderStatus... i'm using same code that is working on testnet... any trouble with info api on mainnet?
Hi builders how are you? Im also getting a 500 while trying to query orderStatus... i'm using same code that is working on testnet... any trouble with info api on mainnet?
Here's my request/response:
curl -i https://api.hyperliquid.xyz/info \
-H "Content-Type: application/json" \
--data-raw '{
"type": "orderStatus",
"user": "0xe8D71c0d50Adb583C65aca59b250d139428376E9",
"oid": 498701870414
}'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 4
Connection: keep-alive
Server: nginx/1.22.1
Date: Sun, 19 Jul 2026 13:16:48 GMT
access-control-expose-headers: *
access-control-allow-origin: *
vary: origin
vary: access-control-request-method
vary: access-control-request-headers
X-Cache: Error from cloudfront
Via: 1.1 d6d2c99e22fa470e01c3d422bed2160e.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: CMH68-P2
X-Amz-Cf-Id: 23wcXJc5XOaih6hY8IWEtL3OWa1qvwqHXsghGM6B3G5GiwzUxl1BEQ==
Here's my request/response:
curl -i https://api.hyperliquid.xyz/info \
-H "Content-Type: application/json" \
--data-raw '{
"type": "orderStatus",
"user": "0xe8D71c0d50Adb583C65aca59b250d139428376E9",
"oid": 498701870414
}'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 4
Connection: keep-alive
Server: nginx/1.22.1
Date: Sun, 19 Jul 2026 13:16:48 GMT
access-control-expose-headers: *
access-control-allow-origin: *
vary: origin
vary: access-control-request-method
vary: access-control-request-headers
X-Cache: Error from cloudfront
Via: 1.1 d6d2c99e22fa470e01c3d422bed2160e.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: CMH68-P2
X-Amz-Cf-Id: 23wcXJc5XOaih6hY8IWEtL3OWa1qvwqHXsghGM6B3G5GiwzUxl1BEQ==
probably public apis down
probably public apis down
public exchange api is working coz i'm able to submit spot trades but cant query status properly... <a:HaroldSpasm:1027397967226875954>
public exchange api is working coz i'm able to submit spot trades but cant query status properly... <a:HaroldSpasm:1027397967226875954>
Looks like it’s back
Looks like it’s back
seems its working now!!
seems its working now!!
same!
same!
1. what I mean is **hyperliquid** is keeping 500 http response today.
2. This is a serious issue that significantly affects my trading and maintenance operations. Please stay focused and do not derail the discussion with irrelevant topics such as Discord or other unnecessary commentary.
1. what I mean is **hyperliquid** is keeping 500 http response today.
2. This is a serious issue that significantly affects my trading and maintenance operations. Please stay focused and do not derail the discussion with irrelevant topics such as Discord or other unnecessary commentary.
had same issue for just under an hour
had same issue for just under an hour
Yep, seems it was some kind of temporary issue... Cuz all is working properly now! 👍
Yep, seems it was some kind of temporary issue... Cuz all is working properly now! 👍