<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>RoSocial  Status - Incident history</title>
    <link>https://rs-status.instatus.com</link>
    <description>RoSocial </description>
    <pubDate>Sun, 3 May 2026 09:38:31 +0000</pubDate>
    
<item>
  <title>Platform SSL Certificate - Handshake Failed</title>
  <description>
    Type: Incident
    Duration: 5 hours and 2 minutes

    Affected Components: User Registration &amp; Login, Jobs, Ads Manager, Blogs, Android App, Posting, Uploading &amp; Content Creation, Watch, Reels, International Language Translation, Pages, Groups
    May 3, 14:40:07 GMT+0 - Resolved - The DNS issue has been solved, and the SSL Certificate issue fix has now been implemented.

Thank you for your patience,

The RoSocial Team May 3, 09:38:31 GMT+0 - Identified - The transfer of databases and servers has now been complete.

When this happens, it also means we have to repoint our DNS IP. This has now been successfully transfered across to the new server, and we&#039;re now fixing the issue of &quot;SSL Handshake Failed&quot;, whereby the DNS doesn&#039;t have an SSL certificate.

This will be fixed in the next couple of hours; we apologise for any inconveniences caused by this downtime.

Thanks,

The RoSocial Team 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , </p>
    <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>14:40:07</var> GMT+0</small><br><strong>Resolved</strong> -
  The DNS issue has been solved, and the SSL Certificate issue fix has now been implemented.

Thank you for your patience,

The RoSocial Team.</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>09:38:31</var> GMT+0</small><br><strong>Identified</strong> -
  The transfer of databases and servers has now been complete.

When this happens, it also means we have to repoint our DNS IP. This has now been successfully transfered across to the new server, and we&#039;re now fixing the issue of &quot;SSL Handshake Failed&quot;, whereby the DNS doesn&#039;t have an SSL certificate.

This will be fixed in the next couple of hours; we apologise for any inconveniences caused by this downtime.

Thanks,

The RoSocial Team.</p>
]]>
  </content:encoded>
  <pubDate>Sun, 3 May 2026 09:38:31 +0000</pubDate>
  <link>https://rs-status.instatus.com/incident/cmopkvpcn091dotsaliouaekp</link>
  <guid>https://rs-status.instatus.com/incident/cmopkvpcn091dotsaliouaekp</guid>
</item>

<item>
  <title>European Server &amp; Database Switchover for RoSocial</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    Affected Components: User Registration &amp; Login, Jobs, Ads Manager, Blogs, RoSocial Europe (EU-WEST-POL), Android App, Posting, Uploading &amp; Content Creation, Watch, Reels, International Language Translation, Pages, Groups
    May 2, 22:00:00 GMT+0 - Completed - Maintenance has completed successfully May 2, 19:00:01 GMT+0 - Identified - Maintenance is now in progress May 2, 19:00:00 GMT+0 - Identified - RoSocial is now owned and operated by RoSocial Platforms.

This means that all userdata, servers and monitoring services are being switched to the ownership of RoSocial Platforms. Since the platform&#039;s database and servers will have to be reconnected to our new servers and database, the RoSocial platform will be entering Maintenance Mode, where no-one will have access to the site.

Alongside the ownership change, this change will allow more effortless upgrading of our services, in the terms of platform optimisation, allowing you to have a much smoother time using RoSocial.

We expect this to last up-to 3 hours; the work starts at 8PM BST, or 3PM ET.

Thank you for your patience.

The RoSocial Team 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , </p>
    <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  RoSocial is now owned and operated by RoSocial Platforms.

This means that all userdata, servers and monitoring services are being switched to the ownership of RoSocial Platforms. Since the platform&#039;s database and servers will have to be reconnected to our new servers and database, the RoSocial platform will be entering Maintenance Mode, where no-one will have access to the site.

Alongside the ownership change, this change will allow more effortless upgrading of our services, in the terms of platform optimisation, allowing you to have a much smoother time using RoSocial.

We expect this to last up-to 3 hours; the work starts at 8PM BST, or 3PM ET.

Thank you for your patience.

The RoSocial Team.</p>
]]>
  </content:encoded>
  <pubDate>Sat, 2 May 2026 19:00:00 +0000</pubDate>
  <link>https://rs-status.instatus.com/maintenance/cmoohyjf100wwhkbt5ua1i27h</link>
  <guid>https://rs-status.instatus.com/maintenance/cmoohyjf100wwhkbt5ua1i27h</guid>
</item>

<item>
  <title>News Feed Loading Error for Users not Logged In</title>
  <description>
    Type: Incident
    Duration: 3 hours and 33 minutes

    Affected Components: User Registration &amp; Login, Jobs, Ads Manager, Blogs, RoSocial Europe (EU-WEST-POL), Android App, Posting, Uploading &amp; Content Creation, Watch, Reels, International Language Translation, Pages, Groups
    Apr 27, 00:18:28 GMT+0 - Resolved - We have implemented a fix to this issue, and the platform has now returned to its fully operational state.

