<?xml version="1.0" encoding="utf-8" standalone="yes"?>
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      
      <title>X4B Network Status</title>
      <link>https://status.x4b.net/</link>
      <description>Incident history</description>
      <generator>github.com/cstate</generator>
      <language>en</language>
      
      <lastBuildDate>Wed, 04 Mar 2026 09:20:00 +0000</lastBuildDate>
      
      
      
        <atom:link href="https://status.x4b.net/index.xml" rel="self" type="application/rss+xml" />
      
      
      
        <item>
          <title>[Resolved] Outage CH</title>
          <link>https://status.x4b.net/issues/2026-03-04-outage-ch/</link>
          <pubDate>Wed, 04 Mar 2026 09:20:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2026-03-04-outage-ch/</guid>
          <category>2026-03-04T11:02:00.000Z</category>
          <description>&lt;p&gt;Server in Switzerland appears offline. Upstream is investigating.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Dallas migration</title>
          <link>https://status.x4b.net/issues/2026-02-21-dallas-migration/</link>
          <pubDate>Mon, 23 Feb 2026 15:55:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2026-02-21-dallas-migration/</guid>
          <category>2026-02-24T07:11:00.000Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Routes have been restored&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Routes have been pulled. Maintenance starting.&lt;/p&gt;
&lt;p&gt;Upstream provider has requested that we move our servers to a different cabinet. Server will be moved via offline imaging by their technicians.&lt;/p&gt;
&lt;p&gt;We do not know exactly how long it will take but we expect a couple hours. We will be around to check services before restoring routes.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Brazil Maintenance</title>
          <link>https://status.x4b.net/issues/2026-02-05-brazil-maintenance/</link>
          <pubDate>Mon, 09 Feb 2026 03:50:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2026-02-05-brazil-maintenance/</guid>
          <category>2026-02-09T06:51:00.000Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; We have confirmed the upstream techs work and restored routes.&lt;/p&gt;
&lt;p&gt;Upstream provider has requested that we move our servers to a different cabinet. Server will be moved via offline imaging by their technicians.&lt;/p&gt;
&lt;p&gt;We do not know exactly how long it will take but we expect a couple hours. We will be around to check services before restoring routes.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Hardware Replacement</title>
          <link>https://status.x4b.net/issues/2026-01-29-hardware-replacement/</link>
          <pubDate>Wed, 04 Feb 2026 01:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2026-01-29-hardware-replacement/</guid>
          <category>2026-02-04T12:03:00.000Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Routes have been restored. If you encounter any issues please do let us know&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; We are still working on this. Currently running behind schedule. Hoping to have this done tonight.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Currently waiting on upstream technicians to do their side. We are hoping for everything to be done tonight. Once upstream side is done we will complete testing &amp;amp; QA and proceed accordingly.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; We are still working on this. Currently running behind schedule. Hoping to have this done by 7pm tonight.&lt;/p&gt;
&lt;p&gt;Upstream has requested that we move our hardware to a new area of the datacenter. To facilitate that we are going to experience an interruption. We have been requested to do this via a system migration.&lt;/p&gt;
&lt;p&gt;To facilitate this we will be taking Singapore routes down from midday AEST on Wednesday. We estimate that it will take 4-5 hours to complete.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] London GTT packet loss</title>
          <link>https://status.x4b.net/issues/2025-12-09-london-gtt-packet-loss/</link>
          <pubDate>Tue, 09 Dec 2025 02:28:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-12-09-london-gtt-packet-loss/</guid>
          <category>2025-12-09T02:44:00.000Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Looks to be clearing. Routes are being restored.&lt;/p&gt;
&lt;p&gt;Packet loss has been detected on routes ingressing via GTT. We are temporarily removing london from the mix while we await GTT resolution.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Routing issues</title>
          <link>https://status.x4b.net/issues/2025-12-04-routing-issues/</link>
          <pubDate>Thu, 04 Dec 2025 01:36:36 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-12-04-routing-issues/</guid>
          <category>2025-12-04T04:30:28.777Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; All servers functional. Appologies for the resolution time, this was an incredibly difficult issue to resolve that required IPMI access to each server.&lt;/p&gt;
&lt;p&gt;We are aware some locations are having issues currnetly. We have disabled the identified problematic locations.&lt;/p&gt;
&lt;p&gt;We are working on it.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] AMS issue</title>
          <link>https://status.x4b.net/issues/2025-11-20-ams-issue/</link>
          <pubDate>Thu, 20 Nov 2025 03:17:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-11-20-ams-issue/</guid>
          <category>2025-11-20T03:30:00.000Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; issue resolved&lt;/p&gt;
&lt;p&gt;We have pulled routes from AMS while an indicident affecting the region is investigated&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Software Upgrades: Anycast</title>
          <link>https://status.x4b.net/issues/2025-11-11-software-upgrades-anycast/</link>
          <pubDate>Mon, 17 Nov 2025 22:30:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-11-11-software-upgrades-anycast/</guid>
          <category>2025-11-18T00:30:00.000Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; as of 11:39AM all done.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; as of 11:15AM&lt;/p&gt;
&lt;p&gt;All servers other than LON are complete pending final review.&lt;/p&gt;
&lt;p&gt;Hopefully will be done before lunch.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; as of 10:15AM&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;SYD, SG, LAX are complete pending final review&lt;/li&gt;
&lt;li&gt;JP, MIA, DAL are currently in progress&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; As a reminder this is starting tomorrow at 9:30 AM AEDT. We expect it will take approximately 1 hour per server (for all 11 servers)&lt;/p&gt;
&lt;p&gt;It is expected that maintenance will take approximately 1 hour per server. No interruption is expected however risk does exist. We will be updating a couple servers at a time.&lt;/p&gt;
&lt;p&gt;There is the chance that we will need to do the update of some servers the following day. However the plan is to get all the servers done in one day if possible.&lt;/p&gt;
&lt;p&gt;This is the same update that has already been performed on the budget line.&lt;/p&gt;
&lt;p&gt;We will update this announcment when maintenance for each region is complete. Thank you for your patience.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] HTTP Log information</title>
          <link>https://status.x4b.net/issues/2025-11-12-http-log-information/</link>
          <pubDate>Wed, 12 Nov 2025 05:07:17 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-11-12-http-log-information/</guid>
          <category>2025-11-12T05:42:03.702Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; system is fixed. Appears to be a bug in the version of vector deployed at the edge. We have resolved the situation for now and will look into a software update and/or fix tomorrow.&lt;/p&gt;
&lt;p&gt;We are investigating an information collecting HTTP information (requests, error logs).&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Software Upgrades</title>
          <link>https://status.x4b.net/issues/2025-11-07-software-upgrades/</link>
          <pubDate>Mon, 10 Nov 2025 22:30:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-11-07-software-upgrades/</guid>
          <category>2025-11-11T00:55:19.795Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; NY done. All Done. If you have any issues please do let us know.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Vegas done. Sorry that one was a bit less smooth.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Switzerland done.&lt;/p&gt;
&lt;p&gt;We will be performing system software updates on Tuesday (AEDT).&lt;/p&gt;
&lt;p&gt;It is expected that maintenance will take a couple hours per server. No interruption is expected however risk does exist.&lt;/p&gt;
&lt;p&gt;We will update this announcment when maintenance is complete. Thank you for your patience.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Maintenance</title>
          <link>https://status.x4b.net/issues/2025-11-06-maintenance/</link>
          <pubDate>Fri, 07 Nov 2025 00:30:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-11-06-maintenance/</guid>
          <category>2025-11-07T02:07:35.898Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; complete&lt;/p&gt;
&lt;p&gt;We will be performing upgrades of our BGP software. During this upgrade we will restart all sessions. No interruption is expected however a short routing blip is possible.&lt;/p&gt;
&lt;p&gt;We will do PoPs in sequence&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] NTT Brazil</title>
          <link>https://status.x4b.net/issues/2025-11-05-ntt-brazil/</link>
          <pubDate>Wed, 05 Nov 2025 00:10:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-11-05-ntt-brazil/</guid>
          <category>2025-11-05T03:31:29.227Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Resolved. Issue was related to outgoing routes via Algar.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Issue appears to be on NTT&amp;rsquo;s side. Ticket is open with NTT.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Brazil outage</title>
          <link>https://status.x4b.net/issues/2025-10-10-brazil-outage/</link>
          <pubDate>Thu, 09 Oct 2025 22:29:45 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-10-10-brazil-outage/</guid>
          <category>2025-10-10T01:35:22.991Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Upstream have confirmed the issue as a power issue affecting core router. It is being worked on.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information. Traffic is routed around the PoP.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Ashburn Emergency Maintenance</title>
          <link>https://status.x4b.net/issues/2025-09-01-ashburn-emergency-maintenance/</link>
          <pubDate>Tue, 02 Sep 2025 13:00:29 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-09-01-ashburn-emergency-maintenance/</guid>
          <category>2025-09-02T17:00:29.994Z</category>
          <description>&lt;p&gt;&lt;em&gt;Upstream has just notified us&lt;/em&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Please be advised that emergency network maintenance is scheduled at our Ashburn location to perform an Core router hardware upgrade aimed at improving network redundancy and stability.&lt;br&gt;
Maintenance Window:&lt;br&gt;
 Date: Tuesday, Sept 2, 2025&lt;br&gt;
 Time: 6:00 AM – 10:00 AM PDT&lt;br&gt;
 Duration : - 10-20 Minutes&lt;br&gt;
&lt;br&gt;
Expected Impact:&lt;br&gt;
A brief 10–15 minute service interruption may occur during the upgrade process. We will work to minimize downtime and restore services as quickly as possible.&lt;br&gt;
We appreciate your understanding and patience as we implement these enhancements to strengthen our network infrastructure.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;We will route around the maintenance for anycast product lines.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Reduced quality of EU routes</title>
          <link>https://status.x4b.net/issues/2025-08-27-reduced-quality-of-eu-routes/</link>
          <pubDate>Wed, 27 Aug 2025 02:02:17 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-08-27-reduced-quality-of-eu-routes/</guid>
          <category>2025-08-27T08:26:55.459Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; issue was found upstream and resolved. Upstream will update their internal documentation to prevent recurrance.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Appears to be a GTT fault. Fault ticket has been opened.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Investigation continues upstream. This issue only appears to affect Premium Anycast customers. Standard Anycast routes seem unaffected.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. It appears to be a bug in the upstream providers routing configuration. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Recaptcha Depreciation</title>
          <link>https://status.x4b.net/issues/2025-08-12-recaptcha-depreciation/</link>
          <pubDate>Tue, 12 Aug 2025 04:29:29 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-08-12-recaptcha-depreciation/</guid>
          <category>2025-08-12T04:29:29.120Z</category>
          <description>&lt;p&gt;We are depreciating Recaptcha &amp;amp; recaptcha fallback for validation pages. Currently recaptcha is in use for less than 0.01% of all verification page requests so far in 2025 and with the exception of an attack utilizing a captcha solver (a growing risk that will be mitigated by removal) was similarly represented in 2024.&lt;/p&gt;
&lt;p&gt;If any customer requires a no-javascript verification page they may contact us and we will see what we can do, however its our current belief given the analytics gathered from user agents and usage of the default PoW verification system that this is below a significant number.&lt;/p&gt;
&lt;p&gt;We will of course be adding an appropriate message for clients without javascipt enabled when Recaptcha fallback &amp;amp; support is removed before the end of 2025.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Budget Line Disrupted (US-EAST)</title>
          <link>https://status.x4b.net/issues/2025-07-29-budget-line-disrupted/</link>
          <pubDate>Tue, 29 Jul 2025 10:14:47 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-07-29-budget-line-disrupted/</guid>
          <category>2025-07-29T10:14:47.651Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; No upstream updates at this time.&lt;/p&gt;
&lt;p&gt;Upstream network for all three PoPs has a reported interruption in New York. New York has been routed around sucessfully according to our observations.&lt;/p&gt;
&lt;p&gt;Eastern US may experience higher than expected latency until the situation is resolved.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Cloud Service outage</title>
          <link>https://status.x4b.net/issues/2025-07-27-cloud-service-outage/</link>
          <pubDate>Sun, 27 Jul 2025 11:08:06 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-07-27-cloud-service-outage/</guid>
          <category>2025-07-29T04:51:41.609Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; No update from Akamai yet but we are seeing Kubernetes nodes that were offline return to function slowly starting around 5 minutes ago.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; We currently await Akamai to fix their internal networking. 4/12 of our cluster nodes are currently online. The panel is up but slow. Some non essential services that rely on inter-node communication are degraded.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Panel is currently very slow due to 70% of cloud nodes being offline currently. We await Akamai&amp;rsquo;s resolution to their datacenter outage.&lt;/p&gt;
&lt;p&gt;We apologise for the inconvenience and are doing everything we can to return to 100%. Even including moving our services to another vendor.&lt;/p&gt;
&lt;p&gt;If you would like to follow the &lt;a href=&#34;https://status.linode.com/incidents/6yw88b0ft94g&#34;&gt;upstream issue&lt;/a&gt; you may.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; We will be keeping this incident open for now as we are still seeing substantially lowered performance in the region and half of our cluster nodes are still unavailable. The panel is however online.&lt;/p&gt;
&lt;p&gt;We continue to monitor the &lt;a href=&#34;https://status.linode.com/incidents/6yw88b0ft94g&#34;&gt;upstream issue&lt;/a&gt; and await resolution.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; We will be keeping this incident open for now as we are still seeing substantially lowered performance in the region and some of our cluster nodes are still unavailable. The panel is however online.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Holy Smokes Akamai that was a long one. Services are restored. We are going through and checking everything in line with our DRP.&lt;/p&gt;
&lt;p&gt;Upstream Update -
Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.&lt;/p&gt;
&lt;p&gt;Upstream Update -
Identified - Our team has identified the issue affecting connectivity in our US-EAST (Newark) data center. The issue is related to heating/cooling complications in the data center due to a power outage . The power outage has been fixed and we are working quickly to bring our services back online, and we will provide an update as soon as the solution is in place.&lt;/p&gt;
&lt;p&gt;Upstream currently has an outage affecting their US-EAST PoP where our core cloud (web panel, data collection, etc) is homed. This does not affect customer services are all essential services (BGP, route validation, mitigation analysis) is multi-homed. Email delivery (i.e on DDoS attack) will not be available until service restored.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;Investigating - Our team is investigating an emerging service issue affecting All Services in US-EAST (Newark). We will share additional updates as we have more information.&amp;rdquo;&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] LUX: Migrating to Switzerland</title>
          <link>https://status.x4b.net/issues/2025-07-26-lux-migrating-to-switzerland/</link>
          <pubDate>Sat, 26 Jul 2025 14:06:45 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-07-26-lux-migrating-to-switzerland/</guid>
          <category>2025-07-26T14:01:45.207Z</category>
          <description>&lt;p&gt;Luxembourg services are moving to Switzerland. Our upstream in the region is co-ordinating the move.&lt;/p&gt;
&lt;p&gt;No substantial interruption is expected for the move as we will do a live migration.&lt;/p&gt;
&lt;p&gt;Appologies for the short notice. While we knew this was planned we were not informed until just now of the exact details.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] LUX interruption</title>
          <link>https://status.x4b.net/issues/2025-07-26-lux-interruption/</link>
          <pubDate>Sat, 26 Jul 2025 13:18:31 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-07-26-lux-interruption/</guid>
          <category>2025-07-27T11:20:23.547Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Looks like theres an interuption currently. No information yet provided from upstream on current or previous interruptions.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; No interruptions today. Upstream really messed up communication on this one. They will be emailing everyone over the next couple of days at which time we will know more. The next couple of days may have some network noise but is generally expected to be fine.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt;. No information currently from upstream. Will leave open as more interruptions are posssible during the night.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Appears down again.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Upstream reports resolved through early moving our hardware to Switzerland.&lt;/p&gt;
&lt;p&gt;Luxembourg network issues affecting Budget Line Luxembourg services currently.&lt;/p&gt;
&lt;p&gt;No information currently on the cause or status.&lt;/p&gt;
&lt;p&gt;Services will return online when upstream resolves.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Software Updates (Anycast)</title>
          <link>https://status.x4b.net/issues/2025-07-22-software-updates-anycast/</link>
          <pubDate>Tue, 22 Jul 2025 23:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-07-22-software-updates-anycast/</guid>
          <category>2025-07-23T00:03:22.113Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Complete&lt;/p&gt;
&lt;p&gt;We will be performing system upgrades on Wednesday. No interruption is expected.&lt;/p&gt;
&lt;p&gt;Systems will be done in parallel in groups with an estimated total risk of interruption period per server of 30 minutes.&lt;/p&gt;
&lt;p&gt;This is the same upgrade that was carried out on the budget line last week without interruption.&lt;/p&gt;
&lt;p&gt;If any interruption or unexpected event occurs we will update this incident.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Software Updates (Budget Line)</title>
          <link>https://status.x4b.net/issues/2025-07-16-software-updates-budget-line/</link>
          <pubDate>Thu, 17 Jul 2025 23:56:30 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-07-16-software-updates-budget-line/</guid>
          <category>2025-07-18T00:17:47.711Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Complete&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Started&lt;/p&gt;
&lt;p&gt;We will be performing system upgrades on Friday. No interruption is expected.&lt;/p&gt;
&lt;p&gt;Systems will be done in parallel with an estimated total risk of interruption period per server of 30 minutes.&lt;/p&gt;
&lt;p&gt;If any interruption or unexpected event occurs we will update this incident.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Autossl issues </title>
          <link>https://status.x4b.net/issues/2025-07-11-autossl-issues/</link>
          <pubDate>Fri, 11 Jul 2025 09:39:54 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-07-11-autossl-issues/</guid>
          <category>2025-07-13T00:56:26.667Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Looks resolved. We will continue to monitor.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - Issue seems to have been limited to 13/37k certificates we generate. We beleive this was caused by an increase in errors due to a large number of bad certificate generations being attempted.&lt;/p&gt;
&lt;p&gt;We have made some changes and are monitoring. Please let us know if you have any issues.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] AMS: Scheduled Maintenance</title>
          <link>https://status.x4b.net/issues/2025-06-03-ams-scheduled-maintenance/</link>
          <pubDate>Thu, 05 Jun 2025 08:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-06-03-ams-scheduled-maintenance/</guid>
          <category>2025-06-05T10:00:00.000Z</category>
          <description>&lt;p&gt;Our upstream datacenter has notified us today of upcoming maintenance in Amsterdam.&lt;/p&gt;
