Everee Outage History

Everee is up right now

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

There were 3 Everee outages since October 30, 2025 totaling 1h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.everee.com

Major September 27, 2026

Time Clock Terminal is down

Detected by Pingoru
Sep 27, 2026, 02:38 AM UTC
Resolved
Sep 27, 2026, 02:41 AM UTC
Duration
3m
Affected: Current status by service (Time Clock Terminal)Current status by service (Time Clock Terminal)
Timeline · 2 updates
  1. investigating Sep 27, 2026, 02:38 AM UTC

    Time Clock Terminal went down.

  2. resolved Sep 27, 2026, 02:41 AM UTC

    Time Clock Terminal recovered.

Read the full incident report →

Major July 31, 2026

API is down

Detected by Pingoru
Jul 31, 2026, 12:23 PM UTC
Resolved
Jul 31, 2026, 12:26 PM UTC
Duration
2m
Affected: Current status by service (API)Current status by service (API)
Timeline · 2 updates
  1. investigating Jul 31, 2026, 12:23 PM UTC

    API went down.

  2. resolved Jul 31, 2026, 12:26 PM UTC

    API recovered.

Read the full incident report →

Minor October 30, 2025

Notifications are delayed

Detected by Pingoru
Oct 30, 2025, 06:00 PM UTC
Resolved
Oct 30, 2025, 07:11 PM UTC
Duration
1h 11m
Affected: Current status by service (API)Current status by service (API)
Timeline · 2 updates
  1. investigating Oct 30, 2025, 06:00 PM UTC

    We are investigating an issue with delayed notifications. Onboarding notifications, account update alerts, and other notifications are affected.

  2. resolved Oct 30, 2025, 07:11 PM UTC

    The underlying issue has been fixed. Any notifications generated between 2025-10-29 19:00 UTC and 2025-10-30 19:15 UTC may not be delivered. If new workers were invited during this time period, you may need to re-send onboarding emails to these workers. Please feel free to reach out to our customer support team if you have any further questions or concerns. Thank you for your patience!

Read the full incident report →