Remind Outage History

Remind is up right now

Remind had 5 outages in the last 2 years totaling 49h 37m of downtime — averaging 0.2 incidents per month.

There were 5 Remind outages since May 27, 2025 totaling 49h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.remind.com

Notice June 12, 2025

Errors with Translations

Detected by Pingoru
Jun 12, 2025, 06:41 PM UTC
Resolved
Jun 14, 2025, 04:47 AM UTC
Duration
1d 10h
Affected: Website
Timeline · 3 updates
  1. investigating Jun 12, 2025, 06:41 PM UTC

    Our translations provider is currently experience issues that lead to errors when translating content for messages in Remind. We are waiting for updates from our translations provider and will post an update when we learn more.

  2. monitoring Jun 12, 2025, 07:08 PM UTC

    It looks like translations are working correctly now. We will continue monitoring.

  3. resolved Jun 14, 2025, 04:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 30, 2025

Remind Message Delivery Errors

Detected by Pingoru
May 30, 2025, 05:32 PM UTC
Resolved
May 30, 2025, 06:00 PM UTC
Duration
28m
Affected: Text Messages (SMS)
Timeline · 2 updates
  1. investigating May 30, 2025, 05:32 PM UTC

    We are investigating an issue impacting the delivery of text message sent by verified Remind organizations. Messages sent by Remind app or email are still delivering properly. We will provide an update shortly. We apologize for the inconvenience caused!

  2. resolved May 30, 2025, 06:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 27, 2025

Remind Errors

Detected by Pingoru
May 27, 2025, 03:45 PM UTC
Resolved
May 27, 2025, 07:16 PM UTC
Duration
3h 31m
Affected: Phone Calls
Timeline · 3 updates
  1. investigating May 27, 2025, 03:45 PM UTC

    We are investigating reports that some users are unable to make phone calls. We will provide an update shortly. We apologize for the inconvenience caused!

  2. identified May 27, 2025, 05:09 PM UTC

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

  3. resolved May 27, 2025, 07:16 PM UTC

    This incident has been resolved.

Read the full incident report →