<?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>VIP VoIP Status - Incident history</title>
    <link>https://status.vipvoip.co.uk</link>
    <description>VIP VoIP</description>
    <pubDate>Thu, 27 Nov 2025 15:03:12 +0000</pubDate>
    
<item>
  <title>Vultr London Data Centre Partial Outage</title>
  <description>
    Type: Incident
    Duration: 4 hours and 50 minutes

    Affected Components: Servers
    Nov 27, 15:03:12 GMT+0 - Investigating - We are currently aware of an incident at Vultr&#039;s London data Centres causing a partial outage to some servers.  
  
The network engineers at Vultr are actively working with our upstream providers to restore connectivity as quickly as possible. investigating this incident.

We ourselves at VIP VoIP are always working behind the scenes to see if there are any affected services that need swapping over to backup servers as well where this is possible.

We aim to provide a further update in the next 30 minutes Nov 27, 15:36:32 GMT+0 - Identified - The team at Vultr are continuing to work on a fix for this incident and we are awaiting a further update.

Just to add that this should only really affect really old servers in the systems (Those old enough to not have a backup server) All servers created in 2022 onwards will most likely have a backup server in place and therefore when affected by this outage would have automatically failed over to their own backup server.

If you need any assistance in the meantime please reach out to the team

Thank you

VIP VoIP Nov 27, 19:53:34 GMT+0 - Resolved - This incident at Vultr London has been resolved.

If you were affected by this outage, it will be because your clients service still resides on an older server.

Please reach out to the team to organise updating the client service to one of our newer shared clusters which have backup servers built in as standard

Thank you

VIP VoIP Support  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 50 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:03:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently aware of an incident at Vultr&#039;s London data Centres causing a partial outage to some servers.  
  
The network engineers at Vultr are actively working with our upstream providers to restore connectivity as quickly as possible. investigating this incident.

We ourselves at VIP VoIP are always working behind the scenes to see if there are any affected services that need swapping over to backup servers as well where this is possible.

We aim to provide a further update in the next 30 minutes.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:36:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The team at Vultr are continuing to work on a fix for this incident and we are awaiting a further update.

Just to add that this should only really affect really old servers in the systems (Those old enough to not have a backup server) All servers created in 2022 onwards will most likely have a backup server in place and therefore when affected by this outage would have automatically failed over to their own backup server.

If you need any assistance in the meantime please reach out to the team

Thank you

VIP VoIP.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:53:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident at Vultr London has been resolved.

If you were affected by this outage, it will be because your clients service still resides on an older server.

Please reach out to the team to organise updating the client service to one of our newer shared clusters which have backup servers built in as standard

Thank you

VIP VoIP Support .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 27 Nov 2025 15:03:12 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cmihkcx1z09jx9gjwc77iqxve</link>
  <guid>https://status.vipvoip.co.uk/incident/cmihkcx1z09jx9gjwc77iqxve</guid>
</item>

<item>
  <title>Issues with Inbound calls routed via Magrathea and Amazon</title>
  <description>
    Type: Incident
    Duration: 1 hour and 2 minutes

    Affected Components: Voice Calls
    Oct 29, 16:39:29 GMT+0 - Investigating - We are aware of reports of some users experiencing issues affecting calls for inbound routes that are routed via Magrathea and Amazon Data centres similar to those experienced last week

Our team are are currently investigating this as a priority and we will provide a further update shortly.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) Oct 29, 17:41:32 GMT+0 - Resolved - We have now investigated the issues raised by some users 

This was not the same issue as that raised last week.

We believe the cause to be a temporary load balancing issue in Amazon. 

We&#039;re reviewing our Amazon infrastructure set up to address this going forwards

Thank you for your patience for anyone affected.

