polylane

Most incidents start with a change. Polylane records every one and watches the aftermath.

Join the waitlist
Clouds prod-aws Changes

SQS visibility timeout lowered on checkout-events

Moderate impact configuration ·Synced 12 minutes ago

VisibilityTimeout on checkout-events dropped from 120s to 15s. Consumers that hold a message longer than 15 seconds will see it delivered twice; the dead-letter queue threshold is unchanged.

What we're watching
ApproximateAgeOfOldestMessage
checkout-events · baseline at change 3.2s · worse if up
Watching: no issue since this change
NumberOfMessagesReceived
checkout-events · baseline at change 41/min · worse if up
Watching: no issue since this change
Triggering events
SetQueueAttributes CloudTrail · deploy-bot · 12:41:02Z attached to this record's delta window
Full diff (3 changes)
Nodes (2) Edges (1)
2 nodes modified · 1 edge removed

“What changed?” answers itself. Nobody has to remember. Nobody has to confess.

  • Every change, recorded

    Polylane diffs your cloud against the last time it looked. Certificate renewals and other churn never make it in.

  • Who and what, together

    The deploy or CloudTrail entry that caused a change lands on its record.

  • Graded for risk

    An agent writes down how much a change could hurt, and why.

  • The aftermath, watched

    Each record names the metrics that would show trouble. If one moves, the issue links straight back to the change.

Ask from anywhere. The console, the feed, or your terminal.

Every resource keeps its own history, notable changes land in your feed, and you can ask what changed in the last hour from a thread, the API, or your coding agent over MCP.

The next incident is a change you haven't noticed yet. Polylane notices.

Join the waitlist