The issue was caused by conflicted information between when we had banned an inappropriate user, and our database. We have now solved this issue and the news feed should be returning back to normal for site-visitors across the platform.

Thank you for your patience,

The RoSocial Team Apr 26, 21:10:29 GMT+0 - Monitoring - The RoSocial platform is now back up, however News Feeds are not loading for users who are not logged in.

We are investigating this further to find the route cause and analyse a plan-of-action in order to get the News Feed visible again for users - we expect this issue to occur for a maximum time of 24 hours.

Logged in users&#039; feeds are available as normal.

Thank you for your patience,

The RoSocial Team Apr 26, 20:45:23 GMT+0 - Identified - The RoSocial site is currently not operational - this is due to a switch in DNS services, made by the switch of servers, domain ownership, and site security (Cloudflare) providers.

We expect the platform to be down for a maximum of 24 hours. We will keep everyone updated during this time.

Thank you for your patience,

The RoSocial Team 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 33 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , </p>
    <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>00:18:28</var> GMT+0</small><br><strong>Resolved</strong> -
  We have implemented a fix to this issue, and the platform has now returned to its fully operational state.

The issue was caused by conflicted information between when we had banned an inappropriate user, and our database. We have now solved this issue and the news feed should be returning back to normal for site-visitors across the platform.

Thank you for your patience,

The RoSocial Team.</p>
<p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>21:10:29</var> GMT+0</small><br><strong>Monitoring</strong> -
  The RoSocial platform is now back up, however News Feeds are not loading for users who are not logged in.

We are investigating this further to find the route cause and analyse a plan-of-action in order to get the News Feed visible again for users - we expect this issue to occur for a maximum time of 24 hours.

Logged in users&#039; feeds are available as normal.

Thank you for your patience,

The RoSocial Team.</p>
<p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>20:45:23</var> GMT+0</small><br><strong>Identified</strong> -
  The RoSocial site is currently not operational - this is due to a switch in DNS services, made by the switch of servers, domain ownership, and site security (Cloudflare) providers.

We expect the platform to be down for a maximum of 24 hours. We will keep everyone updated during this time.

Thank you for your patience,

The RoSocial Team.</p>
]]>
  </content:encoded>
  <pubDate>Sun, 26 Apr 2026 20:45:23 +0000</pubDate>
  <link>https://rs-status.instatus.com/incident/cmog8mcms0xgqpv27ss3ao4kh</link>
  <guid>https://rs-status.instatus.com/incident/cmog8mcms0xgqpv27ss3ao4kh</guid>
</item>

<item>
  <title>Site Maintenance (Server trasnfering)</title>
  <description>
    Type: Maintenance
    Duration: 2 days

    Affected Components: Groups, User Registration &amp; Login, Jobs, Blogs, Ads Manager, RoSocial Europe (EU-WEST-POL), Android App, , Pages, Watch, Reels, International Language Translation, Posting, Uploading &amp; Content Creation, , 
Servers/CDNs → 
RoSocial Platform →
    Sep 12, 18:27:10 GMT+0 - Completed - Maintenance has completed successfully. Sep 8, 13:40:00 GMT+0 - Completed - Maintenance has completed successfully Sep 7, 12:38:45 GMT+0 - Identified - Website resources transfer went well, importing database is still being worked on.

Apologies for the inconvenience. - Zero Sep 6, 13:40:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 days</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , </p>
    <p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>18:27:10</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>13:40:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>12:38:45</var> GMT+0</small><br><strong>Identified</strong> -
  Website resources transfer went well, importing database is still being worked on.

Apologies for the inconvenience. - Zero.</p>
<p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>13:40:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 7 Sep 2025 13:40:00 +0000</pubDate>
  <link>https://rs-status.instatus.com/maintenance/cmf8idr4100wdlsqc5ukvncfc</link>
  <guid>https://rs-status.instatus.com/maintenance/cmf8idr4100wdlsqc5ukvncfc</guid>
</item>

<item>
  <title>Major outage RS</title>
  <description>
    Type: Incident
    Duration: 22 days and 18 hours

    Affected Components: Groups, Blogs, User Registration &amp; Login, Pages, Watch, Reels, International Language Translation, Posting, Uploading &amp; Content Creation, Jobs, Ads Manager
    May 20, 16:24:00 GMT+0 - Resolved - This incident has been resolved. May 20, 07:18:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 days and 18 hours</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>16:24:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>07:18:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 20 May 2025 07:18:00 +0000</pubDate>
  <link>https://rs-status.instatus.com/incident/cmawuvbar000bewgf28fe31rb</link>
  <guid>https://rs-status.instatus.com/incident/cmawuvbar000bewgf28fe31rb</guid>
</item>

  </channel>
  </rss>