Skip to content

Count Amazon's time servers as time sync - #272

Merged
drudge merged 2 commits into
mainfrom
claude/amazon-time-servers
Sep 29, 2026
Merged

drudge merged 2 commits into
mainfrom
claude/amazon-time-servers

Conversation

@drudge

@drudge drudge commented Sep 29, 2026

Copy link
Copy Markdown
Owner

Two Ring cameras showed up in Insights as Started using a new app: Amazon (Shopping) after they set their clocks from ntp-g7g.amazon.com. That's the time server Amazon's devices fall back to when their usual *.amazon.pool.ntp.org servers don't answer, which happened during a stretch of failed lookups this morning. The catalog gives every amazon.com name to the Amazon shopping app.

What changed

  • Time sync owns ntp-g7g.amazon.com, and AWS's public time.aws.com, beside the Meta and Google time servers from Count brands' public time servers as time sync #267. Insights leaves Time sync out of new app findings.
  • ntp-fireos.com stays out. Despite the name, it carries Amazon device metrics, not time.
  • Tests: Lookup gives ntp-g7g.amazon.com to Time sync while www.amazon.com stays Amazon, and a device whose new lookups include ntp-g7g.amazon.com gets no Amazon finding. Both fail against the old catalog.

No console change, so no screenshots.

Checks

  • go tool mage verify and gofmt -l .

Two Ring cameras showed up in Insights as "Started using a new app:
Amazon" after they set their clocks from ntp-g7g.amazon.com, the time
server Amazon's devices fall back to when their usual pool doesn't
answer. The catalog gives every amazon.com name to the Amazon shopping
app. ntp-g7g.amazon.com, and AWS's public time.aws.com, now belong to
Time sync, which Insights leaves out of new app findings.
@drudge
drudge merged commit 7c07a91 into main Sep 29, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant