Is Seesaw down in the US?
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-05 18:18 UTC: We have released a fix to the iOS App Store and rollout has begun. Please download the latest release (10.150.1).
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 passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Seesaw at Nov 6, 2026, 6:01 PM UTC.
Over the last 24 hours we completed 248 checks from Ashburn and San Jose and 248 answered cleanly, 100.00% availability.
Of the 2 other regions we check Seesaw from, all 2 read checks passing right now.
Email me when Seesaw reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 6, 2026, 6:01 PM UTC.
Seesaw from Ashburn and San Jose over the last 30 days
Over the last 30 days, Seesaw answered our Ashburn probe in 2,769 ms on average, and 1 check in 20 took longer than 4,366 ms.
Over the last 30 days, Seesaw answered our San Jose probe in 3,718 ms on average, and 1 check in 20 took longer than 5,291 ms.
Ranked by average response time across the 4 cities we check Seesaw from, Ashburn 1st, San Jose 3rd; Ashburn was fastest at 2,769 ms and Tokyo slowest at 5,372 ms.
From Ashburn and San Jose we ran 1,017 checks of Seesaw in 5 days, and 1,017 answered cleanly: 100.00% availability.
Every one of those days was clean: not one failed check.
In Ashburn local time (EST), Seesaw was slowest around 6 PM, at 3,367 ms on average over the last 14 days, and quickest around 11 PM, at 2,227 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Fri, Nov 6 | 181 | 100.00% | 3,332 ms |
| Thu, Nov 5 | 246 | 100.00% | 3,103 ms |
| Wed, Nov 4 | 248 | 100.00% | 3,005 ms |
| Tue, Nov 3 | 241 | 100.00% | 3,208 ms |
| Mon, Nov 2 | 101 | 100.00% | 3,402 ms |
Seesaw outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Seesaw outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Seesaw from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 94 checks |
| Tokyo | Checks passing | 100.00% of 57 checks |
Other countries we check Seesaw from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Seesaw's public endpoints. They are not user reports, and they are not Seesaw's own status page.
See Seesaw's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Seesaw has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
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 serversRun 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