Any further issues please raise them in the usual way.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [**www.vipvoip.co.uk**](http://www.vipvoip.co.uk) 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:39:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of reports of some users experiencing issues affecting calls for inbound routes that are routed via Magrathea and Amazon Data centres similar to those experienced last week

Our team are are currently investigating this as a priority and we will provide a further update shortly.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:41:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have now investigated the issues raised by some users 

This was not the same issue as that raised last week.

We believe the cause to be a temporary load balancing issue in Amazon. 

We&#039;re reviewing our Amazon infrastructure set up to address this going forwards

Thank you for your patience for anyone affected.

Any further issues please raise them in the usual way.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [**www.vipvoip.co.uk**](http://www.vipvoip.co.uk).&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 29 Oct 2025 16:39:29 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cmhc80rzy005nb2b4w73hsztw</link>
  <guid>https://status.vipvoip.co.uk/incident/cmhc80rzy005nb2b4w73hsztw</guid>
</item>

<item>
  <title>Inbound calls - AWS London and Paris hosted servers </title>
  <description>
    Type: Incident
    

    Affected Components: Voice Calls
    Oct 22, 15:49:53 GMT+0 - Investigating - We are still currently investigating this incident alongside our carrier partner Magrathea and Amazon London and Paris hosted Data Centres.

Magrathea update in the last 30 minutes has been as follows:

We are receiving some reports of issues with inbound calls. At this time we have no current issues on VoIP or IP and are not aware of any issues within the Magrathea network or edge interconnects.  
  
So far we have been unable to find a common factor other than AWS services being within the client call path, however we are continuing to investigate and will provide further updates as soon as we can. Oct 22, 12:15:41 GMT+0 - Investigating - We’re seeing a few different random platform issues for inbound call failures, and no audio on inbound calls.

It seems to currently be affecting customer services hosted in AWS London and Paris data centres. 

We are currently investigating the possible cause and will provide a further update in the next hour

Thank you 

VIP VoIP support team Oct 23, 07:38:42 GMT+0 - Monitoring - Following ongoing monitoring on the AWS issue, last night we now believe the routing to be working correctly again, please can you retest and any further issues reach out to the team

VIP VoIP Support Oct 22, 16:32:33 GMT+0 - Identified - Following our earlier notice, Magrathea have identified intermittent issues with AWS routing traffic to their network and have raised this with the AWS Peering team. 

These issues seem to be specific to the London and Paris Amazon data centres been able to route traffic specifically to Magrathea which is then affecting the inbound calls termination

We are now awaiting the response from the AWS team and will provide further information when it is available.

VIP VoIP support team Oct 23, 06:18:19 GMT+0 - Identified - Magrathea have been in touch this morning regarding their case raised with Amazon and cannot see any further updates so far this morning from Amazon AWS services.

This issue is been treated with the highest priority.

We will continue to monitor and as soon as we get any further updates will relay this info back accordingly. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:49:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are still currently investigating this incident alongside our carrier partner Magrathea and Amazon London and Paris hosted Data Centres.

Magrathea update in the last 30 minutes has been as follows:

We are receiving some reports of issues with inbound calls. At this time we have no current issues on VoIP or IP and are not aware of any issues within the Magrathea network or edge interconnects.  
  
So far we have been unable to find a common factor other than AWS services being within the client call path, however we are continuing to investigate and will provide further updates as soon as we can..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:15:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We’re seeing a few different random platform issues for inbound call failures, and no audio on inbound calls.

It seems to currently be affecting customer services hosted in AWS London and Paris data centres. 

We are currently investigating the possible cause and will provide a further update in the next hour

Thank you 

VIP VoIP support team.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:38:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Following ongoing monitoring on the AWS issue, last night we now believe the routing to be working correctly again, please can you retest and any further issues reach out to the team

VIP VoIP Support.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:32:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Following our earlier notice, Magrathea have identified intermittent issues with AWS routing traffic to their network and have raised this with the AWS Peering team. 

These issues seem to be specific to the London and Paris Amazon data centres been able to route traffic specifically to Magrathea which is then affecting the inbound calls termination

We are now awaiting the response from the AWS team and will provide further information when it is available.

VIP VoIP support team.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:18:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Magrathea have been in touch this morning regarding their case raised with Amazon and cannot see any further updates so far this morning from Amazon AWS services.

This issue is been treated with the highest priority.

We will continue to monitor and as soon as we get any further updates will relay this info back accordingly..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 22 Oct 2025 12:15:41 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cmh1yif1n00b6va2k438um0xa</link>
  <guid>https://status.vipvoip.co.uk/incident/cmh1yif1n00b6va2k438um0xa</guid>
</item>

<item>
  <title>Possible issues with inbound/outbound calls via carrier (EE/O2/Vodafone) - IDENTIFIED</title>
  <description>
    Type: Incident
    Duration: 19 hours and 18 minutes

    Affected Components: External Hardware and Software - Unrelated to VIP VoIP directly
    Jul 24, 12:47:37 GMT+0 - Identified - We are aware of reports of some users experiencing issues affecting calls for inbound and outbound routes that are routed via Vodafone, EE and in some cases O2 as well.

Our own carrier Magrathea has recently put an update out regarding this that we are now sharing with you below:

Following multiple reports of outbound call failures to mobile numbers. We have established that there is a problem beyond our network. 

  
Many clients will already be aware that Vodafone and EE have confirmed issues meaning they are unable to terminate calls on their networks. We will continue to monitor and provide an update when normal service is restored.

---

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

Please do not reply to this email, if you have any queries please check the status pages of those networks directly.

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

If you believe you have an issue for calls outside those which may be affected by these networks, please reach out to us directly at support@vipvoip.co.uk

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) Jul 24, 16:32:03 GMT+0 - Monitoring - Following on from our previous updates, we still await updates on the fault calling mobile numbers but continue to monitor. 

The situation is now being updated in mainstream media so we will not send further updates until we see that it is fully resolved. Jul 25, 08:06:06 GMT+0 - Resolved - Clients will likely be aware by now that BT issued an update shortly before 9.30pm yesterday confirming that a technical fault impacting voice services on their network had been resolved.

Please report any new issues today in the usual way. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:47:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are aware of reports of some users experiencing issues affecting calls for inbound and outbound routes that are routed via Vodafone, EE and in some cases O2 as well.

Our own carrier Magrathea has recently put an update out regarding this that we are now sharing with you below:

Following multiple reports of outbound call failures to mobile numbers. We have established that there is a problem beyond our network. 

  
Many clients will already be aware that Vodafone and EE have confirmed issues meaning they are unable to terminate calls on their networks. We will continue to monitor and provide an update when normal service is restored.

---

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

Please do not reply to this email, if you have any queries please check the status pages of those networks directly.

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

If you believe you have an issue for calls outside those which may be affected by these networks, please reach out to us directly at support@vipvoip.co.uk

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:32:03&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Following on from our previous updates, we still await updates on the fault calling mobile numbers but continue to monitor. 

The situation is now being updated in mainstream media so we will not send further updates until we see that it is fully resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:06:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Clients will likely be aware by now that BT issued an update shortly before 9.30pm yesterday confirming that a technical fault impacting voice services on their network had been resolved.

Please report any new issues today in the usual way..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 24 Jul 2025 12:47:37 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cmdhe0y8m005y131y58fs2k6n</link>
  <guid>https://status.vipvoip.co.uk/incident/cmdhe0y8m005y131y58fs2k6n</guid>
</item>

<item>
  <title>Possible issues with outbound INTERNATIONAL calls via carrier (Magrathea) - INVESTIGATING</title>
  <description>
    Type: Incident
    Duration: 55 minutes

    Affected Components: Voice Calls
    May 2, 18:07:50 GMT+0 - Investigating - We are aware of reports of some users experiencing issues affecting calls for international outbound routes that are routed via Magrathea

The majority of our international outbound routes are generally via alternatively carriers so disruption should be minimal

Our team are in contact with Magrathea who have engineers investigating this as a priority and we will provide a further update shortly.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) May 2, 19:02:25 GMT+0 - Resolved - **This incident has been resolved.**

