High latency and intermittent failure in UAT AMER
Last updateresolvedAug 30 · 04:45 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
Operational
12 components
checked Sep 11, 2026 3:39 PM UTC · Thomson Reuters Corporates's official status page
Thomson Reuters Corporates is up and running.
All components operational
Statusfield watches Thomson Reuters Corporates alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
15 reports published by Thomson Reuters Corporates in the last 30 days
When Thomson Reuters Corporates breaks, it is typically resolved in 10h 24m — median across 25 resolved incidents over 90 days.
resolvedAug 30 · 04:45 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 27 · 11:21 UTC
The data catchup is complete.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 26 · 14:20 UTC
The data catch-up process has been completed successfully
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 25 · 13:39 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 24 · 19:00 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 23 · 06:46 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 22 · 04:47 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 21 · 19:30 UTC
This incident has been resolved, and the team will continue to monitor.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 19 · 10:50 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 19 · 19:29 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 19 · 00:58 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 17 · 14:28 UTC
This incident was resolved on Friday, August 14, 2026.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 14 · 07:40 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
resolvedAug 13 · 10:18 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.
resolvedSep 11 · 15:06 UTC
This incident has been resolved.
Reported by Thomson Reuters Corporates on their status page.