rewindex

ChangesLambdalambda.ai Unreachable Due to DNS Issue

Lambda: Incident updated: lambda.ai Unreachable Due to DNS Issue

Incident updateNormal progress (typesafe/jev-1.13-20260917, 96%)Changed status.lambda.ai (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Discussed on Hacker News

Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.

Incident page: the full timeline of updates

What changed

Struck in red is what Lambda removed; blue is what they added. Muted text is unchanged context.

ChangedTitle#1
Before: Lambda Cloud Dashboard Down
After: lambda.ai Unreachable Due to DNS Issue
ChangedStatus#2
Before: monitoring
After: resolved
AddedResolved time#3
Before: not present
After: 2026-10-31 07:07 UTC
AddedUpdateresolved#4
Before: not present
After: Severity Level: [High] The incident has been resolved. lambda.ai: http://lambda.ai is now working as expected. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please open a support ticket and we’ll get back to you as soon as possible. • https://support.lambdalabs.com/hc/en-us/requests/new To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

TodaySaturday, October 31Sat, Oct 31

3 incident changes

All Lambda changesLambda profileMarkdownJSON