&lt;p&gt;Network engineers will be upgrading top-of-rack switches and reworking some of the network topologies for a more robust and stable overall network in the server cabinet.&lt;/p&gt;
&lt;p&gt;Though the outage is not expected to last more than 5 to 10 minutes, the work window will be longer as our team will test and ensure connectivity is stable before completing the maintenance.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Maintenance Details&lt;/strong&gt;&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Day/Date: Thursday, June 05th, 2025
Start Time: 6:00 AM (PDT)
End Time: 8:00 AM (PDT)
Outage Estimated Duration:  5-10 mins
Effect: Short Outage
Facilities: AM11
Device Description: 0818.16.Black
&lt;/code&gt;&lt;/pre&gt;</description>
        </item>
      
        <item>
          <title>[Resolved] AMS Interruption</title>
          <link>https://status.x4b.net/issues/2025-05-30-ams-interruption/</link>
          <pubDate>Fri, 30 May 2025 13:58:47 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-05-30-ams-interruption/</guid>
          <category>2025-06-03T10:26:53.081Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Hardware has been replaced upstream and we have restored routes. Sorry for any interruption over the past 5 minutes we had a limited window for restoration while under the eye of upstream NOC today.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Upstream confirms that the issue is taking longer than expected to resolve. We continue to route around the issue.&lt;/p&gt;
&lt;p&gt;Upstream has confirmed an interruption in AMS affecting firewalled TCP traffic. We have pulled routes from the region until incident confirmed over.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Dallas: Network Maintenance</title>
          <link>https://status.x4b.net/issues/2025-05-14-dallas-network-maintenance/</link>
          <pubDate>Mon, 19 May 2025 09:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-05-14-dallas-network-maintenance/</guid>
          <category>2025-05-19T09:08:47.588Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Maintenance complete. Routes restored.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Pulling network routes.&lt;/p&gt;
&lt;p&gt;Upstream network is performing maintenance on our network slice. We will take this time to do some long delayed network configuration changes brining this location into sync with other locations configuration.&lt;/p&gt;
&lt;p&gt;We expect 15 minutes of interruption in Dallas during this time. We will pull routes from the region in advance of the maintenance. We will update on status here.&lt;/p&gt;
&lt;p&gt;Should there be any issues we will keep routes pulled until resolved however interruption is expected to be minimal.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Issues with Akamai</title>
          <link>https://status.x4b.net/issues/2025-03-30-issues-with-linode/</link>
          <pubDate>Sun, 30 Mar 2025 11:29:49 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-03-30-issues-with-linode/</guid>
          <category>2025-03-31T00:06:16.136Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Although we are yet to receive a response the issue has been resolved now for nearly 6 hours. As such we will mark as resolved.&lt;/p&gt;
&lt;p&gt;Some services are affected by a service interruption with Linode (likely related to &lt;a href=&#34;https://status.linode.com/incidents/x14zys0wddxk)&#34;&gt;https://status.linode.com/incidents/x14zys0wddxk)&lt;/a&gt;. We opened a ticket 5 hours ago when it appeared as a minor issue on our monitoring however are yet to receive a response. Certain dashboard features are interrupted during this time.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Dallas: Potential issue with Cogent</title>
          <link>https://status.x4b.net/issues/2025-03-10-dallas-potential-issue-with-cogent/</link>
          <pubDate>Mon, 10 Mar 2025 09:40:07 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2025-03-10-dallas-potential-issue-with-cogent/</guid>
          <category>2025-04-15T11:05:28.830Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Upstream has installed a workaround and is looking to drop cogent in the near future. We have been able to restore routes to Dallas PoP. If you encounter any Dallas issues please let us know.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; We still await upstream fix&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information. We have removed Dallas from Anycast mixes while we await upstream feedback.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Block Storage outage</title>
          <link>https://status.x4b.net/issues/2024-12-05-block-storage-outage/</link>
          <pubDate>Thu, 05 Dec 2024 07:05:41 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-12-05-block-storage-outage/</guid>
          <category>2024-12-05T07:56:56.593Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Panel restored.&lt;/p&gt;
&lt;p&gt;An outage at our cloud service provide is affecting the web panel.&lt;/p&gt;
&lt;p&gt;No customer services are affected. Panel access will be restored when upstream resolves issue.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] LA: Fault</title>
          <link>https://status.x4b.net/issues/2024-10-24-la-fault/</link>
          <pubDate>Thu, 24 Oct 2024 09:42:25 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-10-24-la-fault/</guid>
          <category>2024-12-03T03:40:50.534Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Routes have been restored as Cogent have resolved the issue.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Upstream response: They are working with Cogent and hope to have a solution in a couple days. We will keep the routes removed from LAX until fixed.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt; We are aware of a fault upstream in LA. While we wait on resulution we have pulled all routes from the region.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Paypal payments delayed</title>
          <link>https://status.x4b.net/issues/2024-10-16-paypal-payments-delayed/</link>
          <pubDate>Tue, 15 Oct 2024 00:53:48 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-10-16-paypal-payments-delayed/</guid>
          <category>2024-10-24T09:47:45.711Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Still yet to receive any solution from Paypal. Only an acknowledgement of suspected fault on their end.&lt;/p&gt;
&lt;p&gt;We are processing payments through our workaround as per normal. However there is still some element of unknown until paypal resolve the actual issue (which appears to be issues specifically with our x4b.net domain name)&lt;/p&gt;
&lt;p&gt;As this issue does not have any known customer impact we are going to bring it to a close now.&lt;/p&gt;
&lt;p&gt;Should you experience any delayed payments (either immeidately, or after 3 hours when the new correlation script can recover any missed payments) via paypal let us know and we will sort it out.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Still yet to receive any solution from Paypal.&lt;/p&gt;
&lt;p&gt;Our Transaction log check job remains in place. Having discovered a suspected workaround to the Paypal IPN system bug have implemented a workaround that appears to enable IPNs to be sent again. We will continue to run both.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Still yet to receive any solution from Paypal.&lt;/p&gt;
&lt;p&gt;We have implemented a payment check job which is able to import payments made once they are available via Paypal REST api (up to 3 hours). We understand this is inconvenient however at this time it is what we have available to us.&lt;/p&gt;
&lt;p&gt;Paypal&amp;rsquo;s IPN system has abruptly stopped communicating with us and we await a serious response from Paypal on this matter.&lt;/p&gt;
&lt;p&gt;Stripe (Credit Card) and Crypto payments are unaffected. If you need to make an urgent payment we strongly recommend using Stripe until this matter can be resolved.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - Still yet to receive any solution from Paypal.&lt;/p&gt;
&lt;p&gt;Transactions are being manually processed in a priority queue. Open a support ticket if you need manual processing urgently.&lt;/p&gt;
&lt;p&gt;We are working on a temporary solution to reduce the delay to ~5-10 minutes while we wait on a fix from Paypal.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are aware of delays processing paypal payments. We have contacted Paypal merchant support for a fix and are awaiting a response.&lt;/p&gt;
&lt;p&gt;If you need a payment manually processed open a support ticket including a screenshot of your payment and we will get to it ASAP.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Lux: offline event </title>
          <link>https://status.x4b.net/issues/2024-10-08-lux-offline-event/</link>
          <pubDate>Tue, 08 Oct 2024 14:37:17 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-10-08-lux-offline-event/</guid>
          <category>2024-10-08T20:07:05.103Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Upstream router had a major issue interrupting services to all in Luxembourg.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Ashburn offline</title>
          <link>https://status.x4b.net/issues/2024-08-23-ashburn-offline/</link>
          <pubDate>Fri, 23 Aug 2024 02:10:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-08-23-ashburn-offline/</guid>
          <category>2024-08-23T02:40:39.509Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; We have made adjustments to the VLAN routing and have restored service in Ashburn.&lt;/p&gt;
&lt;p&gt;Zayo maintenance on the dark fiber within the network is interrupting service. We are working on a temporary fix to re-route currently.&lt;/p&gt;
&lt;p&gt;Routes have been pulled during the issue.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Sydney: routes pulled</title>
          <link>https://status.x4b.net/issues/2024-07-17-sydney-routes-pulled/</link>
          <pubDate>Thu, 11 Jul 2024 13:25:03 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-07-17-sydney-routes-pulled/</guid>
          <category>2024-07-27T15:14:18.226Z</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - We have been informed that the replacement parts for the failed upstream router have arrived. They will be getting installed on Friday.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] UK Migration 04/06 - 05/06</title>
          <link>https://status.x4b.net/issues/2024-05-29-uk-migration-04-06-05-06/</link>
          <pubDate>Tue, 04 Jun 2024 10:10:22 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-05-29-uk-migration-04-06-05-06/</guid>
          <category>2024-06-06T01:50:54.183Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Routes are live. Migration is complete.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Server has been installed in the new DC. Just waiting on some network updates to be made before routes can be made live.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Server de-racking has begun. Due to the risk of reboots as fibers are moved we have decided that we will be removing routes until the hazard is cleared. Routes have already been removed in advance of our sever being de-racked.&lt;/p&gt;
