- Service Status
- /
- Seesaw
Is Seesaw Down?
- Seesaw's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 692 ms
Right now
The verdict is the worse of these two. How we decide
Seesaw's status page
status.seesaw.me · read · checked every 3 minutes
| Component | Status |
|---|---|
| Seesaw the service itself | Operational |
FlareWarden checks
seesaw.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 692 ms
- Checked
By region
- Ashburn reachable, 471 ms
- Dallas reachable, 547 ms
- Frankfurt reachable, 272 ms
- Johannesburg reachable, 2388 ms
- London reachable, 290 ms
- Los Angeles reachable, 495 ms
- Newark reachable, 411 ms
- São Paulo reachable, 665 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 0 ms | 1 ms | 10 ms | 464 ms |
| Dallas | 0 ms | 1 ms | 9 ms | 539 ms |
| Frankfurt | 0 ms | 2 ms | 13 ms | 263 ms |
| Johannesburg | 0 ms | 173 ms | 183 ms | 1770 ms |
| London | 0 ms | 5 ms | 12 ms | 279 ms |
| Los Angeles | 0 ms | 2 ms | 13 ms | 484 ms |
| Newark | 0 ms | 2 ms | 11 ms | 403 ms |
| São Paulo | 0 ms | 2 ms | 10 ms | 656 ms |
History
Incidents Seesaw reported
Since Oct 22, 27 days · from status.seesaw.me
- Incidents
- 1
- Major or critical
- 1
- Median to resolve
- 2d 5h
- lasted 2d 5h
Seesaw website availability
Measured by FlareWarden · seesaw.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 596ms
Last 30 days
82-day clean streakMeasured by FlareWarden's own checks of seesaw.com from multiple regions every 6 hours. Seesaw's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 82 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
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 17 cities across three regions to find out where it breaks.
Related services
Seesaw outage FAQ
Is Seesaw down for everyone or just my classroom?
Did my students lose the work they submitted?
Students cannot sign in but I am still logged in. Why?
Does a Seesaw outage stop family messages?
How long do Seesaw outages usually last?
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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Seesaw itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Seesaw goes down
We check Seesaw every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring