Is Seesaw Down Right Now? Check if there is a current outage ongoing.

We've identified an issue with getting a QR code for a student post from the [...] menu on student work. A fix has been identified and is in progress. Student login QR codes are unaffected.

A regular maintenance operation to remove old/stale data impacted image fetch abilities within the Seesaw app. While app functionality was not impacted, some images might not have loaded in the app for about ~30mins.

A regular maintenance operation to remove old/stale data impacted image fetch abilities within the Seesaw app. While app functionality was not impacted, some images might not have loaded in the app for about ~30mins.

This incident has been resolved

We discovered a ClassLink-side API connection issue. This prevents the nightly sync from completing for some ClassLink districts. We are in active communication with the ClassLink Team who is investigating the issue.

We had an issue where families could not attach files in Messages. This issue is now resolved on Web as well as the latest iOS and Android releases (requires updating to the latest release 10.64.0).

This issue has been resolved.

We are currently investigating an issue where class creations via CSV are not working.

This issue has been resolved with our latest iOS App Release (10.51.1).

We have submitted a fix for our iOS app, currently pending Apple approval. In the meantime, we have identified workarounds for the camera roll issue and communicated them to customers who reached out.

The engineering team is investigating reports that photos from the camera roll are not displaying in Creative Tools. The root cause has been identified, and a fix is in progress.

All posts and messages are displaying correctly for UK users (Note: Some posts may be pending approval in the Notifications tab). Team has a mitigation in place and is working with our cloud service provider on a path forward.

UK user-facing issue is resolved: All posts and messages are displaying correctly for UK users (Note: Some posts may be pending approval in the Notifications tab). Team has a mitigation in place and is working with our cloud service provider on a path forward.

We have confirmed that with the mitigation in place, all posts and messages are now displaying correctly for UK users — all data is safe and no posts or messages data is lost. (Note: Some posts may be pending approval in the Notifications tab.) We have identified the root cause of the issue as maintenance operations by our cloud service provider and are working with them on a permanent solution.

We have a temporary mitigation in place for the issue impacting the UK so that Seesaw is now displaying posts and messages correctly for UK users. Users previously impacted by missing posts and messages should be able to see their posts in their Journal (note: some posts may be pending approval in Notifications) and messages will be showing up in the Inbox — no posts or messages data is lost. We are continuing to investigate the root cause and additional improvements and will continue to update with more information.

We are currently investigating some reports of posts and messages that are missing for users in the UK. We will update as soon as we have more information.

A small group of our customers in the UK region experienced slowness while loading Seesaw today. The root cause was mitigated, and the engineering team is continuing to assess and fix the root cause. The issue lasted approximately 45 minutes, while the servers handling traffic from UK customers were refreshed. We don't expect any lasting impact or data loss from the slowness today. We will continue to monitor and watch the performance across all our regions worldwide.

The issue is resolved and LTI (LMS integrations - Canvas, Schoology) should now be accessible again.

We have identified an issue impacting access to LTI (LMS integrations - Canvas, Schoology) starting Mon 8/19 ~11:30am PT. Teachers and students can still access all Seesaw features through the regular app experience outside of LTI. We are pushing a fix for the issue today.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We’ve identified an issue for some students responding to activities and saving their work. We are working on a fix.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Between 1:05pm - 2:31pm pacific, Seesaw experienced an elevated level of API errors. We've identified that up to 2,600 schools and districts who are in the 'Seesaw Instruction & Insights' tier received a 500 error when accessing our site. We are working to restore their access.

We are currently investigating an issue where a small percentage of users are experiencing 500 errors across the site.

Due to an infrastructure outage, some users briefly saw an empty messages inbox in Seesaw. Some Seesaw users experienced this issue for brief periods of time between May 8 and May 14th, and we have since fixed the underlying issue. If you tried to send messages during this time, we recommend re-sending your message — you should be able to view and send messages as normal. We will continue to monitor and will also reach out to users who were impacted by this issue with further information.

