Intermittent connection errors to data.alpaca.markets (started recently)

Alpaca Trading
1

Hello all,

I have been running into some issues recently regarding intermittent connection-level errors when hitting Alpaca market data endpoints. The code that I have been using has remain relatively unchanged for months and I have not run into this problem at all before recently (within last day or so I noticed it).

Examples)

  • Cannot connect to host data.alpaca.markets:443
  • Connection reset by peer
  • Occasional 502 gateway responses

I’ve noticed this on

  • /v2/stocks/quotes (SIP)
  • /v2/clock

Is anyone else running into these issues? or is it just me?
Has alpaca made any updates recently to their infrastructure that may be causing this?

Best,
Joseph

2

I have the same issue today. Their API status page shows green but clearly I have problem with connection.

3

@Joseph1234 @PatL The issue with “connection reset by peer” errors has been reported by several users. The Engineering Team is looking into it. It seems to be resolved now, but will monitor especially during market open tomorrow.

Apologies for any inconvenience.

4

Yes noticed it yesterday starting around 1pm EST

5

Hi. I was seeing the same thing yesterday afternoon/evening. It seemed to be fixed this morning, but I’m seeing the problem again now

6

Not sure if this is related but I started getting: Error 12030 calling WINHTTP_CALLBACK_STATUS_REQUEST_ERROR, ‘The connection with the server was terminated abnormally’. while trying to get latest stock prices…

7

same issue here started yesterday. Still having the same issue now. My algo is down due to this.

(‘Connection aborted.’, ConnectionResetError(104, ‘Connection reset by peer’)

8

same here, starting getting errors at 9:30 on EST

9

Same here, really annoying and status page shows green which is also annoying as we have to check forum to check the real status.

2 Likes
10

same here. last several days…

System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
—> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
—> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
— End of inner exception stack trace —
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
at System.Net.Security.SslStream.EnsureFullTlsFrameAsync[TIOAdapter](CancellationToken cancellationToken, Int32 estimatedSize)
at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder1.StateMachineBox1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Security.SslStream.ReceiveHandshakeFrameAsync[TIOAdapter](CancellationToken cancellationToken)
at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](Boolean receiveFirst, Byte reAuthenticationData, CancellationToken cancellationToken)
at System.Net.Http.ConnectHelper.EstablishSslConnectionAsync(SslClientAuthenticationOptions sslOptions, HttpRequestMessage request, Boolean async, Stream stream, CancellationToken cancellationToken)
— End of inner exception stack trace —

11

The Alpaca Engineering team identified the root cause of the “connection aborted. Connection reset error 104 connection reset by peer” errors as a bug in the ingress server code. A fix has been implemented as of around 12:00 EST today 2026-02-05.

If you are still receiving these errors please reply and include your IP address if possible.

Again apologies for this issue.

2 Likes
12

Thanks for the update!

13

What HOMER reported ^^ Is EXACTLY where my issue began.. it cleared up thankfully, I thought i was being Suspended for too many requests honestly ( i tweaked the wrong value and caught it later) .. but in addition to that ive also had news feed httpsconnectionpool….(port=443) errors.. similar to the ssl rejection with intraday requests AND snapshot requests. ITs a blessing to have access to this so im not complaining , just kind of happy to hear it wasnt from me being too agressive with my scanner

14

Same, I was so confused why I was getting those errors all of a sudden when my code had worked for months lol.

15

Seems like a different issue today, but data.alpaca.markets/v1beta1/options/ endpoints (at least) are broken again.

18

@jSp08238 you are correct there was a separate issue with the https://data.alpaca.markets/v1beta1/options/ endpoint on 2026-02-09. That can be found in the status updates here.

This was unrelated to the previous issue and stemmed from a problem fetching interest rate data. Interest rates are used in the calculation of Greeks. This calculation would fail due to no interest rate data and therefore would not return snapshot data.

Apologies for any inconvenience, this issue has been resolved.