We believe the earlier issue affecting international outbound calls this is now cleared.

The carrier engineers are still investigating and more details will follow as soon as we can.

We sincerely apologise for the disruption this evening.

Please do not reply to this email, if you have any queries please contact us on

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 55 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:07:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of reports of some users experiencing issues affecting calls for international outbound routes that are routed via Magrathea

The majority of our international outbound routes are generally via alternatively carriers so disruption should be minimal

Our team are in contact with Magrathea who have engineers investigating this as a priority and we will provide a further update shortly.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:02:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  **This incident has been resolved.**

We believe the earlier issue affecting international outbound calls this is now cleared.

The carrier engineers are still investigating and more details will follow as soon as we can.

We sincerely apologise for the disruption this evening.

Please do not reply to this email, if you have any queries please contact us on

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 2 May 2025 18:07:50 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cma73wuv9001rk0ocss1clo4m</link>
  <guid>https://status.vipvoip.co.uk/incident/cma73wuv9001rk0ocss1clo4m</guid>
</item>

<item>
  <title>Possible issues with inbound/outbound calls via carrier (Magrathea) - CLEARED</title>
  <description>
    Type: Incident
    Duration: 25 days and 25 minutes

    Affected Components: Voice Calls
    May 6, 08:54:28 GMT+0 - Resolved - Further update from our Carrier Partner - Magrathea  