We are aware of reports of missing messages from the Seesaw application that impacted some users on May 8, 13, 14 for brief periods of time, approximately over a total period of 6hrs spread over those 3 days. We have identified the root cause and are working on impact metrics to recover any messages that are missing from / sent during the impacted time periods.

Apple has fixed an issue in iOS 17.4 that was causing occasional crashes when creating complex drawings and using the eraser in the Creative Canvas. iPad and iPhone users on iOS 17.0 - 17.3 are encouraged to upgrade to iOS 17.4.

Some iOS 17+ users (iPad and iPhone) have reported occasional crashes when creating complex drawings and using the eraser in the Creative Canvas. This is due to a change in Apple's iOS operating system, and we are currently working with Apple to resolve this issue.

This incident has been resolved.

We've confirmed that the issue has resolved itself. An upstream provider had an outage from 2/21/24 13:57 PT to 2/21/24 19:01 PT. Our logs show normal activity resumed by 19:15 PT, and we've made an improvement to prevent this issue from occurring if the provider were to have an issue again.

We've confirmed that the issue has resolved itself. An upstream provider had an outage from 2/21/24 13:57 PT to 2/21/24 19:01 PT. Our logs show normal activity resumed by 19:15 PT, and we've made an improvement to prevent this issue from occurring if the provider were to have an issue again.

A small set of users are likely not receiving real-time updates in Messaging. The team is looking into this, and the current workaround is to refresh to receive new messages. Thank you for your patience.

All services are operational, and back to healthy state.

The new change has been rolled back and we continue to monitor the reliability of our services.

We are continuing to work on a fix for this issue.

We're experiencing an elevated level of API errors and are currently looking into the issue. This might impact site load performance.

We have confirmed that issue is now resolved and reliabilities are back up to 100% since 2:45pm Pacific, 2023-12-12

A fix has been implemented and we are monitoring the results.

We are currently aware of an issue communicating with our SMS Gateway provider, resulting in potentially missed SMS notifications for new posts. The team is investigating the root cause, and expecting a fix by Dec 12, 2023 (noon, pacific time)

Seesaw's marketing website (web.seeaw.me, seesaw.com) experienced loading issues from 8:13AM PST - 9:30AM PST.

Some users may have experienced issues with the site/app loading (500 errors) between 11:30-11:45am PT. The issue is now resolved.

The issue is resolved and the Standards & Curriculum Alignments Tool should be loading successfully now.

We are seeing improvement with the Standards & Curriculum Alignments Tool site loading issue. In some cases, refreshing or reloading the page will resolve the issue.

We are continuing to work on a fix for the Standards & Curriculum Alignments Tool site loading issue. In some cases, refreshing or reloading the page will resolve the issue.

Some customers are experiencing loading issues with the Standards & Curriculum Alignments search tool. In some cases, refreshing or reloading the page can work. We are resolving the issue with our third-party web provider and will provide updates as soon as we have more information.

All historical backup of notifications have been cleared and delivered. We consider this incident to be resolved, and continue to monitor the reliability of our services.

We are continuing to monitor for any further issues.

A fix is in place and all the notifications from earlier today should have been delivered at this time. We are continuing to monitor the stability of our fix and reliability.

We have identified the root cause of the issue. New notifications are no longer delayed, and we are actively working on clearing out the backup in the older notifications

We are currently experiencing delays in outbound email and SMS notifications for users, since 1:30pm UTC / 930am Eastern / 630am Pacific. Our team is currently investigating the root cause. More updates will be posted shortly.

AWS has stated the majority of its networking latencies and errors have been resolved. Our error monitoring also corroborates their updates. We are resolving this issue but will continue to monitor as well.

AWS has reported that their actively working on resolving networking latencies and errors. They anticipate this to be fully resolved in the next 60-90 minutes. We will continue to monitor as well.

We are investigating site degradation (slowness and connection issues) that have been impacting some users on the site since ~11am Pacific time. This is potentially tied to a degradation in network performance in our regional data center in US-WEST2 that AWS is actively investigating and fixing forward.

Site connection / slowness issue resolved. There has not been any known customer impact since ~7am PT today.

