<?xml version="1.0" encoding="UTF-8" ?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title type="text">sipsynergy Status</title>
    <subtitle type="html"><![CDATA[Status Feed]]></subtitle>
    <link href="https://status.sipsynergy.co.uk/atom"></link>
    <id>http://status.sipsynergy.co.uk/</id>
    <link rel="alternate" type="text/html" href="https://status.sipsynergy.co.uk/atom" ></link>
    <link rel="self" type="application/atom+xml" href="http://status.sipsynergy.co.uk/" ></link>
        <updated>2026-04-12T10:17:26+00:00</updated>
        <entry>
            <author>
                <name>sipsynergy Status</name>
            </author>
            <title type="text"><![CDATA[SIPTrunks]]></title>
            <link rel="alternate" type="text/html" href="https://status.sipsynergy.co.uk/incident/4/"></link>
            <id>https://status.sipsynergy.co.uk/incident/4/</id>
            <summary type="html"><![CDATA[<p>We are currently investigating an issue with our SIPTrunk Service.
More information will be supplied when available.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-09-28T08:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>sipsynergy Status</name>
            </author>
            <title type="text"><![CDATA[EHC Service Disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.sipsynergy.co.uk/incident/3/"></link>
            <id>https://status.sipsynergy.co.uk/incident/3/</id>
            <summary type="html"><![CDATA[<h3>28 May 2019 12:30</h3>
<p>We have stabilised the affected EHC cluster and will be contacting affected Customers individually in regards to this incident.</p>
<h3>28 May 2019 08:00</h3>
<p>We have identified the cause of the issue and are implementing a workaround.</p>
<h3>28 May 2019 06:33</h3>
<p>We are investigating an issue with one of our EHC clusters.  At the moment, some Customers may be experiencing service disruption placing and receiving external calls. We will update this page as this investigation continues.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-05-28T05:33:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>sipsynergy Status</name>
            </author>
            <title type="text"><![CDATA[Email Delays]]></title>
            <link rel="alternate" type="text/html" href="https://status.sipsynergy.co.uk/incident/2/"></link>
            <id>https://status.sipsynergy.co.uk/incident/2/</id>
            <summary type="html"><![CDATA[<h3>25 Jan 2019 01:00</h3>
<p>Microsoft have confirmed the affected service has now been fixed and have closed the Incident. We are experiencing normal service with Emails, however, if you need an urgent response, please give us a call on 0330 119 0999.</p>
<h3>24 Jan 2019 22:00</h3>
<p>Current status: Microsoft are continuing to monitor the environment to ensure that service is recovering and email is being delivered as expected. We are not experiencing delays to email that we were previously, although we are continuing to monitor until the incident is cleared by Microsoft.  If you need an urgent response, please give us a call on 0330 119 0999.</p>
<h3>24 Jan 2019 19:00</h3>
<p>Current status: Microsoft have identified a potential fix to address the issue and are testing the fix to confirm that it is a viable solution.</p>
<h3>24 Jan 2019 16:10</h3>
<p>Current status: Microsoft are continuing to fix the problem while actively monitoring the connections to the healthy infrastructure. Additionally, they’re reviewing system logs to understand the underlying cause of the issue.  We are still seeing some of our Emails suffer small delays - if you need an urgent response, please give us a call on 0330 119 0999.</p>
<h3>24 Jan 2019 11:00</h3>
<p>Office 365 is experiencing connectivity issues for some subscribers.  We use Office 365 for Email, and therefore any tickets raised by Email may be subject to delays.  We will post another update when we receive an all clear from Microsoft.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2019-01-24T11:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>sipsynergy Status</name>
            </author>
            <title type="text"><![CDATA[Broadband in London Area]]></title>
            <link rel="alternate" type="text/html" href="https://status.sipsynergy.co.uk/incident/1/"></link>
            <id>https://status.sipsynergy.co.uk/incident/1/</id>
            <summary type="html"><![CDATA[<h3>26 Sept 2018 13:15</h3>
<p>All service are back to normal. Will update with root cause as one is available to us.</p>
<h3>26 Sept 2018 12:40</h3>
<p>We are noticing that services are coming back on line. We are continuing to monitor restoration. Next update 13:30</p>
<h3>26 Sept 2018 12:30</h3>
<p>Still no update. Appears to be affecting multiple ISPs in the London area. Continuing to chase BT. Next update 13:00</p>
<h3>26 Sept 2018 12:00</h3>
<p>No further information available, next update 12:30</p>
<h3>26 Sept 2018 11:45</h3>
<p>BT have confirmed they are experiencing issues and are investigating. We are chasing for further updates.</p>
<h3>26 Sept 2018 11:30</h3>
<p>We have just seen a number of BT based broadband lines in the London area disconnecting. We have raised a fault with the provider and will send out a further update shortly.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2018-09-26T10:30:00+00:00</updated>
        </entry>
</feed>
