<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0" xmlns:media="http://search.yahoo.com/mrss/">
    <channel>
        <title>Oysta</title>
        <link>https://status.myoysta.com/rss</link>
        <description><![CDATA[Status Feed]]></description>
        <atom:link href="https://status.myoysta.com/" rel="self"></atom:link>
                                                                <language>en</language>
        <lastBuildDate>Sat, 18 Apr 2026 12:05:03 +0000</lastBuildDate>
                <item>
            <title><![CDATA[SMS service provider has issues]]></title>
                        <link>https://status.myoysta.com/incident/28/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/28/</guid>
            <description><![CDATA[Our main SMS network provider has issues which is affecting SMS to / from some devices / users.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Wed, 02 Feb 2022 16:01:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Continuing to clear data backlog]]></title>
                        <link>https://status.myoysta.com/incident/27/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/27/</guid>
            <description><![CDATA[We are seeing continuing slow reconnections and restorations of service. We will continue to monitor.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Fri, 23 Apr 2021 15:53:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Mobile network issues]]></title>
                        <link>https://status.myoysta.com/incident/26/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/26/</guid>
            <description><![CDATA[We are seeing partial network restoration now, though local conditions and congestion vary. We expect the network to return to normal as data back log clears]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Fri, 23 Apr 2021 14:45:49 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Mobile network issues]]></title>
                        <link>https://status.myoysta.com/incident/25/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/25/</guid>
            <description><![CDATA[“The Pelion/Jersey Telecom issues continue. They report that 4G is returning, but issues continue with 2G and 3G.

We are seeing SMS and Voice failures across their network.

More information on the issue can be found here:

https://connectivity-status.pelion.com

We are monitoring and will keep this page updated.”]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Fri, 23 Apr 2021 11:55:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Mobile network issues]]></title>
                        <link>https://status.myoysta.com/incident/24/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/24/</guid>
            <description><![CDATA[Pelion’s  network partner (Jersey Telecom) have had an issue with their data network starting at 5am this morning. ( https://connectivity-status.pelion.com/ ) 

This affected Pelion (Stream) SIM data (2G, 3G, 4G) connections. Voice and SMS were unaffected.

Alarm calls from Oysta devices are unaffected, and they will connect as normal.

Oysta devices fall-back to SMS data transmission if GPRS, so should not be affected.


The issue has been partially resolved. Oysta will continue to liaise with Pelion as they resolve the issue.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Fri, 23 Apr 2021 04:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Issue logging in to some of the websites]]></title>
                        <link>https://status.myoysta.com/incident/23/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/23/</guid>
            <description><![CDATA[Issue logging in to some of our systems - once logged in appears OK ( but slower response ) ... investigating

All fixed]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Fri, 12 Mar 2021 13:46:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Address lookups slow]]></title>
                        <link>https://status.myoysta.com/incident/22/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/22/</guid>
            <description><![CDATA[Address lookups, provided by one of our third party suppliers are slow, we've swapped the default to a different provider]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Mon, 28 Oct 2019 07:33:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Loads high causeing slow response on the websites]]></title>
                        <link>https://status.myoysta.com/incident/21/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/21/</guid>
            <description><![CDATA[Investigating ... fixed]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Thu, 17 Oct 2019 11:53:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Webservices unavailable for some]]></title>
                        <link>https://status.myoysta.com/incident/20/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/20/</guid>
            <description><![CDATA[Web sites are available for some.   event processing is unaffected.
Resolved.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Thu, 14 Mar 2019 09:30:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Frontend websites unavailable in some areas]]></title>
                        <link>https://status.myoysta.com/incident/19/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/19/</guid>
            <description><![CDATA[Main system functioning normally - but websites not accessible for some users ... investigating.

All fixed]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Fri, 15 Feb 2019 10:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[MysqlDB connections high - causing load issues]]></title>
                        <link>https://status.myoysta.com/incident/18/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/18/</guid>
            <description><![CDATA[mysql requests are high - causing some lods and performance issues - investigating

All back to normal, please contact support if you have any continuing issues.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Thu, 07 Feb 2019 12:24:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Third party mapping site ( cercalia.com ) down - affecting some mapping  in Spain]]></title>
                        <link>https://status.myoysta.com/incident/17/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/17/</guid>
            <description><![CDATA[cercalia.com, a third party mapping site is down,    This is affecting the map displays and address lookups for some users in Spain ( if they have selected to only use cercalia.com )

cercalia.com was down for 45 mins - now back up.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Sat, 19 Jan 2019 08:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Performance issue on some of our web services]]></title>
                        <link>https://status.myoysta.com/incident/16/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/16/</guid>
            <description><![CDATA[Investigating .... Fixed.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Mon, 01 Oct 2018 12:18:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Web interfaces not showing for some]]></title>
                        <link>https://status.myoysta.com/incident/15/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/15/</guid>
            <description><![CDATA[investigating - all looks OK now]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Mon, 10 Sep 2018 10:13:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Websites loading slowly]]></title>
                        <link>https://status.myoysta.com/incident/12/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/12/</guid>
            <description><![CDATA[The websites at myoysta.com are loading slowly ... investigating

Slight loads on one node in the webserver cluster - fixed.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Fri, 20 Jul 2018 10:32:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Some load issues]]></title>
                        <link>https://status.myoysta.com/incident/11/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/11/</guid>
            <description><![CDATA[There are some performance issues on the web pages over the past 20-30 minutes ... investigating]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Wed, 16 May 2018 10:12:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Map locations lookups slower due to third party issue]]></title>
                        <link>https://status.myoysta.com/incident/10/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/10/</guid>
            <description><![CDATA[Third party geomapping site is down, causing a slow down in map lookups for addresses.

Third party site back up and working normally again now.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Wed, 21 Feb 2018 23:16:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Socket maintenance due to Intel bug]]></title>
                        <link>https://status.myoysta.com/incident/9/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/9/</guid>
            <description><![CDATA[One of our socket servers is undergoing maintenance ( as many other servers did last week) due to the Intel bug.    The failover, socket servers are working fine and events handled normally via this failover system.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Sun, 07 Jan 2018 16:55:57 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Azure systems reboot]]></title>
                        <link>https://status.myoysta.com/incident/7/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/7/</guid>
            <description><![CDATA[https://azure.microsoft.com/en-us/blog/securing-azure-customers-from-cpu-vulnerability/

An industry-wide, hardware-based security vulnerability was disclosed yesterday . Keeping customers secure is always our top priority and we are taking active steps to ensure that no Azure customer is exposed to these vulnerabilities. At the time of this blog post, Microsoft has not received any information to indicate that these vulnerabilities have been used to attack Azure customers.

The majority of Azure infrastructure has already been updated to address this vulnerability. Some aspects of Azure are still being updated and require a reboot of customer VMs for the security update to take effect. Many of you have received notification in recent weeks of a planned maintenance on Azure and have already rebooted your VMs to apply the fix, and no further action by you is required.

With the public disclosure of the security vulnerability today, we are accelerating the planned maintenance timing and will begin automatically rebooting the remaining impacted VMs starting at 3:30pm PST on January 3, 2018.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Thu, 04 Jan 2018 09:43:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Website issue]]></title>
                        <link>https://status.myoysta.com/incident/6/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/6/</guid>
            <description><![CDATA[Websites are not fully accessible at the current time investigating

fixed]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Mon, 23 Oct 2017 13:57:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Slight delay in access for some locations]]></title>
                        <link>https://status.myoysta.com/incident/4/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/4/</guid>
            <description><![CDATA[Investigating .... fixed]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Fri, 25 Aug 2017 08:28:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Myoysta website issues from some locations]]></title>
                        <link>https://status.myoysta.com/incident/2/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/2/</guid>
            <description><![CDATA[This is being worked on now..]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Thu, 06 Jul 2017 14:13:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Network issues at the old datacentre]]></title>
                        <link>https://status.myoysta.com/incident/1/</link>
            <guid isPermaLink="true">https://status.myoysta.com/incident/1/</guid>
            <description><![CDATA[There is a networking issue at the old datacentre.   For devices routing through the old location, this is causing a slow down in event traffic.

There was a compromise of some of our old servers  and a DDOS  - one of the reasons we moved to the cloud to eliminate the impact of such events.  A lot of out traffic still routes through that location though, which affected users, the routing of traffic though this location will reduce as we steadily update the configuration in devices.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oysta</dc:creator>
            <pubDate>Fri, 26 May 2017 17:45:00 +0000</pubDate>
                                                                                                        </item>
            </channel>
</rss>
