Skip to content

Outage tracker / Seesaw

Is Seesaw down?

Short linkrlup.io/down/seesaw

I'm having a problem

Vendor reports an incidentWhat Seesaw reports

Seesaw reports an incident on its status page: Seesaw iOS App failing to load with latest release.

Impact: major. Since 2026-11-04 20:19 UTC.

Latest update, 2026-11-04 21:35 UTC: The issue has been identified and a fix is currently being implemented and testing underway

Seesaw's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 4 minutes ago

Our checks of Seesaw pass from all 4 regions we check.

As of Nov 5, 2026, 3:06 PM UTC, RealUptime's checks of Seesaw passed in all 4 regions that returned a reading.

Front-door checks

our check readinglive · checked Nov 5, 2026, 3:06 PM UTC
US-East1713 msChecks passing
US-West4299 msChecks passing
Europe3707 msChecks passing
Asia-Pacific5254 msChecks passing
their status pagetheir claim, not our reading

Seesaw reports: Partial outage (“Partial System Outage”)

from Seesaw's own status page, checked Nov 5, 2026, 1:57 PM UTC

Seesaw reports an active incident: Seesaw iOS App failing to load with latest release (partial outage, since Nov 4, 2026, 8:19 PM UTC)

Seesaw's status page reports Partial System Outage. Our checks of Seesaw currently pass with normal latency. Our checks currently pass from all 4 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

Seesaw's own component breakdown, as they publish it

  • SeesawPartial outage

These are Seesaw's components, named and scored by Seesaw. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Seesaw's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Seesaw response time, by region

US-East
3.8sp95 · latest
10s5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 5.6s2026-11-03 UTC: p95 4.2s2026-11-04 UTC: p95 4.2s2026-11-05 UTC: p95 3.8s
Oct 7Oct 21Nov 5
US-West
4.9sp95 · latest
10s5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 4.9s2026-11-03 UTC: p95 5.0s2026-11-04 UTC: p95 5.3s2026-11-05 UTC: p95 4.9s
Oct 7Oct 21Nov 5
Europe
3.8sp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 4.3s2026-11-03 UTC: p95 4.2s2026-11-04 UTC: p95 4.6s2026-11-05 UTC: p95 3.8s
Oct 7Oct 21Nov 5
Asia-Pacific
6.9sp95 · latest
20s10s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 10.2s2026-11-03 UTC: p95 6.8s2026-11-04 UTC: p95 7.1s2026-11-05 UTC: p95 6.9s
Oct 7Oct 21Nov 5

Check your own site while you wait on Seesaw

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Seesaw. It cannot diagnose Seesaw's own systems.

Email me when Seesaw reports an incident on its status page, and again when it reports it resolved.

Get an email when Seesaw reports an incident

Email me when Seesaw reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Seesaw's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1713msstatus code: 200checked: Nov 5, 2026, 3:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Seesaw normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 4299msstatus code: 200checked: Nov 5, 2026, 2:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Seesaw normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionSeesaw is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionSeesaw is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionSeesaw is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 3707msstatus code: 200checked: Nov 5, 2026, 3:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Seesaw normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionSeesaw is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 5254msstatus code: 200checked: Nov 5, 2026, 3:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Seesaw normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionSeesaw is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionSeesaw is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Seesaw, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Seesaw yet, which is not evidence that nothing is wrong.

Recent probe events

Seesaw iOS App failing to load with latest releasedeclared on their status page2026-11-04
Planned Downtime for Image Library, 1h 21mdeclared on their status page2026-05-08
Some images not loading in Seesaw, 8h 21mdeclared on their status page2026-02-10
Scheduled Messages Delayed, 1h 37mdeclared on their status page2026-01-28
Issues Uploading to Student Journals and Activities, 27mdeclared on their status page2026-01-13
AWS Outage Impacting Third-Party Authentication, 7h 57mdeclared on their status page2025-10-20
Push Notification Causing iOS Crash on 10.89, 32h 35mdeclared on their status page2025-08-14
Unable to use Share Post QR Code fuctionality, 1h 57mdeclared on their status page2025-06-10

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Seesaw since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Seesaw covering any window you pick, with our check readings and Seesaw's own claim at the time, side by side.

Full check history for Seesaw: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Seesaw uptime by RealUptime's checksLive, from this page's own readings.
[![Seesaw uptime by RealUptime's checks](https://realuptime.io/outages/seesaw/badge.svg?days=30)](https://realuptime.io/outages/seesaw)
<a href="https://realuptime.io/outages/seesaw"><img src="https://realuptime.io/outages/seesaw/badge.svg?days=30" alt="Seesaw uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Seesaw down?", https://realuptime.io/outages/seesaw. The readings change with every check, so give the date you read them.

What we check

primary
https://web.seesaw.me/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: web.seesaw.me

RealUptime is not affiliated with Seesaw; the name identifies what we checked, and nothing here speaks for Seesaw's own team. We send a single web request to Seesaw from 4 regions on our own schedule and time the response. We do not see inside Seesaw's systems, do not use an account or real transaction, and are not the same signal Seesaw's own team has access to. Treat this as one external data point, not a verdict. What we check for Seesaw is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Seesaw operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 1210 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

360LearningADPAIGAPRS.fiAXA