Oysta https://status.myoysta.com/ 2026-04-18T10:36:42+00:00 Oysta <![CDATA[SMS service provider has issues]]> https://status.myoysta.com/incident/28/ Our main SMS network provider has issues which is affecting SMS to / from some devices / users.

]]> 2022-02-02T16:01:00+00:00 Oysta <![CDATA[Continuing to clear data backlog]]> https://status.myoysta.com/incident/27/ We are seeing continuing slow reconnections and restorations of service. We will continue to monitor.

]]> 2021-04-23T15:53:00+00:00 Oysta <![CDATA[Mobile network issues]]> https://status.myoysta.com/incident/26/ 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

]]> 2021-04-23T14:45:49+00:00 Oysta <![CDATA[Mobile network issues]]> https://status.myoysta.com/incident/25/ “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.”

]]> 2021-04-23T11:55:00+00:00 Oysta <![CDATA[Mobile network issues]]> https://status.myoysta.com/incident/24/ 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.

]]> 2021-04-23T04:00:00+00:00 Oysta <![CDATA[Issue logging in to some of the websites]]> https://status.myoysta.com/incident/23/ Issue logging in to some of our systems - once logged in appears OK ( but slower response ) ... investigating

All fixed

]]> 2021-03-12T13:46:00+00:00 Oysta <![CDATA[Address lookups slow]]> https://status.myoysta.com/incident/22/ Address lookups, provided by one of our third party suppliers are slow, we've swapped the default to a different provider

]]> 2019-10-28T07:33:00+00:00 Oysta <![CDATA[Loads high causeing slow response on the websites]]> https://status.myoysta.com/incident/21/ Investigating ... fixed

]]> 2019-10-17T11:53:00+00:00 Oysta <![CDATA[Webservices unavailable for some]]> https://status.myoysta.com/incident/20/ Web sites are available for some. event processing is unaffected. Resolved.

]]> 2019-03-14T09:30:00+00:00 Oysta <![CDATA[Frontend websites unavailable in some areas]]> https://status.myoysta.com/incident/19/ Main system functioning normally - but websites not accessible for some users ... investigating.

All fixed

]]> 2019-02-15T10:00:00+00:00 Oysta <![CDATA[MysqlDB connections high - causing load issues]]> https://status.myoysta.com/incident/18/ mysql requests are high - causing some lods and performance issues - investigating

All back to normal, please contact support if you have any continuing issues.

]]> 2019-02-07T12:24:00+00:00 Oysta <![CDATA[Third party mapping site ( cercalia.com ) down - affecting some mapping in Spain]]> https://status.myoysta.com/incident/17/ 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.

]]> 2019-01-19T08:00:00+00:00 Oysta <![CDATA[Performance issue on some of our web services]]> https://status.myoysta.com/incident/16/ Investigating .... Fixed.

]]> 2018-10-01T12:18:00+00:00 Oysta <![CDATA[Web interfaces not showing for some]]> https://status.myoysta.com/incident/15/ investigating - all looks OK now

]]> 2018-09-10T10:13:00+00:00 Oysta <![CDATA[Websites loading slowly]]> https://status.myoysta.com/incident/12/ The websites at myoysta.com are loading slowly ... investigating

Slight loads on one node in the webserver cluster - fixed.

]]> 2018-07-20T10:32:00+00:00 Oysta <![CDATA[Some load issues]]> https://status.myoysta.com/incident/11/ There are some performance issues on the web pages over the past 20-30 minutes ... investigating

]]> 2018-05-16T10:12:00+00:00 Oysta <![CDATA[Map locations lookups slower due to third party issue]]> https://status.myoysta.com/incident/10/ 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.

]]> 2018-02-21T23:16:00+00:00 Oysta <![CDATA[Socket maintenance due to Intel bug]]> https://status.myoysta.com/incident/9/ 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.

]]> 2018-01-07T16:55:57+00:00 Oysta <![CDATA[Azure systems reboot]]> https://status.myoysta.com/incident/7/ 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.

]]> 2018-01-04T09:43:00+00:00 Oysta <![CDATA[Website issue]]> https://status.myoysta.com/incident/6/ Websites are not fully accessible at the current time investigating

fixed

]]> 2017-10-23T13:57:00+00:00 Oysta <![CDATA[Slight delay in access for some locations]]> https://status.myoysta.com/incident/4/ Investigating .... fixed

]]> 2017-08-25T08:28:00+00:00 Oysta <![CDATA[Myoysta website issues from some locations]]> https://status.myoysta.com/incident/2/ This is being worked on now..

]]> 2017-07-06T14:13:00+00:00 Oysta <![CDATA[Network issues at the old datacentre]]> https://status.myoysta.com/incident/1/ 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.

]]> 2017-05-26T17:45:00+00:00