&lt;p&gt;O﻿ur server will be getting physically moved to a new datacenter between these dates. This will help us combat issues observed over the past few months including:&lt;/p&gt;
&lt;p&gt;﻿- Increased temperature within the cage our server is in&lt;/p&gt;
&lt;p&gt;﻿- Replacement of a failing switch (this has been responsible for a few 5-10s per week interruptions over the past month)&lt;/p&gt;
&lt;p&gt;E﻿xpected interuption is likely just a couple hours, however depending on when we get scheduled we may restrict routes before / after depending on the availability of our technicians to verify / prepare. We are relying on remote hands and a significant number of servers are being moved during this time so we do not at this stage know our exact time.&lt;/p&gt;
&lt;p&gt;W﻿e will aim to revise the scheduled time however to reduce the range closer to the event.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Dallas storm</title>
          <link>https://status.x4b.net/issues/2024-05-26-dallas-storm/</link>
          <pubDate>Sun, 26 May 2024 12:15:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-05-26-dallas-storm/</guid>
          <category>2024-05-26T19:57:28.115Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] UK / LON removal (temporary)</title>
          <link>https://status.x4b.net/issues/2024-04-13-uk-lon-removal-temporary/</link>
          <pubDate>Sat, 13 Apr 2024 12:28:14 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-04-13-uk-lon-removal-temporary/</guid>
          <category>2024-04-18T01:58:46.394Z</category>
          <description>&lt;p&gt;&lt;em&gt;﻿&lt;/em&gt;Update** LON1 is being restored to the mix. Upstream techs have been able to repair the existing switch (replaced fan). We have monitored the switch for the past 48-hours after fan replacement and has been reliable.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;We observed that the onsite fans were ineffective, but the replacement fan we dispatched has proven successful. At present, the switch seems to be operating reliably, and we&amp;rsquo;ve been actively monitoring its performance.&amp;quot;&lt;/p&gt;
&lt;p&gt;-﻿&amp;mdash;&lt;/p&gt;
&lt;p&gt;We are temporarily removing LON1 from the anycast mix due to recurring issues with a fa﻿iling switch.&lt;/p&gt;
&lt;p&gt;U﻿pstream techs have assured us the replacement switch is on its way however to prevent further short disruptions we are removing the location temporarily.&lt;/p&gt;
&lt;p&gt;R﻿outes to LON will be restored once the new switch is installed.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Scheduled Maintenance on Datastore</title>
          <link>https://status.x4b.net/issues/2024-02-07-scheduled-maintenance-on-datastore/</link>
          <pubDate>Wed, 07 Feb 2024 23:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-02-07-scheduled-maintenance-on-datastore/</guid>
          <category>2024-02-08T04:00:00.000Z</category>
          <description>&lt;p&gt;We will be performing maintenance on the Datastore powering access logs, error logs, ssl logs and the filtering report tomorrow.&lt;/p&gt;
&lt;p&gt;N﻿o significant interruption is expected however reduced performance and minor disruptions are likely.&lt;/p&gt;
&lt;p&gt;S﻿lightly reduced performance may occur tonight as we prepare for the update.&lt;/p&gt;
&lt;p&gt;I﻿t is possible that data collected during this time may be under representative of actual traffic and patterns.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] London Core Router Software Update</title>
          <link>https://status.x4b.net/issues/2024-02-01-london-core-router-software-update/</link>
          <pubDate>Fri, 02 Feb 2024 14:00:05 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-02-01-london-core-router-software-update/</guid>
          <category>2024-02-04T00:32:32.180Z</category>
          <description>&lt;p&gt;Maintenance Details:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Activity: Core Router Software Update
Impact: Temporary Service Interruptions
Duration: Up to 30 to 60 minutes
Date: Feb 03 2024
Maintenance Window: 1:00 PM GMT to 9:00 PM GMT
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Details:
During the specified maintenance window, our team will be performing a critical update to the Juniper code on our core router. This update is essential to enhance network performance, security, and overall stability.&lt;/p&gt;
&lt;p&gt;Expected Impact:
While we strive to minimize disruptions, it is anticipated that your services will experience interruptions during this maintenance window. The expected downtime is estimated to be within the range of 30 to 60 minutes. We understand the importance of your services and will work diligently to complete the update as quickly as possible.&lt;/p&gt;
&lt;p&gt;Action Required:
To minimize any inconvenience, we recommend scheduling critical tasks outside the maintenance window or notifying relevant parties within your organization.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Network Maintenance</title>
          <link>https://status.x4b.net/issues/2024-02-01-network-maintenance/</link>
          <pubDate>Thu, 01 Feb 2024 08:08:16 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-02-01-network-maintenance/</guid>
          <category>2024-02-02T09:01:22.629Z</category>
          <description>&lt;p&gt;There will be network maintenance carried out affecting US &amp;amp; EU PoPs of the Standard and Premium anycast networks within the next 24-hours.&lt;/p&gt;
&lt;p&gt;O﻿ur upstream is making changes to their transit mix. We will be adjusting our network profile accordingly.&lt;/p&gt;
&lt;p&gt;S﻿ome degree of interruption is inevatable. Please feel free to report any problematic routes if we fall behind on resolving them during the maintenance period.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Singapore: Emergency Maintenance</title>
          <link>https://status.x4b.net/issues/2024-01-24-singapore-emergency-maintenance/</link>
          <pubDate>Wed, 24 Jan 2024 20:16:20 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-01-24-singapore-emergency-maintenance/</guid>
          <category>2024-01-24T20:26:27.090Z</category>
          <description>&lt;p&gt;&lt;em&gt;﻿Update&lt;/em&gt; - Problem appears resolved. We will continue to observe for any regression.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Dashboard &amp; Website offline</title>
          <link>https://status.x4b.net/issues/2024-01-17-dashboard-website-offline/</link>
          <pubDate>Wed, 17 Jan 2024 09:01:18 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-01-17-dashboard-website-offline/</guid>
          <category>2024-01-17T11:16:02.124Z</category>
          <description>&lt;p&gt;&lt;em&gt;﻿Update&lt;/em&gt; - Vendor informs us that service is restored and is continuing to monitor (&lt;a href=&#34;https://status.linode.com/incidents/cv0y0409nl7f&#34;&gt;https://status.linode.com/incidents/cv0y0409nl7f&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;W﻿e confirm our services website and assosiated dashboard services are back online.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;﻿Update&lt;/em&gt; - Vendor has informed us that its an issue affecting all Block Storage in the Newyork Region and that we should expect an update soon.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - Block Storage failure affecting our database server currently has the panel offline.&lt;/p&gt;
&lt;p&gt;W﻿e have made the vendor aware and are awaiting a fix.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Chicago: Offline</title>
          <link>https://status.x4b.net/issues/2024-01-15-chicago-offline/</link>
          <pubDate>Mon, 15 Jan 2024 11:39:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2024-01-15-chicago-offline/</guid>
          <category>2024-01-15T05:47:59.651Z</category>
          <description>&lt;p&gt;Equinix IBX Site Staff reports that multiple chillers are down at the moment and the vendor has been contacted. The vendor is expected to be onsite at approximately 10:30 Site Local Time. Temperatures at the IBX are rising and are above SLA. IBX Critical Facility Engineers continue to monitor.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] LAX: Temporarily removed</title>
          <link>https://status.x4b.net/issues/2023-09-01-lax-temporarily-removed/</link>
          <pubDate>Fri, 01 Sep 2023 12:11:32 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-09-01-lax-temporarily-removed/</guid>
          <category>2024-03-05T05:24:21.250Z</category>
          <description>&lt;p&gt;&lt;em&gt;﻿Update&lt;/em&gt; - At long last upstream has resolved the issue.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;One of the edge routers encountered issues due to a firmware bug. detecting the issue was challenging as no logs were generated, due to the router running outdated firmware. the issue was resolved by updating the RE code and rebooting the router.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;R﻿outes to LA have been restored.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We have been investigating some issues this month in LA upstream. While we wait / work on resolution we have pulled routes from the region.&lt;/p&gt;
&lt;p&gt;W﻿e will return routes once the situation is resolved.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] LAX: Issues</title>
          <link>https://status.x4b.net/issues/2023-08-20-lax-issues/</link>
          <pubDate>Sun, 20 Aug 2023 08:37:56 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-08-20-lax-issues/</guid>
          <category>2023-08-20T12:35:32.332Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; issue resolved. Still awaiting more information.&lt;/p&gt;
&lt;p&gt;W﻿e will restore LAX routes.&lt;/p&gt;
&lt;p&gt;T﻿here is the possibility of routes being pulled in the near future for some maintenance. But for now routes are being restored.&lt;/p&gt;
&lt;p&gt;-﻿-&lt;/p&gt;
&lt;p&gt;We are aware of some issues affecting LAX. As such we have removed LAX from the Anycast mix.&lt;/p&gt;
&lt;p&gt;W﻿e will update and restore routes when resolved.&lt;/p&gt;
&lt;p&gt;T﻿raffic will now be redirected to nearby PoPs.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Hazard Notice</title>
          <link>https://status.x4b.net/issues/2023-07-25-hazard-notice/</link>
          <pubDate>Wed, 26 Jul 2023 03:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-07-25-hazard-notice/</guid>
          <category>2023-07-19T07:00:22.832Z</category>
          <description>&lt;p&gt;W﻿e will be performing maintenance tomorrow. No interruption is expected however risk exists for iterruptions over this time window.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Hazard Notice: Amsterdam, Ashburn, Chicago</title>
          <link>https://status.x4b.net/issues/2023-06-28-hazard-notice-amsterdam-ashburn-chicago/</link>
          <pubDate>Thu, 29 Jun 2023 01:00:03 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-06-28-hazard-notice-amsterdam-ashburn-chicago/</guid>
          <category>2023-06-29T01:43:41.238Z</category>
          <description>&lt;p&gt;&lt;em&gt;﻿&lt;/em&gt;Update** Maintenance completed (smoothly). If you hve any issues please do let us know&lt;/p&gt;
