Correlation

Signals raised in different tools that look like the same underlying problem. Each group shows why it formed, not just that it did - and anything that didn't link is listed too, because a correlation tool that links everything is worse than one that doesn't.

Real (Live) and synthetic signals are never correlated with each other - a group marked Live contains only real records.

Threshold

Two signals link when their weighted confidence reaches the threshold. Confidence is 20% service area, 20% timing (opened within 4h of each other) and 60% text similarity. Change it and the groups re-form instantly - no re-scoring needed.

70%

5 correlation groups

2 signals, 1 likely root causespanning Jira and Rootly

Live97% confidence

Suggested root cause - AI-generated, unverified

A stale DNS resolver cache on the API gateway fleet caused intermittent lookup failures surfacing as sporadic 502s to partner callers.

JiraKAN-4Intermittent 502s reported via partner integrations hitting the API gatewayMediumOpen
Rootly7[Demo] Intermittent DNS resolution failures on the API gatewayHighInvestigating

When each was open

Rootly7
JiraKAN-4

16d 3h agonow

What matched

Service areaExact match · weight 20%

partner api

Time window223 of 240 min shared · weight 20%

Least-overlapping pair in the group

Text similarityClaude97% · weight 60%

Average across pairs

Confidence is the weighted blend of these three - 20% service area + 20% timing + 60% text - averaged over the group's pairs: 97%. A group forms when confidence reaches the threshold.

Pair by pair

Pair	Area	Overlap	Text	Confidence
KAN-4 ↔ 7	exact	223 min	97% (claude)	97%

3 signals, 1 likely root causespanning Incident Platform, Partner Channel and Service Desk

90% confidence

Suggested root cause - AI-generated, unverified

The settlement batch job terminated before processing all partitions, so the report covers only part of the merchants.

Incident PlatformINC-204Settlement batch job exceeded runtime and was terminatedHighInvestigating
Partner ChannelPC-303Kestrel Logistics: yesterday's settlement file has not arrivedMediumOpen
Service DeskSD-103Finance ops: nightly settlement report incompleteMediumOpen

When each was open

Incident PlatformINC-204
Service DeskSD-103
Partner ChannelPC-303

10h 55m agonow

What matched

Service areaExact match · weight 20%

payments

Time window195 of 240 min shared · weight 20%

Least-overlapping pair in the group

Text similarityClaude87% · weight 60%

Average across pairs

Confidence is the weighted blend of these three - 20% service area + 20% timing + 60% text - averaged over the group's pairs: 90%. A group forms when confidence reaches the threshold.

Pair by pair

Pair	Area	Overlap	Text	Confidence
SD-103 ↔ INC-204	exact	225 min	90% (claude)	93%
INC-204 ↔ PC-303	exact	195 min	90% (claude)	90%
SD-103 ↔ PC-303	exact	210 min	80% (claude)	86%

3 signals, 1 likely root causespanning Incident Platform, Security Operations and Service Desk

89% confidence

Suggested root cause - AI-generated, unverified

Both records track the same detected surge of failed sign-ins from unrecognised locations, handed from the security alert into incident management.

Incident PlatformINC-206Security incident: suspected credential-stuffing against customer sign-inHighInvestigating
Security OperationsSEC-401Alert: spike in failed sign-ins from unrecognised locations across many accountsHighInvestigating
Service DeskSD-106Customers locked out after repeated sign-in attempts they did not makeHighOpen

When each was open

Security OperationsSEC-401
Incident PlatformINC-206
Service DeskSD-106

1h 40m agonow

What matched

Service areaRelated areas · weight 20%

authentication ↔ identity

Time window210 of 240 min shared · weight 20%

Least-overlapping pair in the group

Text similarityClaude95% · weight 60%

Average across pairs

Confidence is the weighted blend of these three - 20% service area + 20% timing + 60% text - averaged over the group's pairs: 89%. A group forms when confidence reaches the threshold.

Pair by pair

Pair	Area	Overlap	Text	Confidence
INC-206 ↔ SEC-401	exact	235 min	97% (claude)	98%
SD-106 ↔ INC-206	related	215 min	95% (claude)	85%
SD-106 ↔ SEC-401	related	210 min	93% (claude)	83%

2 signals, 1 likely root causespanning Incident Platform and Service Desk

86% confidence

Suggested root cause - AI-generated, unverified

Degraded SMS delivery through the messaging provider caused missing or delayed login passcodes.