Following on from the issues that were experienced on Friday 2nd May, please find RFO details below.

We sincerely apologise for the inconvenience that this disruption will have caused you – thank you for your support and patience during this period.

Please do not reply to this email, if you have any queries please contact us on [support@vipvoip.co.uk](mailto:support@vipvoip.co.uk)

Post Incident Review 

Incident Symptom: Inability to process inbound/outbound SIP calls 

Date of Incident: Friday 2nd May 2025 

Incident Duration: 14:00 to 19:45 (intermittent and varying impact) 

Incident Timeline: 

Magrathea customers experienced issues with inbound SIP calls on Friday from approximately 14:15\. 

Numbers that had failover routing in place continued to function and the fault was intermittent meaning the severity and extent was unclear until approximately 14:44 at which point we issued our first service notice. 

Service was initially restored a few minutes later with an all clear notice sent at 14:54\. However the issue reappeared and impacted inbound SIP calls again intermittently up to 16:21 when it was cleared. 

At approximately 17:50 we received reports of number translation targets being out of sync and a few minutes later reports of outbound calls failing. Both of these issues impacted a smaller number of clients but the same inbound call failures reappeared intermittently alongside. We finally reported the issue fully resolved at 19:48 and continued monitoring before issuing an ‘all clear’ notice at 21:00\. 

Incident Summary: 

The primary cause of this incident was a memory leak condition in the systems responsible for monitoring and reporting errors. This had the effect of depriving operational memory to systems responsible for core network routing decisions causing them to malfunction. 

Because the fault occurred in the monitoring systems themselves it frustrated our engineers attempt to quickly resolve the problem and in addition as the fault was intermittent in nature not all of our bank of four independent systems were affected. 

These systems have run unchanged for many years without issue and so the issue was completely unexpected. We have taken immediate action to ensure that it cannot reoccur as well as planning additional separate ways to detect this type of issue promptly if it occurs elsewhere in the network.

Separately to this a minor fault occurred in our network during a similar time period which caused changes requested through our numbering API to not propagate through the network correctly. This fault has been isolated to a new network component that was undergoing our final test stages prior to deployment. This was not resolved with our normal speed due to our focus on the more significant fault above. Oct 22, 21:39:31 GMT+0 - Identified - Issues for inbound calls are still ongoing.

We are still awaiting further updates from Amazon Web services with these issues via our carrier partners Magrathea where engineer teams are continuing to liaise around a solution

We do not expect any further updates until the morning now but will continue to monitor things and feedback any updates as we receive them

VIP VoIP support team  Feb 24, 14:17:53 GMT+0 - Resolved - This incident has been resolved. May 2, 13:52:26 GMT+0 - Investigating - We are aware of reports of some users experiencing issues affecting calls for inbound routes that are routed via Magrathea

Our team are in contact with Magrathea who have engineers investigating this as a priority and we will provide a further update shortly.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) May 2, 14:29:33 GMT+0 - Investigating - We have been made aware that the previous issue raised regarding inbound calls failing is NOT yet resolved. 

Magrathea did recently send us a notice to say they were but have since retracted this.

These current issues do seem to be intermittent and will not be affecting all numbers but we are aware of reports that some users are still experiencing issues affecting calls for inbound routes that are routed via Magrathea

Our team are in contact with Magrathea who have engineers investigating this as a priority and we will provide a further update shortly.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) May 2, 15:30:59 GMT+0 - Resolved - This incident has been resolved.

Please see the latest update from our carrier partners Magrathea regarding this below:

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

Dear all

The issue with inbound calls appears to be cleared. A full RFO will be sent as soon as we have concluded our investigations.

We are sincerely sorry for the impact this has caused you and your customers this afternoon.

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

We apologise for any inconvenience caused.

If you have any queries please contact us on [support@vipvoip.co.uk](mailto:support@magrathea-telecom.co.uk) 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 25 days and 25 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:54:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Further update from our Carrier Partner - Magrathea  
Following on from the issues that were experienced on Friday 2nd May, please find RFO details below.

