Entrata Outage History

Entrata is up right now

Entrata had 4 outages in the last 2 years totaling 33h 39m of downtime — averaging 0.2 incidents per month.

There were 4 Entrata outages since June 26, 2024 totaling 33h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.entrata.com

Minor February 9, 2026

Entrata Standard Login Degraded Performance

Detected by Pingoru
Feb 09, 2026, 05:46 PM UTC
Resolved
Feb 10, 2026, 04:35 PM UTC
Duration
22h 48m
Affected: Entrata Standard Login
Timeline · 5 updates
  1. investigating Feb 09, 2026, 05:46 PM UTC

    We are investigating an issue causing some users to be logged out unexpectedly and experience intermittent login issues in Entrata Standard. Our engineering teams are actively reviewing system metrics and backend services to identify the root cause. We will provide updates as more information becomes available.

  2. identified Feb 09, 2026, 06:26 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Feb 09, 2026, 08:09 PM UTC

    Mitigation efforts are under way. We are seeing improvements in system behavior and continue to monitor closely while changes are applied to ensure stability.

  4. monitoring Feb 09, 2026, 09:25 PM UTC

    The actions taken to address the login issues impacting Entrata Standard have reduced the impact. We are continuing to monitor system performance closely to ensure stability and will provide additional updates if needed.

  5. resolved Feb 10, 2026, 04:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 7, 2025

Email Delay

Detected by Pingoru
Jan 07, 2025, 06:36 PM UTC
Resolved
Jan 08, 2025, 01:14 AM UTC
Duration
6h 37m
Affected: Entrata Standard ApplicationEntrata Rapid Application
Timeline · 8 updates
  1. identified Jan 07, 2025, 06:36 PM UTC

    We are currently experiencing delays in the delivery of 2FA emails and Message Center emails. The issue has been identified as originating from a third-party service, and we are actively working to resolve it. At this time, we are unable to provide an estimated timeframe for email delivery.

  2. identified Jan 07, 2025, 06:39 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Jan 07, 2025, 07:01 PM UTC

    We are still unable to provide an estimated timeframe for email delivery.

  4. identified Jan 07, 2025, 07:23 PM UTC

    We are continuing to work on a fix for this issue. We are still unable to provide an estimated timeframe for email delivery.

  5. identified Jan 07, 2025, 07:45 PM UTC

    We are continuing to work on a fix for this issue. We are still unable to provide an estimated timeframe for email delivery.

  6. identified Jan 07, 2025, 08:05 PM UTC

    We are continuing to work on a fix for this issue. We are still unable to provide an estimated timeframe for email delivery.

  7. identified Jan 08, 2025, 12:15 AM UTC

    We are continuing to work on a fix for this issue. We are still unable to provide an estimated timeframe for email delivery.

  8. resolved Jan 08, 2025, 01:14 AM UTC

    This issue has been resolved and emails are now being sent out. Thank you for your patience.

Read the full incident report →

Minor June 27, 2024

General Slowness

Detected by Pingoru
Jun 27, 2024, 07:07 PM UTC
Resolved
Jun 27, 2024, 11:20 PM UTC
Duration
4h 13m
Affected: Entrata Standard ApplicationEntrata Standard LoginEntrata Standard ReportingEntrata Standard PDF Conversions
Timeline · 5 updates
  1. identified Jun 27, 2024, 07:07 PM UTC

    We are aware of general slowness and errors impacting some customers. We are actively investigating the issue.

  2. identified Jun 27, 2024, 08:13 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 27, 2024, 09:02 PM UTC

    We are continuing to monitor. General slowness and errors may still be impacting some areas.

  4. monitoring Jun 27, 2024, 10:33 PM UTC

    Mitigated: Service restored

  5. resolved Jun 27, 2024, 11:20 PM UTC

    This incident has been resolved.

Read the full incident report →