Skip to main content

Is Remind Down?

No — Remind is up

Reachable from all 8 checked regions

Average response time: 859ms

Last checked · checks run every 6 hours

Official status page: https://status.remind.com

Remind uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
801ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 25 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

25-day clean streak
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: 100.00% uptime, 16 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 31 checks
Sep 3: 100.00% uptime, 22 checks
Sep 4: 100.00% uptime, 32 checks
Sep 5: 100.00% uptime, 32 checks
Sep 6: 100.00% uptime, 28 checks
Sep 7: 100.00% uptime, 21 checks
Sep 8: 100.00% uptime, 38 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 8 checks
Aug 24 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
831ms
DNS 165ms TCP 88ms TLS 180ms TTFB 564ms
arn
936ms
DNS 107ms TCP 109ms TLS 222ms TTFB 606ms
bom
1600ms
DNS 143ms TCP 204ms TLS 407ms TTFB 992ms
cdg
901ms
DNS 45ms TCP 113ms TLS 228ms TTFB 674ms
dfw
306ms
DNS 37ms TCP 32ms TLS 67ms TTFB 209ms
ewr
258ms
DNS 150ms TCP 7ms TLS 17ms TTFB 236ms
syd
1774ms
DNS 305ms TCP 203ms TLS 409ms TTFB 1163ms
yyz
269ms
DNS 80ms TCP 17ms TLS 38ms TTFB 216ms

What Remind does

Remind is a school communication platform. Teachers and administrators send announcements and messages to students and parents, who receive them as text messages, push notifications, email or phone calls without exchanging personal numbers. Districts also use it for rostering and for reaching families who do not install the app, which is why the SMS path matters as much as it does.

What an outage looks like

Messages appear sent in Remind but never reach recipients, because Text Messages, Email Messages and Phone Calls are separate components from the Messaging system that composes them. The sender usually sees no error at all. The website and the iOS and Android apps are also reported separately, so staff can be locked out of one surface while another works.

What to do about it

Check status.remind.com and read the delivery component, not just the top banner. If Text Messages is the failing component, families who rely on SMS did not get the announcement even though it shows as sent, so use a second channel for anything time-critical. Rostering is its own component: missing classes after a failed sync is a separate incident from message delivery.

Is it down for everyone, or just you?

If this page says Remind is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Remind outage FAQ

I sent a Remind message. Did parents actually receive it?
A message showing as sent only means Remind accepted it. Text Messages (SMS), Email Messages and Phone Calls are reported as components separate from Messaging, so delivery can fail on one channel while composition succeeded. Check the specific delivery component for the channel most of your families use before assuming the announcement landed.
Is Remind down, or did my message just not send?
Check Messaging and the delivery components separately. A Messaging incident stops messages being composed or queued at all, which you would usually see as an error. A Text Messages or Email Messages incident is quieter: the send appears to succeed and the failure sits downstream, where the sender gets no signal.
Does the Remind app work when the website is down?
Sometimes. Website, iOS App and Android App are three separate components, so an incident can be scoped to one surface. Staff locked out of the web application can occasionally still send from a phone, and vice versa. Check the specific row rather than assuming all of Remind is unavailable.
Students are missing from my class. Is that a Remind outage?
Possibly. Rostering is its own component, covering the sync that populates classes from district systems. A rostering incident or a failed sync leaves classes incomplete while messaging works normally, so students silently do not receive announcements. That is a district IT issue to escalate rather than something a teacher can fix by re-adding students.
Do messages sent during an outage get delivered later?
Remind does not publish queueing or retry behaviour for messages during an incident, so do not assume delayed delivery. For anything time-critical, send again through another channel once the affected component recovers, and accept the risk of a duplicate as cheaper than a family never receiving the message at all.

How we measure this

  • We request Remind's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Remind publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Remind goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required