The slowness/connection issues are resolved and we are investigating the root cause of the site degradation that impacted some users between ~5am PT to ~7am PT.

We are investigating site degradation (slowness and connection issues) that have been impacting some users on the site since ~5am PT.

Family invites should now send correctly via SMS. If you previously sent an invite via SMS that was not delivered, you can re-send the invite now (via SMS or any method) or remove and re-invite so that the family invite properly sends.

A fix for sending family invites via SMS text message has been implemented. Family invites should now send correctly via SMS. We are monitoring to ensure the fix.

Currently we are unable to send family invites via SMS text message to new families without existing Seesaw accounts. As a workaround, teachers can invite families using email, QR code printouts, or invite link. We also recommend re-sending an invite via one of the other methods if you recently tried to invite families via SMS.

Issue resolved. There has not been any known customer impact since ~11:15am PT today.

We are continuing to investigate the site degradation (slowness and connection issues) that impacted the site between ~10:50am PT - 11:15am PT. There has not been any known customer impact since ~11:15am PT today.

We are investigating site degradation (slowness and connection issues) that impacted the site between ~10:50am PT - 11:15am PT. The slowness is temporarily resolved and we are investigating the root cause.

We have resolved the issue impacting Google Sign In to the Seesaw website.

We are currently investigating this issue.

This incident is resolved.

We are currently investigating this issue. Users can continue to sign into Seesaw via Google SSO on the mobile applications with no issues.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

Videos that are recorded on the Web can now be played back on iOS devices. A fix for video playback for videos on recorded on Android is in review.

We identified an issue where users cannot playback videos that were recorded on the web/Android on iOS devices.

The issue has been resolved and customers have been reporting that things are now working as expected with CSV Rostering.

A fix has been implemented and we are monitoring the results to ensure there are no more CSV Rostering 504 errors coming through.

The issue causing the CSV Rostering 504 errors has been identified. A fix is being worked on.

We are currently investigating an issue where some admins get a 504 error when attempting to upload rosters via the CSV rostering method.

The issue with our downstream email service provider is resolved and all delayed emails have been sent.

The issue with our downstream email service provider is resolved and we are currently sending email notifications. We will update again when all delayed emails have been sent.

We have identified an issue where email notifications are delayed due to an issue with our downstream email service provider. All email notifications will be sent, but users may experience a delay in email delivery. We update again when the delay is resolved.

This incident has been resolved.

[Resolved] At approximately 1:30PM Pacific, our downstream service provider resolved the issue on their end. Real-time Messaging updates are now fully operational. Please email help@seesaw.me if you're experiencing any issues.

We are currently investigating issues with real-time Messaging updates as there is an issue with a downstream service provider.

This incident has been resolved. Read a letter from our CEO/co-founder here: https://web.seesaw.me/blog/credential-stuffing-incident