We sincerely apologise for the inconvenience that this disruption will have caused you – thank you for your support and patience during this period.

Please do not reply to this email, if you have any queries please contact us on [support@vipvoip.co.uk](mailto:support@vipvoip.co.uk)

Post Incident Review 

Incident Symptom: Inability to process inbound/outbound SIP calls 

Date of Incident: Friday 2nd May 2025 

Incident Duration: 14:00 to 19:45 (intermittent and varying impact) 

Incident Timeline: 

Magrathea customers experienced issues with inbound SIP calls on Friday from approximately 14:15\. 

Numbers that had failover routing in place continued to function and the fault was intermittent meaning the severity and extent was unclear until approximately 14:44 at which point we issued our first service notice. 

Service was initially restored a few minutes later with an all clear notice sent at 14:54\. However the issue reappeared and impacted inbound SIP calls again intermittently up to 16:21 when it was cleared. 

At approximately 17:50 we received reports of number translation targets being out of sync and a few minutes later reports of outbound calls failing. Both of these issues impacted a smaller number of clients but the same inbound call failures reappeared intermittently alongside. We finally reported the issue fully resolved at 19:48 and continued monitoring before issuing an ‘all clear’ notice at 21:00\. 

Incident Summary: 

The primary cause of this incident was a memory leak condition in the systems responsible for monitoring and reporting errors. This had the effect of depriving operational memory to systems responsible for core network routing decisions causing them to malfunction. 

Because the fault occurred in the monitoring systems themselves it frustrated our engineers attempt to quickly resolve the problem and in addition as the fault was intermittent in nature not all of our bank of four independent systems were affected. 

These systems have run unchanged for many years without issue and so the issue was completely unexpected. We have taken immediate action to ensure that it cannot reoccur as well as planning additional separate ways to detect this type of issue promptly if it occurs elsewhere in the network.

Separately to this a minor fault occurred in our network during a similar time period which caused changes requested through our numbering API to not propagate through the network correctly. This fault has been isolated to a new network component that was undergoing our final test stages prior to deployment. This was not resolved with our normal speed due to our focus on the more significant fault above..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:39:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Issues for inbound calls are still ongoing.

We are still awaiting further updates from Amazon Web services with these issues via our carrier partners Magrathea where engineer teams are continuing to liaise around a solution

We do not expect any further updates until the morning now but will continue to monitor things and feedback any updates as we receive them

VIP VoIP support team .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:17:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:52:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of reports of some users experiencing issues affecting calls for inbound routes that are routed via Magrathea

Our team are in contact with Magrathea who have engineers investigating this as a priority and we will provide a further update shortly.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:29:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We have been made aware that the previous issue raised regarding inbound calls failing is NOT yet resolved. 

Magrathea did recently send us a notice to say they were but have since retracted this.

These current issues do seem to be intermittent and will not be affecting all numbers but we are aware of reports that some users are still experiencing issues affecting calls for inbound routes that are routed via Magrathea

Our team are in contact with Magrathea who have engineers investigating this as a priority and we will provide a further update shortly.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:30:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved.

Please see the latest update from our carrier partners Magrathea regarding this below:

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

Dear all

The issue with inbound calls appears to be cleared. A full RFO will be sent as soon as we have concluded our investigations.

We are sincerely sorry for the impact this has caused you and your customers this afternoon.

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

We apologise for any inconvenience caused.

If you have any queries please contact us on [support@vipvoip.co.uk](mailto:support@magrathea-telecom.co.uk).&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 2 May 2025 13:52:26 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cma6usgln000k101jr9k3r7kr</link>
  <guid>https://status.vipvoip.co.uk/incident/cma6usgln000k101jr9k3r7kr</guid>
</item>

<item>
  <title>Rackspace Data Centre - Possible outage</title>
  <description>
    Type: Incident
    Duration: 40 minutes

    Affected Components: Servers
    Feb 13, 08:56:13 GMT+0 - Investigating - We are currently investigating an incident this morning regarding some client servers that are not accessible.

The issue seems to be centred around our &#039;Rackspace&#039; data centres

We have raised the issue with them and will relay back further information as we have it and are treating the issue as highest priority.

VIP VoIP Feb 13, 09:36:17 GMT+0 - Resolved - We believe the incident this morning affecting servers at the Rackspace data centres are now resolved. 

