The recorded URL now redirects offsite — often an acquisition, rebrand, or wind-down; the destination is recorded in the telemetry below. Pulse has been flat over the last 30 days.
HTTP liveness
real
37 probes · Jun 16, 2026 → Aug 27, 2026aliveredirecteddeadunverified
Signal telemetry
4 families · 2 observed · observed only
Liveness probereal
alive in 0% of 37 probesavg response 1648 ms
Developer tractionchecked · none
No public repository linked — GitHub signals are not tracked for this product.
Press & sentimentchecked · none
No coverage found in the tracked press corpus. Absence of press is itself a signal at this stage.
Web footprintreal
resolved host aws.amazon.comedge direct originserver ServerTranco rank #24,300
Domain age & certificate data not yet collected
Analyst read
generated from the observed metrics above · no external narrative
Amazon LightSail's listed URL redirected off its original domain (to https://aws.amazon.com/lightsail/) when we last probed it on Aug 27, 2026 — we mark it redirected, not dead. Its Pulse Index is 24.8 of 100, built from 2 of 4 observed signal families. Observed footprint: 4 functional tags. It sits on the competitive-alternatives graph with 2 linked rivals, so the comparable set below leans on curated edges.
Confidence reflects source and category coherence: curated = an editorially linked alternative; similar = strong functional tag-overlap in the same category; tag-overlap = shared tags only and may be noisy. Overlap is the shared functional-tag ratio (Jaccard) for tag-matched rows. Pulse is the observed-activity index real and 30d Δ its signed month change; a dash means insufficient observed history, never zero.
Structure
observed attributes
Business modelsaas
Liveness tierunknown
Competitive alternatives2
Open sourceNo
Public APINo
Free tierNo
Enterprise tierNo
Funding & team
not in source
No disclosed funding in our sources. Funding data covers only ~1% of the corpus (462 rounds across 79K products), so absence here is unknown, not zero— we don't estimate a number we can't source.
RAW TELEMETRY last 14 probes▾
PROBED
HTTP
ORIGIN → RESOLVED
SERVER
MS
VERDICT
2026-08-27 18:14Z
200
amazonlightsail.com → aws.amazon.com
Server
1823
redirected_offsite
2026-08-26 09:44Z
200
amazonlightsail.com → aws.amazon.com
Server
1842
redirected_offsite
2026-08-19 14:05Z
200
amazonlightsail.com → aws.amazon.com
Server
1907
redirected_offsite
2026-08-11 00:40Z
200
amazonlightsail.com → aws.amazon.com
Server
1569
redirected_offsite
2026-08-08 06:33Z
200
amazonlightsail.com → aws.amazon.com
Server
2469
redirected_offsite
2026-08-05 18:53Z
200
amazonlightsail.com → aws.amazon.com
Server
1722
redirected_offsite
2026-07-30 18:07Z
200
amazonlightsail.com → aws.amazon.com
Server
1937
redirected_offsite
2026-07-23 09:29Z
200
amazonlightsail.com → aws.amazon.com
Server
1379
redirected_offsite
2026-07-22 09:32Z
200
amazonlightsail.com → aws.amazon.com
Server
1417
redirected_offsite
2026-07-21 09:33Z
200
amazonlightsail.com → aws.amazon.com
Server
1487
redirected_offsite
2026-07-20 10:01Z
200
amazonlightsail.com → aws.amazon.com
Server
2002
redirected_offsite
2026-07-19 09:12Z
200
amazonlightsail.com → aws.amazon.com
Server
1411
redirected_offsite
2026-07-18 08:52Z
200
amazonlightsail.com → aws.amazon.com
Server
622
redirected_offsite
2026-07-17 09:15Z
200
amazonlightsail.com → aws.amazon.com
Server
1479
redirected_offsite
Full redirect chains, response headers, and DNS records are not captured by the current probe.
Launch Sentinel tear sheet · Amazon LightSail · as of 2026-08-28 · launchsentinel.com/reports/amazon-lightsail · liveness, pulse and press figures are observed data with provenance shown per panel.