**9/14 Incident Report** *Summary of the issue:* - Late on September 13, isolated Seesaw users were subjected to a coordinated “credential stuffing” attack. These individual compromised accounts were then used to send a message with a link to an inappropriate image. - *Seesaw was not compromised.* The attack was a result of a coordinated attempt to guess individual user account passwords, sometimes known as a 'credential stuffing' attack. In a credential stuffing attack, publicly available compromised emails/passwords that are re-used across services are used to gain access to individual user accounts. - *Seesaw is safe to use.* Within the first few hours of learning about the attack, we took swift action. We completely disabled messaging, blocked the attacker, made sure the image was removed and no longer accessible, and proactively alerted impacted users as well as our wider community. The incident has been resolved. - *Less than 0.5%* of Seesaw users were affected. Seesaw blocked the attack swiftly to prevent the message from being distributed widely. - We have no evidence to suggest the attacker performed additional actions or accessed data in Seesaw beyond logging in and sending a message from compromised accounts. We are conducting a thorough investigation and will share updates if any new information is discovered. *What Happened?* - A message containing a link to an inappropriate image was sent from individual compromised Seesaw user accounts. - *Seesaw was not compromised.* The attack was a result of a coordinated attempt to guess individual user account passwords, sometimes known as a 'credential stuffing' attack. In a credential stuffing attack, publicly available compromised emails/passwords that are re-used across services are used to gain access to individual user accounts. - *Less than 0.5%* of Seesaw users were affected. Seesaw blocked the attack swiftly to prevent the message from being distributed widely. - We have no evidence to suggest that the attacker performed additional actions in compromised Seesaw user accounts beyond logging in and sending a message. * How Seesaw Immediately Responded* - Ensuring the safety and privacy of our teachers, students, and families was our top priority. - Within the first few hours of learning about the attack, we took action. Seesaw’s swift response to this attack included the following steps: - As we resolved the issue, we completely disabled our messaging feature to ensure no one else saw the inappropriate message. As of September 15, messaging has been fully restored. - We successfully removed the inappropriate message from all accounts and coordinated with Bit.ly and AWS to ensure that the inappropriate image is no longer accessible. - We proactively reset the passwords of all accounts we know to have been compromised and notified all impacted users. - Throughout the day, we released multiple public statements, publicly provided status updates on our website: https://status.seesaw.me/, coordinated with security officials, and notified all customers. - We adjusted our detection and blocking rules to ensure similar attacks are prevented in the future. - In addition to the above, we have taken a number of mitigation steps to prevent a similar attack in the future through refinements to Seesaw’s rate limiting, alerting, blocking, content detection, and login systems. - We'll be reviewing other steps we can take in the coming days to help users secure their accounts further. **Here’s What This Means for Your Users** *Is Seesaw safe to use?* Seesaw is safe to use. The safety and privacy of our teachers, students, and families is our number one priority and we take it extremely seriously. Seesaw was not compromised, and the incident has been resolved. *Is Seesaw Messages secure and safe to use?* Yes, this incident occurred as a result of unauthorized access to Seesaw accounts. Seesaw, including the messaging feature, was not compromised. *How do I know if my account was compromised?* If your account was compromised, the Seesaw team sent you an email. We proactively reset the passwords of all accounts we know to have been compromised. We have also adjusted our detection and blocking rules to ensure similar attacks are prevented in the future. *Why was messaging turned off?* As soon as we identified this attack was taking place, our first priority was to secure the safety of teachers, students, and families. While we resolved the issue, we disabled the messaging feature to prevent the message from being distributed widely. Before turning messaging back on, we took action to block the attacker’s access and made sure the image was removed and no longer accessible. *How do I ensure that the image has been removed?* We have removed the inappropriate image link from all messages and taken many other actions to ensure it is inaccessible (details can be found here: http://status.seesaw.me). In a few instances, if the message was already loaded in a web browser or one of our apps, it may have been cached on devices. To completely remove the image, users can follow these steps: - We recommend all users *refresh their web browsers and restart their mobile app*. - On mobile, we recommend all users update devices to the latest version (version 8.1.2) or re-launch Seesaw by completely closing out and re-opening the Seesaw app. (Here are instructions to close apps for iOS and Android devices). - iOS: https://support.apple.com/en-us/HT201330 - Android: https://support.google.com/android/answer/9079646?hl=en#zippy=%2Cclose-apps *How can I take extra precaution and reset my password?* Any user can always reset their password at https://app.seesaw.me/#/reset_password. *Where can I get more information or support?* If you have any questions or concerns, please reach out to us here: https://help.seesaw.me/hc/en-us/requests/new. Thank you for your patience while our team worked round the clock to get these additional security measures in place.

Messages is ON for all customers. We are continuing to monitor.

We are turning Messages back ON for all customers starting at 7 am PT and continuing to monitor.

We have removed the inappropriate image link from all messages and taken many other actions to ensure it is inaccessible. However, in a few instances, if the message was already loaded in a web browser or one of our apps, the message may have been cached on your device. To ensure that no one has access to the inappropriate message, we recommend all everyone *refresh their web browsers and refresh their mobile apps*. On mobile, you can update your device to the latest app version (version 8.1.2, released today) and re-launch Seesaw OR close and re-open the Seesaw app. Here are instructions to close apps on mobile devices: - iOS: https://support.apple.com/en-us/HT201330 - Android: https://support.google.com/android/answer/9079646?hl=en#zippy=%2Cclose-apps We are also emailing all affected users with these instructions as well. We plan to re-enable Messages tomorrow after overnight monitoring.

