Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for Redox Engine and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Redox Engine.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
API | Active |
Carequality | Active |
Dashboard | Active |
Data Models | Active |
docs.redoxengine.com | Active |
Engine Core | Active |
Polling | Active |
redoxengine.com | Active |
RLS | Active |
ScienceIO ScienceIO API | Active |
VPN | Active |
Hosting | Active |
AWS ec2-us-east-1 | Active |
AWS ec2-us-west-1 | Active |
AWS ec2-us-west-2 | Active |
Hosting | Active |
Third Party Services | Active |
IMO Codeset Normalization | Active |
Verato EMPI | Active |
View the latest incidents for Redox Engine and check for official updates:
Description: A fix has been implemented and processing has returned to normal. This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Oct. 1, 2024, 3:51 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Sept. 16, 2024, 12:15 p.m.
Description: # Logs intermittently unavailable to view or search ## Summary From August 25-26, 2024 Logs were intermittently delayed or unavailable to view or search in the Redox dashboard. Message processing was unaffected. ## What Happened & How We Responded * On the morning of August 25, AWS initiated an automated failover of their managed database service due to an underlying storage volume issue which subsequently affected throughput of our logs processing. * On August 25th at 0539CT, we restarted impacted application processes which resolved the immediate issue. * On August 26th at 0758CT, we were alerted that logs were again falling behind in processing time. Working with AWS support, we uncovered that the underlying storage from the failover the previous day was still being optimized, resulting in database write latency. The storage optimization completed at 1500CT, and the service was fully available again at 2229CT. ## What we are doing about this: * We are exploring an underlying storage system change to further increase our infrastructure durability.
Status: Postmortem
Impact: Major | Started At: Aug. 26, 2024, 1:15 p.m.
Description: # Logs intermittently unavailable to view or search ## Summary From August 25-26, 2024 Logs were intermittently delayed or unavailable to view or search in the Redox dashboard. Message processing was unaffected. ## What Happened & How We Responded * On the morning of August 25, AWS initiated an automated failover of their managed database service due to an underlying storage volume issue which subsequently affected throughput of our logs processing. * On August 25th at 0539CT, we restarted impacted application processes which resolved the immediate issue. * On August 26th at 0758CT, we were alerted that logs were again falling behind in processing time. Working with AWS support, we uncovered that the underlying storage from the failover the previous day was still being optimized, resulting in database write latency. The storage optimization completed at 1500CT, and the service was fully available again at 2229CT. ## What we are doing about this: * We are exploring an underlying storage system change to further increase our infrastructure durability.
Status: Postmortem
Impact: Minor | Started At: Aug. 25, 2024, 10:03 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 26, 2024, 3:43 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.