search

goodeggs / librato-node

A Node.js client for Librato (http://librato.com/)
MIT License
37 stars 26 forks source link

getting a lot of timed out errors #51

Closed vincentwoo closed 8 years ago

vincentwoo commented 8 years ago

{"level":"error","message":"librato error: { [Error: connect ETIMEDOUT 107.21.215.21:443]\n code: 'ETIMEDOUT',\n errno: 'ETIMEDOUT',\n syscall: 'connect',\n address: '107.21.215.21',\n port: 443 }","timestamp":"2016-08-31T23:00:19.623Z"}

Anyone else seeing this?

josephruscio commented 8 years ago

[Librato here] @mbeale does this correlate with the other reports you were investigating earlier today?

vincentwoo commented 8 years ago

yeah, figure it was probably on the server end

On Wed, Aug 31, 2016 at 9:49 PM, Joseph Ruscio notifications@github.com wrote:

[Librato here] @mbeale https://github.com/mbeale does this correlate with the other reports you were investigating earlier today?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/goodeggs/librato-node/issues/51#issuecomment-243975275, or mute the thread https://github.com/notifications/unsubscribe-auth/AAlbyP9y5SDKaB6JR0uMGE_nBw9X4seCks5qlllogaJpZM4JyJz8 .

mbeale commented 8 years ago

We are still investigating. I will reach out privately when i have new information.

bobzoller commented 8 years ago

closing