We believe the disruption was caused by a routing issue to the server from outside Rackspace because some customers lost connectivity at about 8:32am, but most on the server look unaffected. All those customers reconnected about 9:02am.

As these client servers are our older ones, they do not have a backup server option.

We apologise for any disruption caused.

If your clients were affected and you would like to move them to a longer term solution, please raise a ticket to [support@vipvoip.co.uk](mailto:support@vipvoip.co.uk) with the name of your client server and we will be happy to help arrange migrating the clients and client data to a newer server setup that includes the backup server for business continuity. 

VIP VoIP Support Team 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 40 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:56:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident this morning regarding some client servers that are not accessible.

The issue seems to be centred around our &#039;Rackspace&#039; data centres

We have raised the issue with them and will relay back further information as we have it and are treating the issue as highest priority.

VIP VoIP.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:36:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We believe the incident this morning affecting servers at the Rackspace data centres are now resolved. 

We believe the disruption was caused by a routing issue to the server from outside Rackspace because some customers lost connectivity at about 8:32am, but most on the server look unaffected. All those customers reconnected about 9:02am.

As these client servers are our older ones, they do not have a backup server option.

We apologise for any disruption caused.

If your clients were affected and you would like to move them to a longer term solution, please raise a ticket to [support@vipvoip.co.uk](mailto:support@vipvoip.co.uk) with the name of your client server and we will be happy to help arrange migrating the clients and client data to a newer server setup that includes the backup server for business continuity. 

VIP VoIP Support Team.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 13 Feb 2025 08:56:13 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cm733v3rf001c13d0d4m14lk3</link>
  <guid>https://status.vipvoip.co.uk/incident/cm733v3rf001c13d0d4m14lk3</guid>
</item>

<item>
  <title>Possible issues with Management Portal - Investigating</title>
  <description>
    Type: Incident
    Duration: 2 hours and 21 minutes

    
    Jan 11, 08:17:15 GMT+0 - Investigating - We are aware of reports of an outage with our management portal, which may also be affecting some browser phone users.