&lt;p&gt;We will be be performing some maintenance in these three locations in sequence tomorrow. No interruption is expected however some periods of packet loss are possible.&lt;/p&gt;
&lt;p&gt;Certain internal metrics such as filter graphs may be affected for periods of the maintenance.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Dallas &amp; Japan issue detected</title>
          <link>https://status.x4b.net/issues/2023-06-26-dallas-japan-issue-detected/</link>
          <pubDate>Mon, 26 Jun 2023 12:47:18 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-06-26-dallas-japan-issue-detected/</guid>
          <category>2023-06-27T04:12:21.031Z</category>
          <description>&lt;p&gt;&lt;em&gt;﻿Update&lt;/em&gt; Dalas issue resolved. We are waiting on a fix for Tokyo.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;W﻿e have removed routes to both regions.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Hazard Notice</title>
          <link>https://status.x4b.net/issues/2023-06-22-hazard-notice/</link>
          <pubDate>Fri, 23 Jun 2023 04:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-06-22-hazard-notice/</guid>
          <category>2023-06-23T07:28:23.682Z</category>
          <description>&lt;p&gt;&lt;em&gt;﻿&lt;/em&gt;Update** Maintenance completed (smoothly). If you hve any issues please do let us know&lt;/p&gt;
&lt;p&gt;We will be be performing some maintenance in these three locations in sequence tomorrow. No interruption is expected however some periods of packet loss are possible.&lt;/p&gt;
&lt;p&gt;Certain internal metrics such as filter graphs may be affected for periods of the maintenance.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] SYD1: Hazard Notice</title>
          <link>https://status.x4b.net/issues/2023-06-19-syd1-hazard-notice/</link>
          <pubDate>Mon, 19 Jun 2023 09:30:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-06-19-syd1-hazard-notice/</guid>
          <category>2023-06-19T10:35:51.285Z</category>
          <description>&lt;p&gt;&lt;strong&gt;﻿Update&lt;/strong&gt; Maintenance complete for tonight. One action has been delayed to a further maintenance period which we will perform in the coming days.&lt;/p&gt;
&lt;p&gt;We will be be performing some maintenance in Sydney tonight. N﻿o interruption is expected however some periods of packet loss are possible.&lt;/p&gt;
&lt;p&gt;C﻿ertain internal metrics such as filter graphs may be affected for periods of the maintenance.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Configuration update delay</title>
          <link>https://status.x4b.net/issues/2023-05-12-configuration-update-delay/</link>
          <pubDate>Fri, 12 May 2023 12:11:54 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-05-12-configuration-update-delay/</guid>
          <category>2023-05-12T13:21:06.152Z</category>
          <description>&lt;p&gt;&lt;em&gt;﻿Update&lt;/em&gt; service appears to have been restored for about half an hour. We havent yet got an update on our ticket. We will re-open this incident if necessary.&lt;/p&gt;
&lt;p&gt;D﻿ue to an upstream service interruption affecting our Kubernetes cluster configuration updates are currently unavailable.&lt;/p&gt;
&lt;p&gt;W﻿e have spoken to our upstream (Linode) and they have assured us the matter is being worked on.&lt;/p&gt;
&lt;p&gt;W﻿hen their issue is resolved any backlogged updates will be processed.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] SYD1: Maintenance</title>
          <link>https://status.x4b.net/issues/2023-03-28-syd1-maintenance/</link>
          <pubDate>Tue, 28 Mar 2023 03:56:28 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-03-28-syd1-maintenance/</guid>
          <category>2023-03-28T05:07:35.398Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are taking SYD1 offline temporarily for some maintenance. All routes will be redirected to nearby PoPs.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Complete&lt;/em&gt; Maintenance complete&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Vegas and Luxembourg</title>
          <link>https://status.x4b.net/issues/2023-01-05-vegas-and-luxembourg/</link>
          <pubDate>Fri, 06 Jan 2023 00:00:23 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-01-05-vegas-and-luxembourg/</guid>
          <category>2023-01-06T00:57:27.047Z</category>
          <description>&lt;p&gt;We are scheduling maintenance (system restart) tomorrow for a quick patch. Interuption of less than 10 minutes is expected.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;C﻿omplete&lt;/strong&gt;&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] NY1</title>
          <link>https://status.x4b.net/issues/2023-01-04-ny1/</link>
          <pubDate>Wed, 04 Jan 2023 04:30:10 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2023-01-04-ny1/</guid>
          <category>2023-01-04T04:51:09.646Z</category>
          <description>&lt;p&gt;We will be conducting some emergency maintenance shortly to resolve a discovered issue. We expect only a few minutes of interruption while the server restarts to apply the fix.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;﻿Update&lt;/strong&gt; Completed without issue (&amp;lt;1m interruption)&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Vegas: Offline</title>
          <link>https://status.x4b.net/issues/2022-10-15-vegas-offline/</link>
          <pubDate>Fri, 14 Oct 2022 18:25:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2022-10-15-vegas-offline/</guid>
          <category>2022-10-15T07:50:10.046Z</category>
          <description>&lt;p&gt;U﻿pstream Incident Report -&lt;/p&gt;
&lt;p&gt;Short version:&lt;br&gt;
&lt;br&gt;
Networks&#39; been crapping itself for the past day. After 2 - 3 hard failures today we did an emergency JunOS downgrade and are cautiously optimistic that it&amp;rsquo;s resolved.&lt;br&gt;
&lt;br&gt;
Longer/technical version:&lt;br&gt;
&lt;br&gt;
For the past month or so we&amp;rsquo;ve been suffering a weird issue where random IP addresses would stop responding. The issue is that our router would lose/expire out the ARP entry for these IP addresses and wouldn&amp;rsquo;t attempt to learn them again unless forced to.&lt;br&gt;
&lt;br&gt;
No amount of traffic getting sent to the IP externally (pings, random connection attempts, etc) would make the router issue an ARP &amp;ldquo;who-has&amp;rdquo; message. The only fix was to either ping the IP on the LAN (through our speedtest page for instance), forcing the router to see the ARP message on the network, or to login to the router and ping from there.&lt;br&gt;
&lt;br&gt;
No amount of limits, tweaks, process restarts, etc, has helped with this. The only way to date has been the above methods.&lt;br&gt;
&lt;br&gt;
This morning we had an issue where all users on 209.141.x.x dropped offline. These subnets had been moved down to our new Cisco core switch to help resolve the issue. Our Juniper router dropped the ARP entry for the Cisco switch, killing BGP. After some time it re-learned then entry reestablished connectivity, bringing those subnets back online.&lt;br&gt;
&lt;br&gt;
This happened three times in the past 24 hours, each outage lasting anywhere from 5 minutes to 30 minutes.&lt;br&gt;
&lt;br&gt;
Las Vegas is the only location suffering this issue. The key difference between all locations being that Vegas was running JunOS 20.4, where as everywhere else is 18.2~4. In JunOS 20.x they made changes to ARP to allow policing. While we did change this policy, it didn&amp;rsquo;t help us any.&lt;br&gt;
&lt;br&gt;
As of an hour ago we performed a downgrade to JunOS 18.4. It obviously went terribly. After some research we found the configuration entry causing issues (our 100G ports kept channelizing) and fixed it, bringing things back online.&lt;br&gt;
&lt;br&gt;
As of now, ARP&amp;rsquo;s are resolving near instantaneously, even for new IP addresses. We took this as a good time to change the rest of our ports to 100G, giving us a 400Gbit interlink between our router and core switch.&lt;br&gt;
&lt;br&gt;
We&amp;rsquo;re cautiously optimistic that this issue is now resolved.&lt;br&gt;
&lt;br&gt;
We thank you for your patience.&lt;/p&gt;
&lt;p&gt;-﻿-&lt;/p&gt;
&lt;p&gt;U﻿pstream reports that it is conducting emergency maintenance to downgrade the router firmware in an attempt to resolve issues.&lt;/p&gt;
&lt;p&gt;-﻿&amp;ndash;&lt;/p&gt;
&lt;p&gt;O﻿ffline again, ticket has been sent.&lt;/p&gt;
&lt;p&gt;-﻿&amp;ndash;&lt;/p&gt;
&lt;p&gt;U﻿pstream restored services.&lt;/p&gt;
&lt;p&gt;T﻿he underlying issue (router bug) is still under investigation.&lt;/p&gt;
&lt;p&gt;-﻿&amp;ndash;&lt;/p&gt;
&lt;p&gt;Vegas upstream is offline. We have ticketed them and contacted staff members. We await response.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Premium Anycast: Lumen Transit</title>
          <link>https://status.x4b.net/issues/2021-07-19-lumen-apac-upgrade/</link>
          <pubDate>Tue, 04 Oct 2022 01:55:08 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-07-19-lumen-apac-upgrade/</guid>
          <category>2023-02-09T02:44:02.746Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; It finally happened, it was a saga, but london Lumen has finally been lit.&lt;/p&gt;
&lt;p&gt;We are currently in the process of onboarding our new (replacement) transit provider Lumen (formerly Level3). Originally lit only for APAC and South America Lumen transit has now been lit for US and EU PoPs with one exception.&lt;/p&gt;
&lt;p&gt;W﻿e are currently waiting on transit availability in London (Globalswitch). Due to the close pysical location and significant advantage in lighting Lumen accross EU and US at this time we have opted to proceed before London is ready.&lt;/p&gt;
&lt;p&gt;T﻿he current ETA for London&amp;rsquo;s lumen transit is &amp;ldquo;a few weeks&amp;rdquo;.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Miami: Instability</title>
          <link>https://status.x4b.net/issues/2022-07-05-miami-instability/</link>
          <pubDate>Tue, 05 Jul 2022 04:54:31 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2022-07-05-miami-instability/</guid>
          <category>2022-07-06T01:50:44.887Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information. In order to test potential fixes to the issue we may need to restart services in this region.&lt;/p&gt;
