The recorded URL now redirects offsite — often an acquisition, rebrand, or wind-down; the destination is recorded in the telemetry below. Pulse momentum is positive over 30 days (+8.0).
HTTP liveness
real
17 probes · Jun 16, 2026 → Aug 28, 2026aliveredirecteddeadunverified
Signal telemetry
4 families · 2 observed · observed only
Liveness probereal
alive in 0% of 17 probesavg response 3048 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.
generated from the observed metrics above · no external narrative
Urgent.ly's listed URL redirected off its original domain (to https://partners.geturgently.com/) when we last probed it on Aug 28, 2026 — we mark it redirected, not dead. Its Pulse Index is 21.2 of 100, built from 2 of 4 observed signal families. Observed footprint: 7 functional tags. It has no curated competitive-alternative edges yet, so the comparable set below is functional tag-similarity — read it with the confidence flags.
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 alternativesnone linked
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-28 00:33Z
200
urgent.ly → partners.geturgently.com
cloudflare
1837
redirected_offsite
2026-08-19 14:28Z
200
urgent.ly → partners.geturgently.com
cloudflare
2939
redirected_offsite
2026-08-11 01:02Z
200
urgent.ly → partners.geturgently.com
cloudflare
1921
redirected_offsite
2026-08-08 06:58Z
200
urgent.ly → partners.geturgently.com
cloudflare
2888
redirected_offsite
2026-08-05 19:15Z
200
urgent.ly → partners.geturgently.com
cloudflare
3003
redirected_offsite
2026-07-30 18:29Z
200
urgent.ly → partners.geturgently.com
cloudflare
2729
redirected_offsite
2026-07-23 09:57Z
—
—
—
10009
timeout
2026-07-18 09:06Z
200
urgent.ly → partners.geturgently.com
cloudflare
1990
redirected_offsite
2026-07-11 09:19Z
200
urgent.ly → partners.geturgently.com
cloudflare
2869
redirected_offsite
2026-07-04 13:14Z
200
urgent.ly → partners.geturgently.com
cloudflare
3125
redirected_offsite
2026-06-23 14:23Z
200
urgent.ly → partners.geturgently.com
cloudflare
2001
redirected_offsite
2026-06-21 17:28Z
200
urgent.ly → partners.geturgently.com
cloudflare
2298
redirected_offsite
2026-06-21 17:28Z
200
urgent.ly → partners.geturgently.com
cloudflare
2008
redirected_offsite
2026-06-20 06:50Z
200
urgent.ly → partners.geturgently.com
cloudflare
3049
redirected_offsite
Full redirect chains, response headers, and DNS records are not captured by the current probe.
Launch Sentinel tear sheet · Urgent.ly · as of 2026-08-28 · launchsentinel.com/reports/urgent-ly · liveness, pulse and press figures are observed data with provenance shown per panel.