Verified live by HTTP probe across 38 observations. Pulse has been flat over the last 30 days.
HTTP liveness
real
38 probes · Jun 13, 2026 → Aug 27, 2026aliveredirecteddeadunverified
Signal telemetry
4 families · 2 observed · observed only
Liveness probereal
alive in 100% of 38 probesavg response 3182 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 go.chatwork.comedge direct originserver nginxTranco rank #44,443
Domain age & certificate data not yet collected
Analyst read
generated from the observed metrics above · no external narrative
Chatwork's listed site resolved live when we last probed it on Aug 27, 2026, so we mark it verified alive. Its Pulse Index is 48.2 of 100, built from 2 of 4 observed signal families. Observed footprint: 11 functional tags. It sits on the competitive-alternatives graph with 3 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 modelunknown
Liveness tierquiet
Competitive alternatives3
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:13Z
200
chatwork.com → go.chatwork.com
nginx
2472
alive
2026-08-26 09:43Z
200
chatwork.com → go.chatwork.com
nginx
4567
alive
2026-08-19 14:04Z
200
chatwork.com → go.chatwork.com
nginx
3178
alive
2026-08-11 00:39Z
200
chatwork.com → go.chatwork.com
nginx
3968
alive
2026-08-08 06:32Z
200
chatwork.com → go.chatwork.com
nginx
3211
alive
2026-08-05 18:52Z
200
chatwork.com → go.chatwork.com
nginx
4140
alive
2026-07-30 18:06Z
200
chatwork.com → go.chatwork.com
nginx
3593
alive
2026-07-23 09:27Z
200
chatwork.com → go.chatwork.com
nginx
2504
alive
2026-07-22 09:31Z
200
chatwork.com → go.chatwork.com
nginx
3108
alive
2026-07-21 09:32Z
200
chatwork.com → go.chatwork.com
nginx
2486
alive
2026-07-20 09:59Z
200
chatwork.com → go.chatwork.com
nginx
3800
alive
2026-07-19 09:11Z
200
chatwork.com → go.chatwork.com
nginx
2635
alive
2026-07-18 08:51Z
200
chatwork.com → go.chatwork.com
nginx
1258
alive
2026-07-17 09:13Z
200
chatwork.com → go.chatwork.com
nginx
3621
alive
Full redirect chains, response headers, and DNS records are not captured by the current probe.
Launch Sentinel tear sheet · Chatwork · as of 2026-08-28 · launchsentinel.com/reports/chatwork · liveness, pulse and press figures are observed data with provenance shown per panel.