tag:status.samepage.io,2005:/historySamepage.io Status - Incident History2024-03-28T02:52:31ZSamepage.iotag:status.samepage.io,2005:Incident/108889152022-08-23T07:19:12Z2022-08-23T07:19:12ZUpgrade of systems<p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>07:19</var> UTC</small><br><strong>Resolved</strong> - The problem has been resolved. We are sorry for the inconvenience.</p><p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>06:00</var> UTC</small><br><strong>Investigating</strong> - Some non-ASCII characters don't work properly in page names. Investigating...</p><p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>05:43</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>05:43</var> UTC</small><br><strong>Investigating</strong> - Upgrade of one of internal systems caused Samepage to be unavailable. Users cannot login. WE expect the issue to be resolved within few minutes.</p>tag:status.samepage.io,2005:Incident/88553072021-12-15T16:29:17Z2021-12-15T16:29:17ZInternet connectivity issue<p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>16:29</var> UTC</small><br><strong>Resolved</strong> - Per AWS the issue is resolved. And we are not seeing any issues.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>16:13</var> UTC</small><br><strong>Monitoring</strong> - The situation seems to be improving but we will continue monitoring it.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>15:55</var> UTC</small><br><strong>Update</strong> - Due to the same internet connectivity issue our systems are unable to access Google and Apple push servers and thus notifications may not be delivered correctly.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>15:49</var> UTC</small><br><strong>Investigating</strong> - Our infrastructure provider AWS is investigating an internet connectivity issue that can cause Samepage inaccessible for some of our customers.</p>tag:status.samepage.io,2005:Incident/62058122021-02-06T03:21:21Z2021-02-06T03:21:21ZVideo calling service is down<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>03:21</var> UTC</small><br><strong>Resolved</strong> - The issue has been resolved. We are sorry for any inconvenience caused but this.</p><p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>01:07</var> UTC</small><br><strong>Identified</strong> - Our video calling service is experiencing an outage. You will not be able to use video calling inside Sameapge Web and App until we fix the issue. We expect the restoration of the service in up to 2 hours. We are really sorry for the inconvenience.</p>tag:status.samepage.io,2005:Incident/45568552020-07-07T19:01:11Z2020-07-07T19:01:11ZMemory overload on one of our page editing servers<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>19:01</var> UTC</small><br><strong>Resolved</strong> - Starting around 0900 UTC today, Samepage suffered memory overload on one of our page editing servers. We failed to detect and correct it for approximately 6 hours. No data was lost on the server-side; however, users' changes to page content were potentially lost under certain conditions. Ordinarily, Samepage client (our desktop application, mobile app, or web session) is caching all page changes in the event of transitory loss of connection to the server. If a user restarts the desktop or mobile app or refreshes the browser session, those changes are lost as the cache is cleared. Due to the extended outage of that one server, we are aware that some customers reported data losses, and we sincerely apologize for this error. Web sessions have already been showing a warning if a user attempts to refresh while changes are still cached. We are adding this to our desktop client to improve user's expectations in the future. In addition, we've implemented additional logging and status notifications to prevent future extended server outages.</p>tag:status.samepage.io,2005:Incident/35658442020-02-14T19:00:00Z2020-02-14T09:31:10ZUnwanted notifications got sent from our servers<p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>19:00</var> UTC</small><br><strong>Resolved</strong> - We had a brief situation where notifications coming from open teams were sent to every guest in that organization. That was resolved. Those notifications (email and push) did include the texts of the messages but at no time were the guests able to access the actual team content. That's why you are seeing the deleted messages. Those are to teams that you do not have access to so when you try to go to those messages you see the deleted error. All the data in your account is safe. Mostly you are probably seeing messages from our tenant as our support teams are all open teams and we have thousands of guests. We are drafting a complete technical explanation and will be posting it in a variety of locations to notify everyone. I am very sorry for this error.</p>tag:status.samepage.io,2005:Incident/23465482019-04-23T22:57:16Z2019-04-23T22:57:16ZWebsite Connectivity Issue<p><small>Apr <var data-var='date'>23</var>, <var data-var='time'>22:57</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Apr <var data-var='date'>23</var>, <var data-var='time'>22:55</var> UTC</small><br><strong>Update</strong> - www.samepage.io is experiencing a connectivity issue. The Samepage app is not affected. You can log in through any browser at https://samepage.io/login.</p><p><small>Apr <var data-var='date'>23</var>, <var data-var='time'>22:53</var> UTC</small><br><strong>Update</strong> - www.samepage.io is experiencing a connectivity issue. The Samepage app is not affected. You can log in through any browser at https://samepage.io/login.</p><p><small>Apr <var data-var='date'>23</var>, <var data-var='time'>22:53</var> UTC</small><br><strong>Identified</strong> - www.samepage.io is experiencing a connectivity issue. The Samepage app is not affected. You can log in through any browser at https://samepage.io/login.</p>tag:status.samepage.io,2005:Incident/23084052019-04-04T23:55:09Z2019-04-04T23:55:09ZAudio & Video Calling Performance<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>23:55</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>19:20</var> UTC</small><br><strong>Monitoring</strong> - Some users may have experienced delays in audio or video calls. The issue has been addressed and we are continuing to monitor performance.</p>tag:status.samepage.io,2005:Incident/19007292018-09-11T08:41:43Z2018-09-18T08:42:04ZIncreased load<p><small>Sep <var data-var='date'>11</var>, <var data-var='time'>08:41</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>10</var>, <var data-var='time'>20:13</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Sep <var data-var='date'>10</var>, <var data-var='time'>19:47</var> UTC</small><br><strong>Investigating</strong> - We're investigating an issue, that put Samepage under unusual load. You may experience degraded performance, like slow opening of pages etc.</p>tag:status.samepage.io,2005:Incident/17344612018-06-06T19:55:10Z2018-09-10T19:55:35ZConflict with Bitdefender's cloud managed anti-virus platform<p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>19:55</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>May <var data-var='date'>17</var>, <var data-var='time'>18:57</var> UTC</small><br><strong>Identified</strong> - We are aware of reports that Bitdefender's cloud managed anti-virus platform may be blocking the use of the Samepage Desktop Application. We are in contact with Bitdefender to fix this situation. In the meantime, if you are affected, please access Samepage via a desktop web browser.</p>tag:status.samepage.io,2005:Incident/17212992018-05-08T16:12:08Z2018-05-08T16:12:08Z"Upgrading our servers" message<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>16:12</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>May <var data-var='date'> 8</var>, <var data-var='time'>16:08</var> UTC</small><br><strong>Monitoring</strong> - We have identified and addressed the issue. We are currently monitoring performance.</p><p><small>May <var data-var='date'> 8</var>, <var data-var='time'>15:46</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating an issue associated with upgrading our servers.</p>tag:status.samepage.io,2005:Incident/16251582018-03-04T13:00:22Z2018-03-04T13:00:22ZSamepage infrastructure maintenance<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>13:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>11:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>12:10</var> UTC</small><br><strong>Scheduled</strong> - On Sunday, March 4th from 3 a.m. to 5 a.m. PDT, we will be performing system upgrades. During this time, you may experience one loss of connectivity lasting five minutes. We apologize for the inconvenience and thank you for your patience.</p>tag:status.samepage.io,2005:Incident/15637262018-01-12T13:37:33Z2018-01-12T13:37:33ZConectivity issues<p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>13:37</var> UTC</small><br><strong>Resolved</strong> - The issue was resolved.</p><p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>12:20</var> UTC</small><br><strong>Identified</strong> - We're experiencing momentarily connectivity issues. Affected clients may try to restart their browsers and NDCs.</p>tag:status.samepage.io,2005:Incident/15516442018-01-03T17:18:00Z2018-01-04T01:22:28ZFull-text search not available<p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>17:18</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>17:17</var> UTC</small><br><strong>Monitoring</strong> - We've identified and fixed the issue. Now we're rebuilding the search index. Meanwhile your search results might be incomplete or inaccurate.</p><p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>16:27</var> UTC</small><br><strong>Investigating</strong> - Our full-text search is currently not functioning. We are investigating the cause and will update when we have more info. We sincerely apologize for this inconvenience and are working to resolve it asap.</p>tag:status.samepage.io,2005:Incident/15475402017-12-28T00:41:00Z2017-12-28T00:54:09ZFull-text search not available<p><small>Dec <var data-var='date'>28</var>, <var data-var='time'>00:41</var> UTC</small><br><strong>Resolved</strong> - We've resolved the issue, but search results of pages created or changed during the past week might be inaccurate or incomplete. This issue will be resolved within 48 hours.</p><p><small>Dec <var data-var='date'>27</var>, <var data-var='time'>23:26</var> UTC</small><br><strong>Investigating</strong> - Our full-text search is currently not functioning, we are investigating the cause and will update when we have more info. We sincerely apologize for this inconvenience and are working to resolve it asap.</p>tag:status.samepage.io,2005:Incident/13686782017-09-20T20:31:58Z2017-09-20T20:31:58ZDNS provider issues<p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>20:31</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>17:16</var> UTC</small><br><strong>Monitoring</strong> - The problem seems to be fixed. We are continuing with close monitoring of the situation.</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>14:43</var> UTC</small><br><strong>Update</strong> - It looks that all .io domains are affected, because the issue is caused by outage of .io domain root nameservers.</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>14:27</var> UTC</small><br><strong>Identified</strong> - We're having issues with our DNS provider, some requests might fail.</p>tag:status.samepage.io,2005:Incident/13511832017-09-09T11:59:42Z2017-09-09T11:59:42ZSamepage database cluster upgrade<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>11:59</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>11:47</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>10:53</var> UTC</small><br><strong>Scheduled</strong> - On Saturday, September 9th from 4 a.m. to 5 a.m. PDT, we will be performing system upgrades. During this time, you may experience one loss of connectivity lasting five minutes. We apologize for the inconvenience and thank you for your patience.</p>tag:status.samepage.io,2005:Incident/13162132017-08-04T06:28:10Z2017-08-04T06:28:10ZSamepage degraded performance and unavailability<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>06:28</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>16:07</var> UTC</small><br><strong>Monitoring</strong> - On August 3rd, between 2pm and 4pm UTC, a fault related to migrating Samepage services to Amazon caused unavailability of Samepage for a majority of our users. The incident was resolved and Samepage is now operating normally. We have identified the root cause, implemented a solution and are preparing additional improvements to prevent such failures in the future. We apologize for the inconvenience.</p>tag:status.samepage.io,2005:Incident/13104132017-07-29T12:01:37Z2017-07-29T12:01:37ZSamepage Infrastructure Migration<p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>12:01</var> UTC</small><br><strong>Completed</strong> - Maintenance completed.</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>11:10</var> UTC</small><br><strong>In progress</strong> - We're starting the announced scheduled maintenance.</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>14:16</var> UTC</small><br><strong>Scheduled</strong> - On Saturday, July 29th from 4 a.m. to 9 a.m. PDT, we will be performing system upgrades. During this time, you may experience one or two losses of connectivity lasting between fifteen and sixty minutes. We apologize for the inconvenience and thank you for your patience.</p>tag:status.samepage.io,2005:Incident/13095382017-07-27T16:23:29Z2017-07-27T16:23:29ZSamepage degraded performance<p><small>Jul <var data-var='date'>27</var>, <var data-var='time'>16:23</var> UTC</small><br><strong>Resolved</strong> - On June 27th, between 2pm and 4pm UTC, a faulty service caused degraded Samepage performance for some of our users. During this time, Samepage was unavailable for these users. The incident was resolved and Samepage is now operating optimally.</p>tag:status.samepage.io,2005:Incident/12839952017-07-04T19:52:57Z2017-07-04T19:52:57ZConnectivity Problem<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>19:52</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>19:33</var> UTC</small><br><strong>Monitoring</strong> - Our upstream provider has fixed the connectivity problem. We are continuing with close monitoring of the situation.</p><p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>19:25</var> UTC</small><br><strong>Identified</strong> - We are working on an issue with our upstream internet provider.</p>tag:status.samepage.io,2005:Incident/12806132017-07-04T19:25:09Z2017-07-04T19:25:09ZSamepage under DDoS attack<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>19:25</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>30</var>, <var data-var='time'>05:07</var> UTC</small><br><strong>Monitoring</strong> - Samepage datacenter suffered a DDoS attack during which Samepage was unavailable. All Samepage services were functional, just unavailable. Our engineers and datacenter provider are analyzing the attack now to determine how to prevent a repetition in the future.</p>tag:status.samepage.io,2005:Incident/12645362017-06-17T21:30:02Z2017-06-17T21:30:02ZDatabase Infrastructure Maintenance<p><small>Jun <var data-var='date'>17</var>, <var data-var='time'>21:30</var> UTC</small><br><strong>Completed</strong> - Database maintenance completed.</p><p><small>Jun <var data-var='date'>17</var>, <var data-var='time'>11:08</var> UTC</small><br><strong>Update</strong> - Global maintenance completed. Now only individual accounts may be temporarily unavailable.</p><p><small>Jun <var data-var='date'>17</var>, <var data-var='time'>10:59</var> UTC</small><br><strong>In progress</strong> - We're starting the announced scheduled maintenance.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>20:19</var> UTC</small><br><strong>Scheduled</strong> - On Saturday, June 17th from 4 a.m. to 9 a.m. PDT, we will be performing system upgrades. During this time, you may experience one or two losses of connectivity lasting between five and thirty minutes. We apologize for the inconvenience and thank you for your patience.</p>tag:status.samepage.io,2005:Incident/12660482017-06-14T15:40:00Z2017-06-15T11:09:16ZSamepage unavaliable<p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>15:40</var> UTC</small><br><strong>Resolved</strong> - This morning around 5am Pacific Time (11:52 UTC), an incident occurred which caused a temporary failure of certain Samepage administration functions. In order to recover from this failure, we took Samepage offline for approximately 1 hour. At approximately 13:00 UTC the error was corrected and access to Samepage was restored. No customer data inside Samepage was lost or damaged. Samepage is functioning normally now.
<br />We have identified a small number of customers where new user registrations may have been affected, and we are reaching out to those customers directly.</p><p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>13:03</var> UTC</small><br><strong>Identified</strong> - We had to recover some data from backup. Most people should see no problem now. We're continuing to investigate.</p><p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>12:14</var> UTC</small><br><strong>Investigating</strong> - Samepage is currently unavaliable. We're investigating the issue.</p>tag:status.samepage.io,2005:Incident/9806452016-11-06T11:04:59Z2016-11-06T11:04:59ZPeering connectivity issues<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>11:04</var> UTC</small><br><strong>Resolved</strong> - Looks like the issues are gone</p><p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>08:53</var> UTC</small><br><strong>Monitoring</strong> - We've got reports about peering connectivity issues from some locations. Our service does not experience any problems, but may be unreachable from those locations.</p>tag:status.samepage.io,2005:Incident/7590002016-09-06T08:55:00Z2016-09-06T09:31:34ZScheduled Maintenance<p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>08:55</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>08:31</var> UTC</small><br><strong>Verifying</strong> - Everything is done and Samepage service is back and running. Samepage service was inaccessible for about 20 minutes within this maintenance period. Verification is currently underway to double check everything is alright. We are very sorry for any inconvenience which might be caused by this maintenance.</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>07:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. Samepage service may become inaccessible for limited time within this maintenance period. We will provide updates as necessary.</p><p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>13:03</var> UTC</small><br><strong>Scheduled</strong> - We will perform a scheduled maintenance of Samepage.io service. The expected duration of maintenance period is one hour. Samepage service may become completely inaccessible for a limited time during this period. We expect about 5 minutes inaccessibility at max. We are very sorry for any inconvenience.</p>