ERCOT API slow and 400s

[tbriggs-nee]

I have been having a lot of difficulty with the API today. Many requests fluctuate between returning 400 responses and taking ~60 seconds to return. Does anyone else have these issues?

I know its not me because the same request will return a 400 one moment and then work another which doesn't make sense to me.

example response:
400 Client Error: Bad Request for url: https://api.ercot.com/api/public-reports/np6-788-cd/lmp_node_zone_hub?sort=SCEDTimestamp&size=100&page=1&SCEDTimestampFrom=2025-09-17T11%3A15%3A30&SCEDTimestampTo=2025-09-19T12%3A15%3A30 Your request could not be processed. The request may be malformed or the URL does not exist..

This seems to come and go the last several days.

[ivanjgr]

Has the 400 error been fixed? I’m still experiencing the same issue with the API.

[and1-ALB]

Hi Everyone,

I am also experiencing this 400 error when passing parameters.
Is there any update on this ?

[alexderb]

Same problem on my side....

[mansimii]

Hi all, I am also experiencing the same issue. The API has been increasingly flaky for me over the past 4 days.

I am also experiencing this 400 error when passing parameters.

Seconding this. I get a 200 response without parameters but 400 when I pass any parameters.

[sungpark-trwd]

We have been still experiencing the same issue for the past few days.

[sscott-ercot]

We have the issue resolved (again). We are investigating the underlying cause.

[alexderb]

Not resolved on my side..I still have the same issue

[tbriggs-nee]

Thank you for the reply @sscott-ercot . Please let us know when you think this will be resolved. I have noticed it mostly starting on the 16th this week with a single occurrence for me on the 15th as well.

[JoseIChoriEPWM]

Same problem here, we need your support in this Issue, please!

Error requesting data, status code: 400, response: { "timestamp": "2025-09-18 09:09:52", "code": 400, "status": "BAD_REQUEST", "message": "Your request could not be processed. The request may be malformed or the URL does not exist." }

[sscott-ercot]

We identified an individual who was abusing the system and violating the terms of use. We have disabled this account and are contacting the individual.

[tbriggs-nee]

Hi @sscott-ercot I am still experiencing the issue - Really long response times and sometimes a rogue 400.

[sscott-ercot]

We are blocking the IP address.

[and1-ALB]

Hi @sscott-ercot , I am getting some data from public Ercot API but sometimes I get 500 error . Is there any limit on requests per minute ?

[d-smit]

@sscott-ercot still errors unfortunately. Some endpoints work e.g. np4-190-cd, however np4-190-cd gives ConnectionError: None.

[sscott-ercot]

Quick update. We are continuing to troubleshoot the issue. Additional details will be provided as they are known. There is a limit on the requests per minute. You can look at #100 for additional details.

[sscott-ercot]

We are continuing to investigate. We've implemented a temporary workaround. It may be slow while we capture a definitive solution.

[tbriggs-nee]

Thank you for the updates.

[d-smit]

Hi @sscott-ercot I am still getting ConnectionError: None, just confirming you can see on your side too.

[d-smit]

@sscott-ercot problem came from not setting the size attribute. This attribute is confusing as surely the start and end date dictate number of rows. Can you confirm the timezone of the API data -> every endpoint is America/Chicago?

[mansimii]

Hi @sscott-ercot , we have been experiencing Timeout issues (resolves on increasing the timeout) and 503 Server Errors.

Are there any new updates on the ongoing issues? :)

[sscott-ercot]

Thank you for the patience. We have identified a handful of items we would like to address. Unfortunately, the one with the biggest impact will require modifications to the backend. This is not something we can perform "on the fly" and are making plans to address these. As we go through the modifications, there will be an outage, although anticipated to be brief. We will provide an update when we get to this point.

We continue to watch the system and as we see issues, we will continue to restore the service as quickly as possible.

[mansimii]

Thanks for the prompt response @sscott-ercot :)

[c3-angelmr]

Hi @sscott-ercot, This affects all endpoints and account types, or does this just apply to certain endpoints/account types?

[sscott-ercot]

All endpoints will be impacted. When we plan this work, we will provide a date/time range.

[sscott-ercot]

We continue to work through the backend improvements. Several changes were implemented and it appears performance has stabilized over the last several days. We will continue to monitor it.

[tbriggs-nee]

Thanks for the continued updates @sscott-ercot