Truemed Outage History

Truemed is up right now

Truemed had 3 outages in the last 2 years totaling 1h 59m of downtime — averaging 0.1 incidents per month.

There were 3 Truemed outages since November 18, 2025 totaling 1h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.truemed.com

Major July 24, 2026

API outage

Detected by Pingoru
Jul 24, 2026, 11:07 AM UTC
Resolved
Jul 24, 2026, 12:04 PM UTC
Duration
56m
Affected: API
Timeline · 3 updates
  1. investigating Jul 24, 2026, 11:07 AM UTC

    API cannot be accessed at the moment. This incident was created by an automated monitoring service.

  2. resolved Jul 24, 2026, 12:04 PM UTC

    API is now operational! This update was created by an automated monitoring service.

  3. resolved Jul 29, 2026, 06:12 PM UTC

    This incident has been resolved. The root cause was an outage with one of our providers ([further details here).](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-west-2::event/MULTIPLE%5FSERVICES/AWS%5FMULTIPLE%5FSERVICES%5FOPERATIONAL%5FISSUE/AWS%5FMULTIPLE%5FSERVICES%5FOPERATIONAL%5FISSUE%5F83A36%5F24C89B493A6)

Read the full incident report →

Major July 24, 2026

Frontend outage

Detected by Pingoru
Jul 24, 2026, 11:02 AM UTC
Resolved
Jul 24, 2026, 12:05 PM UTC
Duration
1h 3m
Timeline · 2 updates
  1. investigating Jul 24, 2026, 11:02 AM UTC

    Frontend cannot be accessed at the moment. This incident was created by an automated monitoring service.

  2. resolved Jul 24, 2026, 12:05 PM UTC

    Frontend is now operational! This update was created by an automated monitoring service.

Read the full incident report →

Major March 26, 2026

Website outage

Detected by Pingoru
Mar 26, 2026, 08:59 PM UTC
Resolved
Mar 26, 2026, 08:59 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 26, 2026, 08:59 PM UTC

    Type: Incident Duration: 5 minutes Mar 26, 20:59:41 GMT+0 - Investigating - Website cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 26, 21:04:43 GMT+0 - Resolved - Website is now operational! This update was created by an automated monitoring service.

Read the full incident report →