*What Happened* - Late on September 13th, Seesaw was subjected to a coordinated “credential stuffing” attack. - Seesaw was not compromised; however, isolated individual user accounts were compromised and used to send an inappropriate message. - Widely available compromised emails/passwords that were reused across services were used to gain unauthorized access to Seesaw accounts. - We have no evidence to suggest this attacker performed additional actions or accessed data in Seesaw beyond logging in and sending a message from these compromised accounts. *What Data May Have Been Accessed* - An isolated number of Seesaw user accounts were compromised in this attack, and only a portion of those were able to send the inappropriate message before the attack was blocked. - We have no evidence that the attacker performed additional actions in Seesaw beyond logging in and sending a message from these compromised accounts. *What We Have Done* - As soon as we identified this attack was taking place, we took action to block the attacker’s access to these accounts. - We completely disabled the messaging feature to ensure no one else saw the inappropriate message as we worked to resolve the issue. - We removed the inappropriate message from accounts where it was sent. - We proactively reset the passwords of all accounts we know to have been compromised, and have notified impacted users already. - We adjusted our detection and blocking rules to ensure similar attacks are prevented in the future. - We have coordinated with Bit.ly to ensure that the link to the inappropriate image is no longer accessible in any email notifications that may have been sent. *What You Should Do* - Maintaining the security of Seesaw accounts is paramount. While we work to proactively prevent these kinds of attacks, you can help by making sure that all user accounts use unique passwords that are not used in other services. - If you are an administrator, you can let your parents and teachers know: - Seesaw was not compromised; however, isolated individual user accounts were compromised and used to send an inappropriate message. - This incident was the result of an outside actor; the messages were not created by the sender. - If your account was compromised, your password was reset and you have already received an email notifying you of this. - It is essential that you always use best practices to ensure your password is secure: https://www.cisa.gov/uscert/ncas/current-activity/2018/03/27/Creating-and-Managing-Strong-Passwords - Seesaw takes protecting your security and privacy seriously and we have a number of measures in place to protect the integrity of your information. You can learn more here: https://help.seesaw.me/hc/en-us/articles/203258429-How-Seesaw-keeps-student-data-safe * Next Steps* - We will re-enable messaging when we’ve confirmed that the inappropriate message is no longer accessible from our servers. - We are actively monitoring the situation and will be putting additional mitigation measures in place to prevent this and future attacks of this type. - We will be scanning databases of known compromised passwords and resetting the passwords of users who may have re-used passwords as a proactive additional security measure (and preventing use of these passwords in the future). - Please always use a unique password for accessing Seesaw and any other online account or service. Never reuse an old password or use the same password. Consider using a password manager for added security. - We will continue providing updates here.

We believe there may be some caching cases where the previously sent inappropriate images may still be accessible to some customers. At this time we do not believe there are any new messages with the inappropriate image being sent. We have turned the Messaging feature off while we investigate the issue further. We are continuing to monitor and investigate the situation and will post a more detailed update shortly.

We have reset passwords for affected individuals and confirmed that links are no longer accessible. At this point, we have re-enabled the Messages feature. We are continuing to monitor and investigate the situation and will post a more detailed update shortly.

As of 9:15am PT: Users who received the link via an email notification will no longer be able to access the link. As of 10:15am PT: We have reset passwords for and sent password reset emails to all affected accounts.

It was brought to our attention that a link to an inappropriate image was being shared via the Messages feature. It appears that specific accounts were compromised by an outside actor. We take this incident extremely seriously. We’ve turned OFF Messages temporarily for all users while we investigate, to prevent further spread of this image from being sent or seen by any Seesaw users. - We have removed this inappropriate link from any messages that reference it - We are resetting the passwords of any users who had their account compromised - We have taken measures to prevent additional accounts from being compromised - Any user can always reset their password at: https://app.seesaw.me/#/reset_password - Our team continues to monitor and investigate the situation If you have any questions or concerns, please reach out to us at https://help.seesaw.me/hc/en-us/requests/new. We will continue to provide updates on https://status.seesaw.me/ as we investigate and manage the situation. —The Seesaw Team

