Last checked: 9 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: March 2, 2023, 5:03 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: March 2, 2023, 5:03 p.m.
Description: ### **Root cause** A code change had the unexpected result of preventing a small number of customers from requesting \(legacy\) JWT-based authentication to Redox. ### **Impact on customers** Customers using legacy JWT auth were unable to authenticate with the Redox API. Being that this was a legacy auth method, only a small number \(< 5\) of Redox customers were using this and were affected. ## What Happened? At approximately 11 AM CT a code change was made which unintentionally affected the use of _legacy_ JWT-based authentication tokens. We received reports from a customer at approximately 1:30 PM CT that they were unable to request new access tokens and authenticate with Redox. Shortly after 2 PM CT the code change was reverted and by 2:30 PM CT Redox was able to confirm that the issue had been resolved. ## Learnings / Follow-ups Redox will be investigating improvements to our alerting to lead to quicker identification of these authentication issues in the future.
Status: Postmortem
Impact: Minor | Started At: Feb. 22, 2023, 8:17 p.m.
Description: ### **Root cause** A code change had the unexpected result of preventing a small number of customers from requesting \(legacy\) JWT-based authentication to Redox. ### **Impact on customers** Customers using legacy JWT auth were unable to authenticate with the Redox API. Being that this was a legacy auth method, only a small number \(< 5\) of Redox customers were using this and were affected. ## What Happened? At approximately 11 AM CT a code change was made which unintentionally affected the use of _legacy_ JWT-based authentication tokens. We received reports from a customer at approximately 1:30 PM CT that they were unable to request new access tokens and authenticate with Redox. Shortly after 2 PM CT the code change was reverted and by 2:30 PM CT Redox was able to confirm that the issue had been resolved. ## Learnings / Follow-ups Redox will be investigating improvements to our alerting to lead to quicker identification of these authentication issues in the future.
Status: Postmortem
Impact: Minor | Started At: Feb. 22, 2023, 8:17 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Feb. 15, 2023, 8:47 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.