ES /docs

Failed to put records: Failed to open TCP connection to kinesis.us-west-2.amazonaws.com:443 (executi

Service
cupixworks-api
Occurrences
2
Status
Approved
Confidence
85%
Actionability
52%
Cluster ID
00c90beb-425a-4d4f-b82f-69f2a2f814df
First Seen
2026-07-17 13:45 UTC
Last Seen
2026-07-24 08:40 UTC
Actions
현재 상태 approved 에서는 실행할 액션이 없습니다.

Failed to put records: Failed to open TCP connection to kinesis.us-west-2.amazonaws.com:443 (executi

What Happened#

2026-07-17 22:45 KST, cupixworks-api (production, us-west-2) 에서 model update callback 이 site-insights 이벤트를 Kinesis 스트림에 동기 publish 시도하다가 kinesis.us-west-2.amazonaws.com:443 로의 TCP 소켓 open 이 timeout 되며 실패했다. 단일 요청 1회 발생이며, 같은 초에 caller-level(Failed to create event) 과 SDK-level(Failed to put records) 두 개의 error 로그가 페어로 남았다.

Quick Facts#

Field Value
exception.class Seahorse::Client::NetworkingError (wraps Net::OpenTimeout)
exception.message Failed to open TCP connection to kinesis.us-west-2.amazonaws.com:443 (execution expired)
top_frame lib/cupix/aws/kinesis.rb:9 (kinesis_client.put_records)
runtime Ruby / Rails (cupixworks-api)
env production, us-west-2, tenant cupix

Affected Teams#

Team / Domain Error Count Impact
cupixworks-api (site-insights event publish) 2 로그 / 1 요청 단일 API request 의 모델 업데이트 콜백이 500 으로 실패했을 가능성 (site-insights 이벤트 소실)

Timeline#

  1. 2026-07-17 22:45:51 KSTEventable::Events::Update.create_event 콜백이 Cupix::EventService.publish_event 를 호출해 Kinesis put_records! 로 진입.
  2. 2026-07-17 22:45:51 KSTAws::Kinesis::Client#put_records 내부의 HTTP open 이 timeout, Net::OpenTimeout (execution expired) 발생. Cupix::Aws::Kinesis.put_records! 의 rescue 블록이 Failed to put records: ... 를 로깅하고 raise.
  3. 2026-07-17 22:45:51 KSTEventable::Events::Base.create_eventrescue StandardError 가 이 예외를 잡아 Failed to create event: ... 를 로깅하고 재-raise. 이후 자동 재시도 없음.
  4. 2026-07-17 22:45:51 KST — status-board 가 sibling cluster 28729bf3-51f6-47d0-80ba-c79bd2a8ee61 와 함께 svc:cupixworks-api::unknown 인시던트 2026-07-17-svc-cupixworks-api--unknown-2 로 자동 그룹핑 (동일 초, 이후 재발 없음 — resolved).

Scoring#

Confidence 85% · Actionability 52%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 15 code refs, 6 log queries
Code path explicitness 3/3 15 file:line refs
Log evidence 3/3 section, query, pattern
RCA structure 3/3 3/3 sections
Revision history 0/3 0 revision(s)
Agent execution 3/3 success

Actionability#

Dimension Score Detail
Fix complexity 5/5 trivial
Affected files 1/5 16 file(s)
Single repo 1/3 2 service(s)
Immediate actions 0/3 absent
Testability 2/3 test mentioned
External dependency 1/3 external deps found
Data migration 3/3 no migration