The issue has been identified and a fix is being implemented.

[Investigation] We have turned off our messaging tool temporarily while we investigate an issue.

This issue has been resolved.

The issue has been identified and a fix is being implemented.

We are investigating an issue where Clever and Classlink SSO results in an endless loop on the web version of Seesaw. Clever SSO on iOS is unaffected.

This issue has been fully resolved and all impacted customers should now see their previous conversations in the new messaging experience.

We have re-migrated the conversations for all impacted schools and are monitoring to make sure everything is fixed.

We've fixed the root cause so we expect this issue should not impact any customers moving forward. We are now re-migrating the conversations for all previously impacted schools.

We’re investigating an issue where some schools are reporting that they are missing their previous conversations after turning on messages. We’ve identified the root cause (a recent infrastructure upgrade) and will be fixing this ASAP, then remigrating conversations for all impacted customers. For customers that experience this, none of their conversation data is missing or lost, and we will be properly migrating previous conversations over as soon as possible. Customers can continue using messages without any impact to previous conversations.

This issue has been resolved and email notifications are being delivered normally.

We are seeing signs of recovery from our downstream email provider and are working through the delayed emails. We expect all delayed email notifications to be correctly sent in the next hour or earlier.

We have identified an issue where some email notifications are delayed due to an issue with our downstream email service provider. All email notifications will be sent, but users may experience a delay in email delivery. You can view the status of our email provider here: https://status.mailgun.com/

This issue has been resolved and email notifications are being delivered normally.

We have identified an issue where some email notifications are delayed due to an issue with our downstream email service provider. All email notifications will be sent, but users may experience a delay in email delivery.

We’ve processed all backed up notifications and the notifications delay issue should now be fully resolved for all customers.

We’ve increased the speed of the process and now expect the delayed notifications issue to clear up for customers in under 3 hrs (or earlier). We’ll continue to monitor and will update again when the issue is fully resolved for all customers.

We made a few changes to address the issue and are monitoring the improvement. We are working through the backed up notifications which takes some time, so customers may not see improvement immediately. We expect the issue to clear up in the next ~6 hrs (or earlier) for customers. In the meantime, we continue to recommend refreshing to view new messages.

We've been investigating an issue where new messages notifications are delayed and not showing up in real-time. In the meantime, customers will need to refresh their browser/app to view new messages. Note that this issue impacts the new Messaging product only, Legacy Inbox & Announcements is unaffected.

This issue has been resolved. All announcement attachments should open normally on iOS.

We have made a fix so all new school announcements can be opened in the iOS app. We are now working to clean up previously sent announcements so these announcements can be opened on iOS.

We have identified an issue where some teachers, students and families will see an “Item Not Found” error when trying to open the expanded post view of school announcements message attachments on iOS devices. This issue is affecting new school announcement attachments with images, videos, links or PDFs. The issue is isolated to iOS, there are no issues on Android or web. We are actively working on a fix.

All teachers connections to classes should be fixed. Please email help@seesaw.me if that is not the case.

A fix has been implemented for the affected users so they have been re-added to appropriate classes - we are monitoring / verifying.

Affected accounts have been identified and we are working to restore their association with the right classes.

We are investigating some teacher reports of missing classes. We have identified root cause and are working on a resolution.

This incident has been resolved.

Seesaw error rate is back down to normal levels. AWS has identified the root cause and is seeing signs of recovery. https://status.aws.amazon.com/. We are continuing to monitor.

AWS continues to work on remediating the issue. Seesaw error rate is steady at 0.4%. AWS updates available here: https://status.aws.amazon.com/.

0.4% of requests across the site are getting an error in response. We are continuing to monitor the issue. Amazon Web Services is experiencing a significant outage in US East. They have identified the root cause and are actively working on remediation. Updates here: https://status.aws.amazon.com/