&lt;p&gt;We will attempt to keep interruption to a minimum.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - We have rebooted the system into a new kernel with a proposed fix. The underlying cause (potentially hardware) continues to be investigated. We beleive however that the action taken will prevent the issue from impacting reliability further.&lt;/p&gt;
&lt;p&gt;We will keep this incident open and update it as matters progress.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - The workaround applied yesterday has proven itself effective. We will keep the workaround applied at this time until the underlying [assumed] hardware issue can be resolved. We do not anticipate any further instability and will schedule maintenance as appropriate for the next step seperately.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] AMS: Removed</title>
          <link>https://status.x4b.net/issues/2022-06-25-ams-removed/</link>
          <pubDate>Sat, 25 Jun 2022 09:11:42 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2022-06-25-ams-removed/</guid>
          <category>2022-06-25T11:25:07.521Z</category>
          <description>&lt;p&gt;After observing intermitant interuptions throught the day we have made the decision to temporarily remove the AMS PoP from both Anycast networks while we await upstream resolution.&lt;/p&gt;
&lt;p&gt;Routes via AMS will be restored once we get a suitable response or stability has appeared to return.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Miami: Network Unavailable</title>
          <link>https://status.x4b.net/issues/2022-05-17-miami-network-unabailable/</link>
          <pubDate>Mon, 16 May 2022 01:22:11 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2022-05-17-miami-network-unabailable/</guid>
          <category>2022-05-17T02:44:51.617Z</category>
          <description>&lt;p&gt;**Update** Upstream restored connectivity&lt;/p&gt;
&lt;p&gt;We are aware the Miami PoP is unavailable currently. Issue looks upstream and we await response from their operations / techs.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Equnix IX (Singapore)</title>
          <link>https://status.x4b.net/issues/2022-04-05-equnix-ix-singapore/</link>
          <pubDate>Tue, 05 Apr 2022 02:42:37 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2022-04-05-equnix-ix-singapore/</guid>
          <category>2022-04-05T01:42:00.000Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; We have restored Equinix SG IX. Issue was an incorrect route policy upstream. Upstream has issued a fix. We will be continuing to monitor the situation for any regression.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; We have made adjustments temporarily reducing the traffic going to SG but preventing route over-reach. We await the IX fix.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; we are awaiting upstream response on this matter&lt;/p&gt;
&lt;p&gt;We are aware of some (HE) traffic on the Premium Line from around the world arriving in Signapore. This appears to be due to a BGP bug in Equinix IX (Singapore). We are working with our upstreams on it.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Client Panel &amp; Website Upgrade</title>
          <link>https://status.x4b.net/issues/2022-03-21-client-panel-website-upgrade/</link>
          <pubDate>Tue, 22 Mar 2022 02:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2022-03-21-client-panel-website-upgrade/</guid>
          <category>2022-03-22T04:00:00.000Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Deployment of all queued customer configuration updates has been performed. If you are encountering any issues please do let us know.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Customer deployments and all customer facing services are up. If you are encountering any issues please do let us know. We will process the backlog of request for all services after a short break.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Most site components are are up. Customer service deployments will be available shortly. Appologies that this has taken much longer than expected.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Site is up (in dry-run mode). Changes to customer services will be deployed once we have completed full system tests. We will be taking this slowly and will update when an ETA is available.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; We are currently running a bit behind schedule on the first stage of the maintenance. We now hope to complete the first stage within the next 45 minutes.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Maintenance has begun&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Maintenance will begin on time in less than half an hour.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;On Tuesday afternoon we will be moving our web panel and database to new upgraded servers. This will consist of approximately 1 hour of panel and site outage (maintenance page) and up to 1 hour of partial ouage (dry run mode) while we complete manual tests on all components and services. During this time any customer service changes requested will be queued for execution on completion.&lt;/p&gt;
&lt;p&gt;We appologies for any inconvenience this may cause.&lt;/p&gt;
&lt;p&gt;We will update this status announcement as appropriate with updates.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Budget PoPs offline (upstream)</title>
          <link>https://status.x4b.net/issues/2022-02-15-budget-pops-offline-upstream/</link>
          <pubDate>Tue, 15 Feb 2022 00:07:29 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2022-02-15-budget-pops-offline-upstream/</guid>
          <category>2022-02-15T00:20:57.017Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Upstream resolved.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Luxembourg Network Outage</title>
          <link>https://status.x4b.net/issues/2022-01-24-luxembourg-network-outage/</link>
          <pubDate>Mon, 24 Jan 2022 01:31:04 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2022-01-24-luxembourg-network-outage/</guid>
          <category>2022-01-24T12:09:49.072Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; No official all clear yet as work related to the move continues. However all XCs are now up and services online for over half an hour.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Some routes are back. Some XCs are not yet spliced.&lt;/p&gt;
&lt;p&gt;Upstream network provider has announced a maintenenace affecting Lux customers.&lt;/p&gt;
&lt;p&gt;&amp;ndash;&lt;/p&gt;
&lt;p&gt;We apologize about the short notice (again).&lt;/p&gt;
&lt;p&gt;In the next 12 to 24 hours we will be migrating our router and cross connects in Luxembourg. Due to LuxConnect using a 3rd party to complete the fiber splicing, we can&amp;rsquo;t set an exact start time.&lt;/p&gt;
&lt;p&gt;To complete this work a full network outage must occur. The actual moving of the router upstairs should go quick since it&amp;rsquo;s a single unit, but given the delays we&amp;rsquo;ve had already I won&amp;rsquo;t promise any &amp;lsquo;completion&amp;rsquo; time.&lt;/p&gt;
&lt;p&gt;What we can say is this:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Luxconnect claims each XC will take around 10 minutes to splice.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;We have 4 cross connects in this location so their side will take about an hour to complete.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;We don&amp;rsquo;t require all 4 cross connects to be completed for service to be restored. Although there will be high latency and poor speeds until the work is fully completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Root really shouldn&amp;rsquo;t take more than 15 - 20 at the most to move that single unit as it&amp;rsquo;s quite light and doesn&amp;rsquo;t require 2 people. Famous last words.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Once we see one of or links go down we&amp;rsquo;ll press on Root to start the router move ASAP.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Since we&amp;rsquo;re not on site to complete this work ourselves we&amp;rsquo;re at the mercy of our vendors. We&amp;rsquo;re sorry we can&amp;rsquo;t give concrete completion times.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] LV1: Outage</title>
          <link>https://status.x4b.net/issues/2021-12-05-lv1-outage/</link>
          <pubDate>Sun, 05 Dec 2021 23:37:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-12-05-lv1-outage/</guid>
          <category>2021-12-06T00:57:00.000Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are aware of an outage in Vegas, we reported to datacenter and are awaiting resolution.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Local engineer on his way to datacenter to replace server PSU&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Fixed&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Observed issues with GTT routes</title>
          <link>https://status.x4b.net/issues/2021-10-14-observed-issues-with-gtt-routes/</link>
          <pubDate>Thu, 14 Oct 2021 03:23:50 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-10-14-observed-issues-with-gtt-routes/</guid>
          <category>2021-10-15T01:32:04.521Z</category>
          <description>&lt;p&gt;We are aware of issues with GTT routes at the transit level. These occur primarily from EU&amp;lt;-&amp;gt;US however some issues have been observed with other routes. We have contacted them for a comment however have not (as of yet) received one.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Observed Resolved&lt;/strong&gt; We are not longer observing GTT related packet loss.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Chicago Rack Maintenance</title>
          <link>https://status.x4b.net/issues/2021-10-09-chicago-rack-maintenance/</link>
          <pubDate>Tue, 12 Oct 2021 22:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-10-09-chicago-rack-maintenance/</guid>
          <category>2021-10-12T23:45:40.712Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Scheduled Maintenance&lt;/strong&gt; Upstream datacenter will be performing maintenance in the rack our server is located in. To keep downtime to the mininmum they have offered to move our server to an adjacent rack. We expect have been told to expect an interruption of between 10-20 minutes between 5:00pm and 7:00pm on Tuesday the 12th of October (Centeral Time)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Maintenance complete&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] LA: Hardware Upgrade</title>
          <link>https://status.x4b.net/issues/2021-09-23-la-hardware-upgrade/</link>
          <pubDate>Tue, 28 Sep 2021 04:50:32 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-09-23-la-hardware-upgrade/</guid>
          <category>2021-09-28T06:44:35.075Z</category>
          <description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Routes are up. We will observe closely for any issues. Please do open a support ticket if you notice anything we don&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Maintenance is proceeding roughly on schedule. We expect to be complete in 15-30 minutes.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; Maintenance is begining now&lt;/p&gt;
&lt;p&gt;We will be performing maintenance in L.A on Monday and Tuesday to upgrade the hardware we have deployed in the region.&lt;/p&gt;
&lt;p&gt;We will endeavour to keep interruption to a minimum by removing the PoP before and during major works. We expect to be able to perform this maintenance within 1-2 hours.&lt;/p&gt;
&lt;p&gt;We will update this announcement with further information when available.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Outage</title>
          <link>https://status.x4b.net/issues/2021-09-24-outage/</link>
          <pubDate>Fri, 24 Sep 2021 16:47:43 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-09-24-outage/</guid>
          <category>2021-09-24T17:24:22.261Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential upstream issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Upstream beleives it&amp;rsquo;s a breaker or power related. We await feedback from dc techs.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; power restored&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Chicago Launch</title>
          <link>https://status.x4b.net/issues/2021-08-27-chicago-launch/</link>
          <pubDate>Fri, 27 Aug 2021 07:22:55 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-08-27-chicago-launch/</guid>
          <category>2021-08-28T05:27:32.347Z</category>
          <description>&lt;p&gt;Due to unforseen circumstances the launch of the Chicago PoP has been delayed from the 27/08/2021 to 28/08/2021. We appologise for the inconvenience.&lt;/p&gt;
