Live  /  Providers  /  RXNT

RXNT

rxnt.comNo open incidents

Independent assessment — SquidGrid is not affiliated with RXNT. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks RXNT’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what RXNT is reporting

Current & recent incidents

Resolved

RXnotify

Major impact · 2026-11-05 15:37 UTC · source

Resolved

RXnotify

Major impact · 2026-10-23 06:36 UTC · source

Resolved

Billing and Scheduler app slowness

Minor impact · 2026-10-19 16:03 UTC · source

Resolved

RXnotify

Major impact · 2026-10-14 16:26 UTC · source

Resolved

AI Encounter Generation - Degradation

Minor impact · 2026-10-06 19:30 UTC · source

Resolved

Application Access

None impact · 2026-09-30 03:28 UTC · source

Resolved

RXnotify

Major impact · 2026-09-22 07:16 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 7 incidents from RXNT’s own status page since 2026-09-22.

Recent incidents in the archive

Computed by SquidGrid from the incidents RXNT published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what RXNT has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

RXNT runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of RXNT is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with RXNT.