We are currently investigating an issue where a small percentage of users are experiencing 400 errors across the site.

The Roster Sync dashboard and syncing for ClassLink districts are now operational.

At 5:00 am PT we discovered a ClassLink-side API issue that is preventing loading of the Roster Sync dashboard and syncing for ClassLink districts. We've reached out to the ClassLink Team for investigation.

The issue impacting manual Clever/ClassLink syncs should now be resolved and manual syncs should now complete successfully.

We’re investigating an issue where manual Clever/ClassLink roster syncs are failing (displaying “unexpected error” in the sync dashboard) when the sync involves adding new students due to a recent update. We are investigating the issue and will patch a fix as soon as we can.

This issue should now be resolved — the issue was the Ada Zendesk Support Chatbot, which we have now turned off. The Activity Library should now be fully functional.

We're currently investigating an issue where the Seesaw Activity Library is experiencing an outage, impacting My Library, Community Library, School & District Library, and Seesaw Lessons Library. We will update on the issue when we have more information.

The issue with downloads, uploads, messaging, and other time-based actions failing to complete due to an AWS issue should now be resolved.

Amazon is continuing to investigate this issue. Information and updates on AWS status page: https://status.aws.amazon.com/

Starting at around 11am PT, customers are sporadically seeing downloads, uploads, messaging, and other time-based actions fail to complete due to an AWS issue. We are investigating and will update when we have more information. Information on AWS status page: https://status.aws.amazon.com/

ClassLink notified us that our original supported API is working again. We tested and confirmed, and have switched back, so syncs from now on will run using the original supported API as before. Please reach out to ClassLink and Seesaw support if you experience any issues with your sync as a result of the API switches.

We have patched a change to use a newer version of the ClassLink API as a temporary workaround while we wait for the ClassLink team to fix the API we are currently using. Roster Sync dashboards for ClassLink districts should now load and be able to run syncs (note that you may need to hard refresh). We have also unpaused district syncs and run all nightly syncs from 8/15 using the new ClassLink API. As a reminder — Because this is a new API there may be some unpredictable issues that come up, which customers should report to ClassLink if observed. If customers are able to wait, we recommend waiting to run a manual sync until after ClassLink has fixed our supported API and we are able to revert back.

ClassLink has identified that the issue is with the version of the ClassLink API we are currently using. We are patching a change to use a newer version of the ClassLink API as a temporary workaround while we wait for the ClassLink team to fix the API we are currently using. We will also unpause and rerun all nightly syncs from 8/15 using the new ClassLink API. Because this is a new API there may be some unpredictable issues that come up, which customers should report to ClassLink if observed. If customers are able to wait, we recommend waiting to run a manual sync until after ClassLink has fixed our supported API and we are able to revert back.

We have preemptively paused all ClassLink district syncs while this issue is being investigated.

At 12:17pm PT we discovered a ClassLink-side API connection issue. This prevents the loading of our Roster Sync dashboard and prevents syncing for ClassLink districts. We are in active communication with the ClassLink Team who is investigating the issue.

Between 1:00 to 1:05pm PT, users may have experienced intermittent 500 errors and slowness using Seesaw. This issue has now been resolved.

Users were seeing 503 errors when loading images or downloading data in Seesaw from 11:53am - 12:03pm PT. The issue should now be resolved.

Seesaw 7.6.9 is now available on iOS and Android. Please install this update to resolve this issue.

Unfortunately, in the latest iOS and Android release 7.6.8, we introduced a bug where students and teachers will see a “Cannot Save Drawing” error message if they try to edit a post or respond to an activity with a video on the page. We’ve fixed the issue and submitted new versions of the iOS and Android apps to the stores, which we hope will be available before the weekend is over.

This incident has been resolved.

We are currently investigating a low number of errors (0.0002% of requests) across the site.

This incident has been resolved.

We're currently investigating slowness loading the site and periodic 500 errors.

This incident has been resolved.

This issue has been resolved.

We’re seeing increased slowness loading the site and occasional 500 errors. We are currently investigating.