&lt;p&gt;Routes are up for all ranges in Chicago. Please do report any issues via ticket.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Amsterdam: Instability</title>
          <link>https://status.x4b.net/issues/2021-06-30-amsterdam-instability/</link>
          <pubDate>Wed, 30 Jun 2021 14:58:53 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-06-30-amsterdam-instability/</guid>
          <category>2021-06-30T16:48:51.560Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Resolved. Will continue to observe.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Ashburn Maintenance</title>
          <link>https://status.x4b.net/issues/2021-06-26-ashburn-maintenance/</link>
          <pubDate>Mon, 28 Jun 2021 04:48:39 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-06-26-ashburn-maintenance/</guid>
          <category>2021-06-28T06:43:46.378Z</category>
          <description>&lt;p&gt;As of this latest update we are marking this maintenance window as complete. If you are experiencing any issues please don&amp;rsquo;t hesitate to open a support ticket.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Regarding the network interruption (~30 second) that occurred during the Ashburn maintenance we do appologise for any inconvenience, particularly those in other regions adversely affected that should not have been involved in this maintenance. Clearly we did not intend for this response and will be investigating a fix for the faulty module ASAP which will be deployed before any other hardware upgrades are completed.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Update not going as smoothly as planned. However there should be no further interruptions. Further information to follow once upgrade is complete.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; We will be starting maintenance shortly. We expect minimal interuption. It is however possible some connections will be interrupted near the start and end of the maintenance. As always we will do our best to limit interruptions.&lt;/p&gt;
&lt;p&gt;We are planning to conduct a hardware upgrade during off-peak in Ashburn. Exact time is currently being scheduled with local technicians. We will update this entry with more information when we get scheduling confirmation.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Brazil: Packet Loss</title>
          <link>https://status.x4b.net/issues/2021-06-26-brazil-packet-loss/</link>
          <pubDate>Sat, 26 Jun 2021 03:07:48 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-06-26-brazil-packet-loss/</guid>
          <category>2021-06-26T04:38:31.525Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We have detected packet loss international and possibly domestic links. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Amsterdam: Issues</title>
          <link>https://status.x4b.net/issues/2021-06-03-amsterdam-issues/</link>
          <pubDate>Thu, 03 Jun 2021 00:46:45 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-06-03-amsterdam-issues/</guid>
          <category>2021-06-04T05:13:10.188Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are seeing  an issue with either network port stability or ixgbe driver stability in Amsterdam. We are investigating.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - We continue to watch for issues&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - We continue to watch for issues. Nothing has been observed as of yet.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We continue to search for the root cause. Another incident occurred around 07:35 GMT.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Changes&lt;/em&gt; - Some changes have been made to test a theory. We continue to monitor.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - We beleive the changes to have mostly resolved the issue. Further changes will be made to complete this. With this the issue can be closed.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Packet Loss in London</title>
          <link>https://status.x4b.net/issues/2021-05-23-packet-loss-in-london/</link>
          <pubDate>Sun, 23 May 2021 21:17:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-05-23-packet-loss-in-london/</guid>
          <category>2021-05-24T00:10:10.292Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating some observed uptream packet loss in London.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - London network vendor has confirmed the issue&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - We have not observed packet loss in half an hour. We await network vendor update.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Confirmed fixed upstream&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Cogent interruption</title>
          <link>https://status.x4b.net/issues/2021-05-12-cogent-interruption/</link>
          <pubDate>Wed, 12 May 2021 17:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-05-12-cogent-interruption/</guid>
          <category>2021-05-12T20:14:36.632Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We have narrowed the issue down to outgoing routes going over Cogent in two locations (AMS &amp;amp; LAX)&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - Cogent activated uRPF (without notice) on our upstream ports (2 PoPs) leading to an interruption as we don&amp;rsquo;t use Cogent for Ingress but they are used (if they are the best route) for Egress selectively.&lt;/p&gt;
&lt;p&gt;To resolve this we are now exporting ingress routes to Cogent with Cogents own no-export community.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Dallas: Issue</title>
          <link>https://status.x4b.net/issues/2021-04-14-dallas-issue/</link>
          <pubDate>Wed, 14 Apr 2021 11:56:26 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-04-14-dallas-issue/</guid>
          <category>2021-04-14T12:15:00.000Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; from upstream &amp;ldquo;I apologize for the trouble, one of our virtual chassis switches was having problems routing packets, so all packets were being split causing 50/50 delivery, so to clear this problem along with applying changes I rebooted the problematic switch. The issue should be fixed and as well redundant routing is now active.&amp;rdquo;&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Dallas: Switch issues</title>
          <link>https://status.x4b.net/issues/2021-04-14-dallas-switch-issues/</link>
          <pubDate>Wed, 14 Apr 2021 00:01:59 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-04-14-dallas-switch-issues/</guid>
          <category>2021-04-14T02:01:59.462Z</category>
          <description>&lt;p&gt;We are aware of some instability in the region. When contacted our upstream confirmed it and that it was resolved. It doesnt seem to be resolved.&lt;/p&gt;
&lt;p&gt;We have hence pulled our routes from the region.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; upstream has reported that everything has normalized and we have obersved the same. We are restoring Dallas routes.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] UK &amp; Amsterdam Maintenance</title>
          <link>https://status.x4b.net/issues/2021-03-03-uk-amsterdam-maintenance/</link>
          <pubDate>Sat, 03 Apr 2021 02:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-03-03-uk-amsterdam-maintenance/</guid>
          <category>2021-03-04T02:18:22.810Z</category>
          <description>&lt;p&gt;We will be conducting maintenance during regional off-peak in Europe tomorrow. No interruption is expected however a low risk of packet loss or latency does exist. This is the same maintenance conducted without interuption in Miami and L.A today.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt;  Maintenance is complete in both regions. Unfortunately not as smooth as yesterday with both regions experiencing short interruptions. Appologies for the inconvenience.&lt;/p&gt;
&lt;p&gt;Everything should now be at 100%. Please feel free to contact us if you are experiencing any issues.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] LA: maintenance</title>
          <link>https://status.x4b.net/issues/2021-03-03-la-maintenance/</link>
          <pubDate>Wed, 03 Mar 2021 10:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-03-03-la-maintenance/</guid>
          <category>2021-03-03T10:01:13.634Z</category>
          <description>&lt;p&gt;Maintenance will be be performed in LA during regional off-peak time tonight. No interruption is expected, a risk of small interruption is possible.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; complete. No interruption observed.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Miami: Maintenance</title>
          <link>https://status.x4b.net/issues/2021-03-03-miami-maintenance/</link>
          <pubDate>Wed, 03 Mar 2021 08:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-03-03-miami-maintenance/</guid>
          <category>2021-03-03T09:21:34.715Z</category>
          <description>&lt;p&gt;We are performing maintenance tonight during the regional off-peak. No interruption is expected however a risk does exist.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Completed without interruption.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] London: Hardware Crash</title>
          <link>https://status.x4b.net/issues/2021-02-27-london-hardware-crash/</link>
          <pubDate>Sat, 27 Feb 2021 17:40:50 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-02-27-london-hardware-crash/</guid>
          <category>2021-02-27T17:40:50.539Z</category>
          <description>&lt;p&gt;The filtering server in London experienced hard failure resulting in server crash. The server has rebooted and is now online.&lt;/p&gt;