Our team are investigating and we will provide a further update shortly.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [**www.vipvoip.co.uk**](http://www.vipvoip.co.uk) Jan 11, 10:38:31 GMT+0 - Resolved - We believe all systems should now be back to normal and earlier issues with the management portal are now cleared.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [**www.vipvoip.co.uk**](http://www.vipvoip.co.uk) 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 21 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:17:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of reports of an outage with our management portal, which may also be affecting some browser phone users.

Our team are investigating and we will provide a further update shortly.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [**www.vipvoip.co.uk**](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:38:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We believe all systems should now be back to normal and earlier issues with the management portal are now cleared.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [**www.vipvoip.co.uk**](http://www.vipvoip.co.uk).&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 11 Jan 2025 08:17:15 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cm5rwxuk9007j13c2kg0oj0r1</link>
  <guid>https://status.vipvoip.co.uk/incident/cm5rwxuk9007j13c2kg0oj0r1</guid>
</item>

<item>
  <title>Billing CDR data error - Investigating</title>
  <description>
    Type: Incident
    Duration: 4 hours and 19 minutes

    Affected Components: Billing Tools
    Dec 2, 16:47:15 GMT+0 - Investigating - We are currently aware of reports of some resellers experiencing issues affecting call data report (CDR) downloads for clients invoicing this month .

Our team are currently investigating this as a priority and we will provide a further update shortly.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) Dec 2, 21:06:32 GMT+0 - Resolved - The issues affecting call data report (CDR) downloads for clients is now resolved.

Resellers should now have received a further email allowing the download of client CDR data for the month.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries or further questions regarding this please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 19 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:47:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently aware of reports of some resellers experiencing issues affecting call data report (CDR) downloads for clients invoicing this month .

Our team are currently investigating this as a priority and we will provide a further update shortly.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:06:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issues affecting call data report (CDR) downloads for clients is now resolved.

Resellers should now have received a further email allowing the download of client CDR data for the month.

We apologise for the inconvenience

Please do not reply to this email, if you have any queries or further questions regarding this please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 2 Dec 2024 16:47:15 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cm479ku9n000ues6er6639rxy</link>
  <guid>https://status.vipvoip.co.uk/incident/cm479ku9n000ues6er6639rxy</guid>
</item>

<item>
  <title>Possible issues with calls via Magrathea - Investigating</title>
  <description>
    Type: Incident
    Duration: 53 minutes

    Affected Components: Voice Calls
    Nov 20, 10:41:15 GMT+0 - Investigating - We are aware of reports of some call issues, and believe this issue lies with Magrathea call routes.

Our team are investigating and we will provide a further update shortly.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) Nov 20, 10:57:10 GMT+0 - Identified - We are still experiencing some issues with both inbound and outbound calls.

Magrathea engineers are in the process of fully restoring service - more updates will follow as soon as they are available. We apologise for the disruption.

We apologise for the disruption.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [**www.vipvoip.co.uk**](http://www.vipvoip.co.uk) Nov 20, 11:34:36 GMT+0 - Resolved - **This incident has been resolved.**

The issue affecting inbound and outbound calls this morning is now cleared.

The carrier engineers are in the process of investigating and more details will follow as soon as we can.

We sincerely apologise for the disruption this morning.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) Nov 20, 14:06:22 GMT+0 - Resolved - Following on from the earlier issues with Magrathea we have now had the following further update from them.

We are now confident that we have isolated the problem but the underlying cause is still being investigated.

Our initial findings are, as you can expect, that the failover systems did not meet our expectations in this event and that itself will be taken on as a project by our team to ensure greater resilience going forward.

Meanwhile, our technical team will be fully focussed on proving the underlying cause so we can provide a full and transparent RFO. To ensure this is accurate and useful we ask for your patience but hope to get the document to you no later than tomorrow afternoon

We sincerely apologise for the inconvenience that this disruption will have caused you this morning. Thank you for your support and patience during this period.

Kind regards

**Magrathea Telecommunications Ltd** Nov 21, 11:57:39 GMT+0 - Resolved - A further update has been provided from our Carrier partner regarding the issue with some calls yesterday.

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

Our technical specialists have continued working through the evening and overnight to closely monitor our network stability whilst also carrying out further investigations into the root cause of yesterdays&#039; outage. 

As you will appreciate, such a serious outage requires thorough investigation and the volume of logs and analysis to be done takes some time. We have now reached a conclusion on the root cause of the outage..

In summary, we can confirm that there was interruption to some calls between 10:34am and 11:20am on the 20th November, with service returning sporadically during that period. A core routing device experienced a fault that affected the internal BGP routing, which caused some of our RTP instances to have incorrect routing for UDP traffic. This led to call switching servers failing to respond to requests and forward calls, requiring each affected RTP machine to be restarted. 

The team continue to carry out tests and put plans in place to improve resilience should a similar fault occur in the future, and of course are constantly monitoring the network while we have this vulnerability. This work will continue throughout the day as a matter of utmost priority. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 53 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:41:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of reports of some call issues, and believe this issue lies with Magrathea call routes.

Our team are investigating and we will provide a further update shortly.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:57:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are still experiencing some issues with both inbound and outbound calls.

Magrathea engineers are in the process of fully restoring service - more updates will follow as soon as they are available. We apologise for the disruption.

We apologise for the disruption.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [**www.vipvoip.co.uk**](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:34:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  **This incident has been resolved.**

The issue affecting inbound and outbound calls this morning is now cleared.

The carrier engineers are in the process of investigating and more details will follow as soon as we can.

We sincerely apologise for the disruption this morning.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:06:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Following on from the earlier issues with Magrathea we have now had the following further update from them.

We are now confident that we have isolated the problem but the underlying cause is still being investigated.

Our initial findings are, as you can expect, that the failover systems did not meet our expectations in this event and that itself will be taken on as a project by our team to ensure greater resilience going forward.

Meanwhile, our technical team will be fully focussed on proving the underlying cause so we can provide a full and transparent RFO. To ensure this is accurate and useful we ask for your patience but hope to get the document to you no later than tomorrow afternoon

We sincerely apologise for the inconvenience that this disruption will have caused you this morning. Thank you for your support and patience during this period.

Kind regards

**Magrathea Telecommunications Ltd**.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:57:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  A further update has been provided from our Carrier partner regarding the issue with some calls yesterday.

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

Our technical specialists have continued working through the evening and overnight to closely monitor our network stability whilst also carrying out further investigations into the root cause of yesterdays&#039; outage. 

As you will appreciate, such a serious outage requires thorough investigation and the volume of logs and analysis to be done takes some time. We have now reached a conclusion on the root cause of the outage..

In summary, we can confirm that there was interruption to some calls between 10:34am and 11:20am on the 20th November, with service returning sporadically during that period. A core routing device experienced a fault that affected the internal BGP routing, which caused some of our RTP instances to have incorrect routing for UDP traffic. This led to call switching servers failing to respond to requests and forward calls, requiring each affected RTP machine to be restarted. 

The team continue to carry out tests and put plans in place to improve resilience should a similar fault occur in the future, and of course are constantly monitoring the network while we have this vulnerability. This work will continue throughout the day as a matter of utmost priority..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 20 Nov 2024 10:41:15 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cm3pr7pgw004m95zu3p2pv7cs</link>
  <guid>https://status.vipvoip.co.uk/incident/cm3pr7pgw004m95zu3p2pv7cs</guid>
</item>

<item>
  <title>Problem Sending Emails</title>
  <description>
    Type: Incident
    Duration: 3 hours and 45 minutes

    Affected Components: Management Portal
    Nov 5, 08:07:31 GMT+0 - Investigating - Our email provider is currently having problems delivering email reports and some voicemail emails. We have an open ticket with them and will update this page when we have a resolution to the problem. Nov 5, 10:20:50 GMT+0 - Monitoring - Email reports are now being sent as normal. We are still investigating issues sending voicemail emails. Nov 5, 11:52:35 GMT+0 - Resolved - All emails should now be sending as usual. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:07:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Our email provider is currently having problems delivering email reports and some voicemail emails. We have an open ticket with them and will update this page when we have a resolution to the problem..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:20:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Email reports are now being sent as normal. We are still investigating issues sending voicemail emails..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:52:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  All emails should now be sending as usual..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 5 Nov 2024 08:07:31 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cm34639m0002611hr6iwg8jgv</link>
  <guid>https://status.vipvoip.co.uk/incident/cm34639m0002611hr6iwg8jgv</guid>
</item>

<item>
  <title>Possible issues with shared server 5 - Cleared</title>
  <description>
    Type: Incident
    Duration: 33 minutes

    Affected Components: Voice Calls
    Sep 9, 09:26:11 GMT+0 - Investigating - We are aware of reports of some issues with one of our shared client servers

Our team are investigating and we will provide a further update shortly.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) Sep 9, 09:46:52 GMT+0 - Identified - We believe we have identified the cause of the issue with Shared server 5\. The server has been rebooted and we can see devices starting to connect back to the server again

Our team will continue to monitor and we will provide a further update shortly.

Please do not reply to this email, if you have any queries please contact us on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [**www.vipvoip.co.uk**](http://www.vipvoip.co.uk) Sep 9, 09:59:00 GMT+0 - Resolved - Following on from the earlier notices, the issue affecting one of our shared servers is now cleared. Our monitoring shows that the service is now stable.

The incident seems to have been related to connectivity within one of our datacentres.

Please do not reply to this email, if you have any queries please contact us on [support@vipvoip.co.uk](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk) 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 33 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:26:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of reports of some issues with one of our shared client servers

Our team are investigating and we will provide a further update shortly.

Please do not reply to this email, if you have any queries please contact us

on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:46:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We believe we have identified the cause of the issue with Shared server 5\. The server has been rebooted and we can see devices starting to connect back to the server again

Our team will continue to monitor and we will provide a further update shortly.

Please do not reply to this email, if you have any queries please contact us on [**support@vipvoip.co.uk**](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [**www.vipvoip.co.uk**](http://www.vipvoip.co.uk).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:59:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Following on from the earlier notices, the issue affecting one of our shared servers is now cleared. Our monitoring shows that the service is now stable.

The incident seems to have been related to connectivity within one of our datacentres.

Please do not reply to this email, if you have any queries please contact us on [support@vipvoip.co.uk](mailto:support@vipvoip.co.uk)

Kind regards

**VIP VoIP Support Team**

T: 03300 881182

W: [www.vipvoip.co.uk](http://www.vipvoip.co.uk).&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 9 Sep 2024 09:26:11 +0000</pubDate>
  <link>https://status.vipvoip.co.uk/incident/cm0ust4vw003slnnfkrk5hwtl</link>
  <guid>https://status.vipvoip.co.uk/incident/cm0ust4vw003slnnfkrk5hwtl</guid>
</item>

  </channel>
  </rss>