Incident PlatformINC-203Elevated failure rate sending SMS one-time passcodes through messaging providerHighResolved
Service DeskSD-102Customers not receiving one-time passcodes at loginHighResolved

When each was open

Service DeskSD-102
Incident PlatformINC-203

20h 30m agonow

What matched

Service areaRelated areas · weight 20%

authentication ↔ identity

Time window225 of 240 min shared · weight 20%

Least-overlapping pair in the group

Text similarityClaude95% · weight 60%

Average across pairs

Confidence is the weighted blend of these three - 20% service area + 20% timing + 60% text - averaged over the group's pairs: 86%. A group forms when confidence reaches the threshold.

Pair by pair

Pair	Area	Overlap	Text	Confidence
SD-102 ↔ INC-203	related	225 min	95% (claude)	86%

5 signals, 1 likely root causespanning Incident Platform, Partner Channel and Service Desk

83% confidence

Suggested root cause - AI-generated, unverified

Slow partner portal application-submit path is causing both the latency alert and the partner's multi-minute submissions.

Incident PlatformINC-201P2 — elevated latency on partner-facing API gatewayHighInvestigating
Incident PlatformINC-202Synthetic check failing: partner portal submit endpoint p95 above 8sMediumInvestigating
Partner ChannelPC-301Meridian Retail: customer applications taking minutes to submitHighOpen
Partner ChannelPC-302Halcyon Travel: booking applications timing out at final stepMediumOpen
Service DeskSD-101Users reporting slow application submission on partner portalHighInvestigating

When each was open

Service DeskSD-101
Incident PlatformINC-201
Partner ChannelPC-301
Incident PlatformINC-202
Partner ChannelPC-302

3h 20m agonow

What matched

Service areaRelated areas · weight 20%

partner api ↔ partner portal

Time window190 of 240 min shared · weight 20%

Least-overlapping pair in the group

Text similarityClaude81% · weight 60%

Average across pairs

Confidence is the weighted blend of these three - 20% service area + 20% timing + 60% text - averaged over the group's pairs: 83%. A group forms when confidence reaches the threshold.

Pair by pair

Pair	Area	Overlap	Text	Confidence
INC-202 ↔ PC-301	exact	228 min	90% (claude)	93%
SD-101 ↔ PC-301	exact	212 min	90% (claude)	92%
SD-101 ↔ INC-202	exact	200 min	90% (claude)	91%
INC-202 ↔ PC-302	exact	230 min	75% (claude)	84%
SD-101 ↔ INC-201	related	225 min	85% (claude)	80%
SD-101 ↔ PC-302	exact	190 min	70% (claude)	78%
INC-201 ↔ PC-301	related	227 min	80% (claude)	77%
INC-201 ↔ PC-302	related	205 min	65% (claude)	66%

Problem candidates

Two or more separate groups in the same service (or the same family of services) that describe similar things, which points at a cause worth finding rather than another fix. Similar means at least 20% of the distinctive words in common, a plain wording check that is weaker than the similarity used inside a group, so it can miss a recurrence and never invents one. Only synthetic groups count.

None right now: no two of the 5 active groups share a service and enough wording to look like the same recurring problem.

Considered, not linked

The strongest pairs that did not become a link at 70%, and why. A further 14 signals had no candidate partner at all - no signal from another source in a related area within 4h.

Incident PlatformINC-201Partner ChannelPC-304
43% confidence
P2 — elevated latency on partner-facing API gatewayBrightwater Foods: request for updated API documentation
Not linked: The wording doesn't match - text similarity is only 5%, so the two records look like different problems. (One of the two is part of another group.)
Incident PlatformINC-202Partner ChannelPC-304
34% confidence
Synthetic check failing: partner portal submit endpoint p95 above 8sBrightwater Foods: request for updated API documentation
Not linked: The wording doesn't match - text similarity is only 10%, so the two records look like different problems. (One of the two is part of another group.)
Service DeskSD-105Incident PlatformINC-203
32% confidence
Customer asks how to change the address on their profileElevated failure rate sending SMS one-time passcodes through messaging provider
Not linked: The wording doesn't match - text similarity is only 5%, so the two records look like different problems. (One of the two is part of another group.)
Service DeskSD-101Partner ChannelPC-304
32% confidence
Users reporting slow application submission on partner portalBrightwater Foods: request for updated API documentation
Not linked: The wording doesn't match - text similarity is only 5%, so the two records look like different problems. (One of the two is part of another group.)