Is Seesaw Down?

No — Seesaw is up

Reachable from all 8 checked regions

Average response time: 678ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://status.seesaw.me

Seesaw uptime

100%

Last 7 days

99.86%

Last 30 days

99.86%

Last 90 days

553ms

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

17-day clean streak

Aug 23 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.

iad

475ms

DNS 0ms TCP 1ms TLS 10ms TTFB 462ms

jnb

1320ms

DNS 0ms TCP 0ms TLS 10ms TTFB 1308ms

lax

386ms

DNS 0ms TCP 1ms TLS 12ms TTFB 369ms

lhr

543ms

DNS 0ms TCP 2ms TLS 13ms TTFB 527ms

nrt

1184ms

DNS 0ms TCP 1ms TLS 29ms TTFB 1171ms

ord

239ms

DNS 0ms TCP 2ms TLS 12ms TTFB 223ms

sin

900ms

DNS 1ms TCP 1ms TLS 18ms TTFB 880ms

sjc

378ms

DNS 0ms TCP 1ms TLS 13ms TTFB 363ms

What Seesaw does

Seesaw is a classroom platform where students post work into a digital portfolio and teachers assign activities and send messages home to families. It is used heavily in primary education, often across a whole district, and frequently on shared school devices. Lessons are built around it during the school day, so an outage interrupts teaching rather than merely delaying it.

What an outage looks like

The app or web client fails to load, or students sign in and see an empty journal. Uploads are the common failure: a photo, drawing or recording appears to submit but never lands in the teacher's feed. Class codes and QR sign-in can fail while existing sessions keep working, which makes a classroom of new logins fail while the teacher's own screen looks fine.

What to do about it

Check status.seesaw.me, bearing in mind it reports a single overall component and will not tell you whether uploads, sign-in or messaging specifically are affected. Ask students to keep work on the device rather than resubmitting repeatedly, since duplicate posts all appear at once when service returns. For urgent family communication, use the school's own email or phone system instead.

Is it down for everyone, or just you?

If this page says Seesaw 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

Seesaw outage FAQ

Is Seesaw down for everyone or just my classroom?

Seesaw's status page reports a single overall component, so it cannot distinguish a regional problem from a full outage or tell you which feature is affected. School networks are a common confounder, since content filtering and bandwidth limits produce failures that look identical to an outage. Measurement from outside the school network is the practical way to separate the two.

Did my students lose the work they submitted?

Work that never reached Seesaw is not saved on its side, so treat an upload that did not appear in the teacher feed as not submitted. Whether a draft survives on the device depends on the app and how the session ended, which Seesaw does not document on its status page. Ask students not to close the app or sign out until posts have visibly landed.

Students cannot sign in but I am still logged in. Why?

An existing session and a new sign-in take different paths, so a teacher already authenticated can keep working while class codes and QR sign-in fail for a room of students. That pattern is common on shared devices at the start of a lesson. It is not evidence the service is healthy, so check the status page rather than judging from your own screen.

Does a Seesaw outage stop family messages?

Seesaw reports one component covering the whole service, so messaging is not tracked separately and the page cannot confirm whether it is specifically affected. Assume a message you cannot see delivered has not been sent. For anything a family needs the same day, use the school office rather than a message queued in an app that is currently failing.

How long do Seesaw outages usually last?

Seesaw does not publish target resolution times, and a single-component status page gives no basis for estimating from past incidents by feature. Its incident history on the status page is the best available guide. Planning a paper fallback for the rest of the lesson is more reliable than waiting on an estimate the vendor has not given.

How we measure this

We request Seesaw'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 Seesaw 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 Seesaw 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