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: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 12, 2024, 6:19 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 12, 2024, 1:11 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 12, 2024, 1:11 p.m.
Description: ## Summary From June 10-12, 2024 <2.5% of Logs were intermittently unavailable to view or search in the Redox dashboard for approximately two hours accumulatively. Message processing was unaffected. ## What Happened & How We Responded * On the evening of June 10, we experienced bottlenecks in the throughout of our Logs processing. * On June 11th at 0024CT, we scaled up processing power and added additional observability metrics. This initially appeared to remediate the issue. * On June 12th at 0842CT, the issue resurfaced and we discovered and remediated a code limitation that caused the software to fall behind while processing payloads. This fully remediated the issue, and we added additional monitoring to alert us to similar potential failures in the future. ## What we are doing about this: * We will retain the code optimization we made moving forward. * We added additional monitoring to alert us to similar potential failures in the future.
Status: Postmortem
Impact: Minor | Started At: June 11, 2024, 7:29 p.m.
Description: ## Summary From June 10-12, 2024 <2.5% of Logs were intermittently unavailable to view or search in the Redox dashboard for approximately two hours accumulatively. Message processing was unaffected. ## What Happened & How We Responded * On the evening of June 10, we experienced bottlenecks in the throughout of our Logs processing. * On June 11th at 0024CT, we scaled up processing power and added additional observability metrics. This initially appeared to remediate the issue. * On June 12th at 0842CT, the issue resurfaced and we discovered and remediated a code limitation that caused the software to fall behind while processing payloads. This fully remediated the issue, and we added additional monitoring to alert us to similar potential failures in the future. ## What we are doing about this: * We will retain the code optimization we made moving forward. * We added additional monitoring to alert us to similar potential failures in the future.
Status: Postmortem
Impact: Minor | Started At: June 11, 2024, 7:29 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.