<?xml version="1.0" encoding="UTF-8" standalone="no"?>

 <feed xmlns="http://www.w3.org/2005/Atom">
  <title>Andrews &amp; Arnold Incidents Feed</title>
  <link href="https://aastatus.net/atom.cgi" rel="self" />
  <link href="https://aastatus.net/" />
  <id>https://aastatus.net/atom.cgi</id>
  <updated>2026-07-28T07:34:14+01:00</updated>
  <author>
   <name>Andrews &amp; Arnold</name>
   <email>support@aaisp.net.uk</email>
  </author>

  
   <entry>
    <title type="html">[PEW] Routers: LNS and BGP Router upgrades</title>
    <id>https://aastatus.net/42885</id>
    <link href="https://aastatus.net/apost.cgi?incident=42885" rel="alternate" />
    <updated>2026-07-28T07:34:14+01:00</updated>
    <published>2026-07-14T14:59:37+01:00</published>
    <category term="Routers" label="Routers" scheme="https://aastatus.net/type" />
    <category term="1" label="PEW" scheme="https://aastatus.net/severity" />
    <category term="Closed" label="Closed" scheme="https://aastatus.net/status" />
    <content type="html">
     &lt;b&gt;Started: 2026-07-16 03:00:00&lt;/b&gt;&lt;br /&gt;
     &lt;p&gt;We'll be performing routine overnight software upgrades on our pool of LNSs and BGP routers, starting Thursday 16th July. One LNS will be done per night, and this involves moving lines between the LNSs and upgrading when lines have been moved off. Customers may see a PPP drop and reconnect in the early hours of the morning as this work is carried out.&#13;&#10;&lt;/p&gt;&lt;p&gt;&#13;&#10;Upgrades to our BGP routers will also happen overnight but should have little to no impact. &lt;/p&gt;
     &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 19 Jul 2026 09:07:48&lt;/b&gt; LNS moves will be starting from Monday morning. We have 9 LNSs named a to i. The upgrade is happening in reverse order one per night. Customers on i will be moved off first. 
     &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Resolution&lt;/b&gt; Our pool of LNS routers have completed their round of upgrades and so have the majority of our other routers.
     
    </content>
   </entry>
  
   <entry>
    <title type="html">[Minor] VoIP and SIMs: SIP2SIM Network Connectivity</title>
    <id>https://aastatus.net/42884</id>
    <link href="https://aastatus.net/apost.cgi?incident=42884" rel="alternate" />
    <updated>2026-07-16T08:19:16+01:00</updated>
    <published>2026-07-14T09:47:01+01:00</published>
    <category term="VoIP and SIMs" label="VoIP and SIMs" scheme="https://aastatus.net/type" />
    <category term="2" label="Minor" scheme="https://aastatus.net/severity" />
    <category term="Closed" label="Closed" scheme="https://aastatus.net/status" />
    <content type="html">
     &lt;b&gt;Started: 2026-07-14 09:00:00&lt;/b&gt;&lt;br /&gt;
     From our SIP2SIM carrier: We are investigating over night reports of network access problems over various geographical locations. (This is affecting a very small number of our customers)
     &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 14 Jul 2026 10:36:53&lt;/b&gt; From the carrier: Engineers are working on a resolution. We are in regular contact with them and will continue to provide updates as soon as we receive further information.&#13;&#10;&#13;&#10;At this time, we do not have an estimated time for resolution.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 14 Jul 2026 12:33:10&lt;/b&gt; Our upstream carrier continues to work on the incident, with engineering teams actively investigating the underlying cause and implementing corrective measures.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 14 Jul 2026 14:22:29&lt;/b&gt; A recent routing change has been identified as a possible cause and a roll back is being implemented. Whilst the root cause has not been fully confirmed engineers are working on an alternative workaround.&#13;&#10;&#13;&#10;Further updates to follow.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 14 Jul 2026 17:58:04&lt;/b&gt; Our carrier is still working through the resolution steps previously mentioned and investigating the root cause.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 14 Jul 2026 20:29:27&lt;/b&gt; The cause has been narrowed to a routing change made by an upstream carrier partner. A mitigation was implemented this evening and has resolved the registration issues for users connecting over 4G/VoLTE. Thos affected by this should now be back in service.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 15 Jul 2026 08:59:58&lt;/b&gt; A mitigation was implemented this evening (approx 19:00) and has resolved the registration issues for users connecting over 4G/VoLTE. Service for the majority of users should now be back to normal.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 15 Jul 2026 09:26:02&lt;/b&gt; Some of our customers are reporting their services still are not working - these are being investigated. &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update 15 Jul 2026 12:28:01&lt;/b&gt; &lt;p&gt;SIP2SIM customers where we register to your own PBX are affected by a separate problem to that of the carrier....&#13;&#10;&lt;/p&gt;&#13;&#10;&lt;p&gt;the carrier's problem was fixed yesterday evening, and we have a manual work-around for customers who have their own PBX - please contact support.&#13;&#10;&lt;/p&gt;
     &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Resolution&lt;/b&gt; Service fully restored.
     
    </content>
   </entry>
  
   <entry>
    <title type="html">[Minor] Routing: IPv6 routing</title>
    <id>https://aastatus.net/42883</id>
    <link href="https://aastatus.net/apost.cgi?incident=42883" rel="alternate" />
    <updated>2026-07-03T10:19:45+01:00</updated>
    <published>2026-07-02T11:08:52+01:00</published>
    <category term="Routing" label="Routing" scheme="https://aastatus.net/type" />
    <category term="2" label="Minor" scheme="https://aastatus.net/severity" />
    <category term="Closed" label="Closed" scheme="https://aastatus.net/status" />
    <content type="html">
     &lt;b&gt;Started: 2026-07-02 11:00:00&lt;/b&gt;&lt;br /&gt;
     We're investigating a problem with IPv6 routing
     &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update  2 Jul 2026 11:13:19&lt;/b&gt; Routing is recovering and we're investigating the cause.
     
     
    </content>
   </entry>
  
 </feed>

