Is Redox Down?

No — Redox is up

Redox's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 357 ms

Right now

The verdict is the worse of these two. How we decide

Redox's status page

status.redoxengine.com · read 3 minutes ago · checked every 3 minutes

Operational

Redox's components, as its status page reports them
Component	Status
Traffic Processing	Operational
Logs (view/search)	Operational
Alerting	Operational
Dashboard Tools	Operational
Platform API	Operational
Developer Docs	Operational
Hosting	Operational
Verato EMPI	Operational
IMO Codeset Normalization	Operational
RLS	Operational
Carequality	Operational
CommonWell	Operational

1 more, all operational · show all 13

All of Redox's components
Component	Status
Traffic Processing	Operational
Logs (view/search)	Operational
Alerting	Operational
Dashboard Tools	Operational
Platform API	Operational
Developer Docs	Operational
Hosting
Hosting	Operational
Third Party Services
Verato EMPI	Operational
IMO Codeset Normalization	Operational
Clinical Networks
RLS	Operational
Carequality	Operational
CommonWell	Operational
DirectTrust	Operational

3 locations All operational

Open their status page

FlareWarden checks

redoxengine.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 357 ms
Checked: 1 hour ago

By region

Ashburn reachable, 259 ms
Chicago reachable, 109 ms
Johannesburg reachable, 1190 ms
London reachable, 134 ms
Los Angeles reachable, 163 ms
Singapore reachable, 398 ms
São Paulo reachable, 349 ms
Tokyo reachable, 254 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	197 ms	1 ms	9 ms	251 ms
Chicago	25 ms	1 ms	9 ms	101 ms
Johannesburg	166 ms	159 ms	168 ms	701 ms
London	36 ms	3 ms	13 ms	124 ms
Los Angeles	113 ms	3 ms	10 ms	156 ms
Singapore	283 ms	2 ms	7 ms	391 ms
São Paulo	121 ms	2 ms	9 ms	341 ms
Tokyo	209 ms	1 ms	13 ms	249 ms

We check that redoxengine.com loads, not every feature behind it. Test it yourself

History

Incidents Redox reported

Since Oct 29, 8 days · from status.redoxengine.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Redox website availability

Measured by FlareWarden · redoxengine.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 229ms

Last 30 days

8-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of redoxengine.com from multiple regions every 6 hours. Redox's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 8 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Redox does

Redox connects healthcare software to hospital and clinic systems. Digital health companies send and receive patient data through one Redox API instead of building a separate interface to every electronic health record, and Redox also connects to national networks such as Carequality and CommonWell. When Redox has trouble, messages between an app and the health systems it serves are delayed or fail.

What an outage looks like

Synchronous API requests return errors and asynchronous messages queue up, as on September 8, 2026, when a third-party infrastructure outage disrupted processing for about 40 minutes. More often only the dashboard lags: message logs appear late while traffic processes normally (September 9, June 22, March 16). Network-specific problems show as failed or empty Carequality queries (July 9, April 13) or VPN tunnels that cannot deliver (May 6).

What to do about it

Check status.redoxengine.com, which separates Traffic Processing, the Platform API, logs, the dashboard, each clinical network and each AWS region. When processing fails, Redox asks customers to put their downtime procedures into effect and to contact support@redoxengine.com with questions. If only log visibility is delayed, messages are still being processed, so do not resend them.

Is it down for everyone, or just you?

If this page says Redox is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Redox outage FAQ

Are messages lost when Redox is down?

Not as a rule. In the September 8, 2026 incident Redox said asynchronous processing was delayed, which means queued messages were processed late, while synchronous requests returned errors and had to be retried by the caller. Redox's postmortem said it failed over to backup infrastructure. Check the incident's updates before resending anything, to avoid duplicates.

Why can't I see my messages in the Redox dashboard?

Redox regularly posts incidents where log visibility in the dashboard is delayed while messages keep processing, as on September 9, June 22 and March 16, 2026. In those cases traffic is flowing and only the record of it is late, so the Logs component on status.redoxengine.com is the one to watch.

Does a Carequality or CommonWell outage affect Redox?

It affects queries that go through those networks. The status page lists Carequality, CommonWell, RLS and DirectTrust as their own components. On July 9, 2026 documents were not returned for outbound Carequality DocumentGet requests, and on April 13 Carequality queries saw more HTTP 500 errors, while other Redox traffic was not named.

Does an AWS outage affect Redox?

It can. Redox lists AWS us-east-1, us-west-1 and us-west-2 as hosting components on its status page, so an AWS problem in one of those regions is worth checking against status.redoxengine.com. The September 8, 2026 outage was caused by a third-party infrastructure provider Redox uses for message processing.

How we measure this

We request Redox's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Redox publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Redox itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Redox goes down

We check Redox every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required