&lt;p&gt;We are investigating the cause.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Amsterdam: Minor Maintenance</title>
          <link>https://status.x4b.net/issues/2021-02-14-amsterdam-minor-maintenance/</link>
          <pubDate>Mon, 15 Feb 2021 20:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-02-14-amsterdam-minor-maintenance/</guid>
          <category>2021-02-15T22:00:00.000Z</category>
          <description>&lt;p&gt;We will be conducting minor maintenance in Amsterdam. There will be a risk of a minutes of interruption as sessions are updated. We will attempt to keep the interruption as quick as possible if required (which we hope it will not be).&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Amsterdam: Hazzard Notice</title>
          <link>https://status.x4b.net/issues/2021-02-14-amsterdam-hazzard-notice/</link>
          <pubDate>Mon, 15 Feb 2021 02:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-02-14-amsterdam-hazzard-notice/</guid>
          <category>2021-02-15T06:00:00.000Z</category>
          <description>&lt;p&gt;Today we will be performing preperation for tomorrows scheduled maintenance. No interruption is expected.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] London: Minor Maintenance</title>
          <link>https://status.x4b.net/issues/2021-02-10-london-minor-maintenance/</link>
          <pubDate>Fri, 12 Feb 2021 19:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-02-10-london-minor-maintenance/</guid>
          <category>2021-02-12T22:30:00.000Z</category>
          <description>&lt;p&gt;At some point between the 7AM and 9:30 AM AEDT tomorrow we will be performing minor maintenance in London. Expected interruption is 1-5 minutes as we apply changes from todays preperation session.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Rescheduled due to upstream scheduling conflict.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; complete&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] UK: Hazard Warning</title>
          <link>https://status.x4b.net/issues/2021-02-10-uk-hazard-warning/</link>
          <pubDate>Wed, 10 Feb 2021 03:00:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-02-10-uk-hazard-warning/</guid>
          <category>2021-02-10T05:30:00.000Z</category>
          <description>&lt;p&gt;We will be conducting some minor maintenance in London this afternoon. No interruption is expected however as always when work is being carried out there is a small chance of issue. Due to this we are conducting this maintenance outside of UK peak hours.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Maintenance is proceeding well. End time has been revised to reflect some expected delays.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; Maintenance complete. Minor interruption did occur towards the end. Procedure has been updated to prevent this in future executions of this plan.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Dallas: Partial Interruption</title>
          <link>https://status.x4b.net/issues/2021-02-08-dallas-partial-interruption/</link>
          <pubDate>Mon, 08 Feb 2021 18:51:06 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-02-08-dallas-partial-interruption/</guid>
          <category>2021-02-08T18:58:43.061Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - A partial outage has been detected in Dallas. We have pulled routes from region while we investigate / resolve.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - Issue related to some minor maintenance being performed behind the scenes not going as planned. Caused has been fixed and maintenance is complete.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Hazard Notice: Dallas</title>
          <link>https://status.x4b.net/issues/2021-01-14-hazard-notice-dallas/</link>
          <pubDate>Thu, 14 Jan 2021 01:50:45 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-01-14-hazard-notice-dallas/</guid>
          <category>2021-01-15T01:50:00.000Z</category>
          <description>&lt;p&gt;We will be performing some preperation for upcoming maintenance in Dallas at a time after 6PM AEST tonight. We do not expect any interruption in region however the possibility of minor packet loss or short interruption does exist. We will endevour to perform preperation without any interruption.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Amsterdam: Maintenance</title>
          <link>https://status.x4b.net/issues/2021-01-09-amsterday-maintenance/</link>
          <pubDate>Sat, 09 Jan 2021 01:40:16 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-01-09-amsterday-maintenance/</guid>
          <category>2021-01-09T03:12:08.243Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating an increase in latency observed last night. In order to perform this investigating without risk to customer performance we have removed AMS from the network with UK taking over to provide capacity while we investigate.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Complete&lt;/em&gt; - AMS routes restored. Issue should be resolved.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] London: Investigating</title>
          <link>https://status.x4b.net/issues/2021-01-05-london-investigating/</link>
          <pubDate>Tue, 05 Jan 2021 04:31:15 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-01-05-london-investigating/</guid>
          <category>2021-01-05T08:31:55.445Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. As such we have pulled routes from the London region while we investigate.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Attempted to restore routes however we are seeing a problem with that. Please hold while the issue is identified.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Dallas: Fault Detected</title>
          <link>https://status.x4b.net/issues/2021-01-04-dallas-fault-detected/</link>
          <pubDate>Mon, 04 Jan 2021 00:32:13 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-01-04-dallas-fault-detected/</guid>
          <category>2021-01-05T01:26:52.786Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We have detected a fault in our network cable / switch port. We will be scheduling replacement later today.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Replacement occurring now&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - While we confirm the issue is resolved we will keep routes disabled. If the lack of Dallas routes is causing you issue please open a support ticket and we will see what we can do.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Confirmed resolved, routes re-enabled.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Budget: Issue continued.</title>
          <link>https://status.x4b.net/issues/2021-01-02-budget-issue-continued/</link>
          <pubDate>Sat, 02 Jan 2021 03:49:26 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2021-01-02-budget-issue-continued/</guid>
          <category>2021-01-02T07:04:00.000Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Upstream&lt;/em&gt; - Confirmed issue with them.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Budget: Incident</title>
          <link>https://status.x4b.net/issues/2020-12-30-lux-incident/</link>
          <pubDate>Wed, 30 Dec 2020 04:20:00 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2020-12-30-lux-incident/</guid>
          <category>2020-12-30T12:53:00.000Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Upstream response&lt;/em&gt; - Confirms issue on their end.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Upstream response&lt;/em&gt; - Upstream is experiencing DDoS attacks on unprotected resources they operate (extortion).&lt;/p&gt;
&lt;p&gt;Attack looks to have ended for some hours. Marked as resolved.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Lux: Packet Loss</title>
          <link>https://status.x4b.net/issues/2020-12-27-lux-packet-loss/</link>
          <pubDate>Sun, 27 Dec 2020 09:39:32 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2020-12-27-lux-packet-loss/</guid>
          <category>2020-12-27T09:54:57.991Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Upstream Response&lt;/em&gt; - Confirms the issue and will have it fixed ASAP.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Under Observation&lt;/em&gt; - Upstream has the issue resolved for now and will continue observation.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Luxembourg: Unplanned Hardware Migration</title>
          <link>https://status.x4b.net/issues/2020-12-23-luxembourg-unplanned-hardware-migration/</link>
          <pubDate>Wed, 23 Dec 2020 09:50:55 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2020-12-23-luxembourg-unplanned-hardware-migration/</guid>
          <category>2020-12-23T10:53:40.864Z</category>
          <description>&lt;p&gt;We have been made aware of an emergency migration taking place in Luxembourg. We have been given an ETA of 1hr to move our data. Once moved we will endevour to get the node booted ASAP.&lt;/p&gt;
&lt;p&gt;Appologies for the inconvenience expecially at this time of year.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Fixed&lt;/strong&gt; Maintenance complete. We are currently conducting tests to ensure everything is A-OK. Please let us know if something is currently not.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Amsterdam: Connectivity Issues (2)</title>
          <link>https://status.x4b.net/issues/2020-12-19-amsterdam-connectivity-issues-2/</link>
          <pubDate>Sat, 19 Dec 2020 14:42:11 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2020-12-19-amsterdam-connectivity-issues-2/</guid>
          <category>2020-12-19T22:52:18.874Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - It appears that the Emergency maintenance performed by upstream to resolve Amsterdam: Connectivity Issues has not been successful in resolving the ToR stability issue. We have seen what appears to be a similar interuption. We have pulled routes again and await upstream response.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - CPU spikes on upstream ToR switch. They have made some adjustments and continue to monitor. We have restored routes.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Upstream reports fixed. We will continue to monitor closely over the next few days however.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Amsterdam: Connectivity Issues</title>
          <link>https://status.x4b.net/issues/2020-12-18-amsterdam-connectivity-issues/</link>
          <pubDate>Fri, 18 Dec 2020 16:02:44 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2020-12-18-amsterdam-connectivity-issues/</guid>
          <category>2020-12-18T16:02:44.146Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; -  We hae confirmed a partial interruption in network traffic in region. This is similar to a smaller incident observed yesterday which was reported upstream. We have collected data and reported this incident upstream and are awaiting resolution. Routes have been pulled from Amsterdam at this time.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - Upstream beleives they have identified the issue on their end and are taking action to confirm. Routes remain removed from region.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Resolution (1)&lt;/em&gt; - An emergency top of rack switch update has been scheduled to resolve a software bug in the managment software. Routes restored until we have a date/time.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - ToR switch updated&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Amsterdam: Reverse Proxy issue</title>
          <link>https://status.x4b.net/issues/2020-12-16-amsterdam-reverse-proxy-issue/</link>
          <pubDate>Wed, 16 Dec 2020 11:37:16 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2020-12-16-amsterdam-reverse-proxy-issue/</guid>
          <category>2020-12-16T11:37:16.086Z</category>
          <description>&lt;p&gt;An issue affecting Layer 4 reverse proxies in Amsterdam after todays maintenance has been reported and resolved. Appologies for the inconvenience.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Maintenance: Amsterdam Network Upgrade</title>
          <link>https://status.x4b.net/issues/2020-12-14-maintenance-amsterdam-network-upgrade/</link>
          <pubDate>Tue, 15 Dec 2020 19:50:52 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2020-12-14-maintenance-amsterdam-network-upgrade/</guid>
          <category>2020-12-15T21:00:52.175Z</category>
          <description>&lt;p&gt;We will be upgrading our network capacity and filtering hardware in Amsterdam. Any customers who have configured a HA type setup will be largely unaffected as routes will be removed from the region at-least 10 minutes before start of maintenance and traffic redirected to London and Ashburn PoPs.&lt;/p&gt;
&lt;p&gt;We expect the total maintenance to take approx 1-hour.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Maintenance taking a little longer than expected. Routes will be restored to Amsterdam as soon as possible.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Routes have been restored, final finishing of tasks continues in the background with no expected interruption.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Final checks complete. If you are experiencing any issues please don&amp;rsquo;t hesitate to contact us.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Packet Loss (multiple locations)</title>
          <link>https://status.x4b.net/issues/2020-12-13-packet-loss-multiple-locations/</link>
          <pubDate>Sun, 13 Dec 2020 05:53:02 +0000</pubDate>
          <guid>https://status.x4b.net/issues/2020-12-13-packet-loss-multiple-locations/</guid>
          <category>2020-12-16T05:10:00.000Z</category>
          <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Cause&lt;/em&gt; - We are seeing intermittent issues caused by an upstream system not working as it should or being delayed in operation. We have tickets waiting response upstream.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; 1 - We have some mitigations in place and await full diagnosis and fix upstream.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; 2 - We continue to await confirmation of permanent fix. Tempory fix means no issues have been observed for &amp;gt;24-hours.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update 3&lt;/em&gt; - We continue to await confirmation of permanent fix. However as there has been no impact on customer services for days we will close this issue.&lt;/p&gt;
</description>
        </item>
      
    </channel>
  </rss>

