<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:webfeeds="http://webfeeds.org/rss/1.0">
    <channel>
        <title><![CDATA[LINX Community]]></title>
        <description><![CDATA[LINX Community]]></description>
        <link>https://community.linx.net</link>
        <generator>Bettermode RSS Generator</generator>
        <lastBuildDate>Wed, 05 Aug 2026 20:55:52 GMT</lastBuildDate>
        <atom:link href="https://community.linx.net/rss/feed" rel="self" type="application/rss+xml"/>
        <pubDate>Wed, 05 Aug 2026 20:55:52 GMT</pubDate>
        <copyright><![CDATA[2026 LINX Community]]></copyright>
        <language><![CDATA[en-US]]></language>
        <ttl>60</ttl>
        <webfeeds:icon></webfeeds:icon>
        <webfeeds:related layout="card" target="browser"/>
        <item>
            <title><![CDATA[Learn With LINX: LINX NoVA]]></title>
            <link>https://community.linx.net/events-zyy1nbfb/post/learn-with-linx-linx-nova-15EzuH3bWbAV9CS</link>
            <guid isPermaLink="true">https://community.linx.net/events-zyy1nbfb/post/learn-with-linx-linx-nova-15EzuH3bWbAV9CS</guid>
            <dc:creator><![CDATA[Marketing Admin]]></dc:creator>
            <pubDate>Thu, 30 Jul 2026 07:57:40 GMT</pubDate>
            <content:encoded/>
        </item>
        <item>
            <title><![CDATA[Dammam IX route server information]]></title>
            <description><![CDATA[OVERVIEW

LINX/Dammam IX maintains route servers at each peering LAN, allowing members to establish multilateral peerings with other participants on Dammam IX. By establishing a single peering with a ...]]></description>
            <link>https://community.linx.net/exchange-docs-oo8vcsp0/post/dammam-ix-route-server-information-r9AmZP69qNQLXee</link>
            <guid isPermaLink="true">https://community.linx.net/exchange-docs-oo8vcsp0/post/dammam-ix-route-server-information-r9AmZP69qNQLXee</guid>
            <dc:creator><![CDATA[Marketing Admin]]></dc:creator>
            <pubDate>Tue, 07 Jul 2026 08:11:06 GMT</pubDate>
            <content:encoded><![CDATA[<h3 class="text-lg" data-toc-id="3ef97fff-ab9a-4e93-8ed0-3b44a53478e6" id="3ef97fff-ab9a-4e93-8ed0-3b44a53478e6"><strong>Overview</strong></h3><p>LINX/Dammam IX maintains route servers at each peering LAN, allowing members to establish multilateral peerings with other participants on Dammam IX. By establishing a single peering with a route server, routes can be shared with a large number of LINX members without configuring separate peerings with each LINX member.</p><p>Current route server statistics can be found here:&nbsp;<a class="text-interactive hover:text-interactive-hovered" rel="noopener noreferrer nofollow" href="https://portal.linx.net/route-server-graphs"><u>Route Server Graphs</u></a></p><h3 class="text-lg" data-toc-id="2302f56e-49f7-4c03-8ddf-d1e91c531d4a" id="2302f56e-49f7-4c03-8ddf-d1e91c531d4a"><strong>Dammam IX route server list</strong></h3><p>All LINX route servers are using the BIRD distribution and are configured with ASN&nbsp;<a class="text-interactive hover:text-interactive-hovered" rel="noreferrer" href="https://apps.db.ripe.net/db-web-ui/query?form_type=simple&amp;full_query_string=&amp;searchtext=AS213797"><u>213797</u></a></p><table style="width: 360px" class="border-collapse m-0 table-fixed"><colgroup><col style="width: 120px"><col style="width: 120px"><col style="width: 120px"></colgroup><tbody><tr class="isolation-auto"><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Server</p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>IPv4 Address</p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>IPv6 Address</p></th></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>rs1.dam1</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>193.201.155.124</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>2001:7f8:15f::3:4325:1</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>rs2.dam1</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>193.201.155.125</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>2001:7f8:15f::3:4325:2</p></td></tr></tbody></table><p>All route servers filter bogon address ranges.</p><h3 class="text-lg" data-toc-id="c2d05007-f6ef-41a7-b942-349d9fd9517d" id="c2d05007-f6ef-41a7-b942-349d9fd9517d"><strong>Dammam IX route server list</strong></h3><p>Policy control is done by use of BGP Standard Communities and BGP Large Communities. Members may tag their routes with the following to control policy via the route server. The model is as follows:</p><table style="width: 360px" class="border-collapse m-0 table-fixed"><colgroup><col style="width: 120px"><col style="width: 120px"><col style="width: 120px"></colgroup><tbody><tr class="isolation-auto"><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Action</p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Standard Community</p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Large Community</p></th></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>block announcement of a route to a certain peer</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>N/A</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>213797:0:peer-as</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>announcement of a route to a certain peer</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>N/A</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>213797:1:peer-as</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>block announcement of a route to all peers</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>N/A</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>213797:0:0</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>announcement of a route to all peers</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>N/A</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>213797:1: 213797</p></td></tr></tbody></table><p>* N/A ~ Cannot be used as RS ASN is 32bit</p><p>If none of the above communities is present, then the default behaviour is to advertise the prefix to all peers.</p><h3 class="text-lg" data-toc-id="a48aa5a7-a63c-4e8a-b0c5-81deb7728ce4" id="a48aa5a7-a63c-4e8a-b0c5-81deb7728ce4"><strong>AS-Path prepending</strong></h3><p>Members can tag their prefixes with the following communities, causing the Dammam IX route server to prepend ASNs to the prefix when advertising it to either all or selected members.</p><p>The following communities will cause the Dammam IX route server to prepend ASNs to the prefix for all members peering on the route server.</p><table style="width: 480px" class="border-collapse m-0 table-fixed"><colgroup><col style="width: 120px"><col style="width: 120px"><col style="width: 120px"><col style="width: 120px"></colgroup><tbody><tr class="isolation-auto"><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Community type</p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Prepend ASN one time</p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Prepend ASN two times</p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Prepend ASN three times</p></th></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Standard</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>N/A</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>N/A</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>N/A</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Large</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>213797:65501:1</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>213797:65502:2</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>213797:65503:3</p></td></tr></tbody></table><p>* N/A ~ Cannot be used as RS ASN is 32bit</p><p>The following communities will cause the Dammam IX route server to prepend ASNs to the prefix for the member with ASN $peer on the route server.</p><table style="width: 480px" class="border-collapse m-0 table-fixed"><colgroup><col style="width: 120px"><col style="width: 120px"><col style="width: 120px"><col style="width: 120px"></colgroup><tbody><tr class="isolation-auto"><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Community type</p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Prepend ASN one time</p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Prepend ASN two times</p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 120px; min-width: 120px;" rowspan="1" colspan="1"><p>Prepend ASN three times</p></th></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Standard</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>65501:$peer</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>65502:$peer</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>65503:$peer</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Large</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>213797:65501:$peer</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>213797:65502:$peer</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>213797:65503:$peer</p></td></tr></tbody></table><p><br></p><p>If you want to prepend more than three ASNs, please contact <a class="text-interactive hover:text-interactive-hovered" rel="noopener noreferrer nofollow" href="mailto:support@linx.net"><u>support@linx.net</u></a></p><h3 class="text-lg" data-toc-id="6e57b70b-283d-4a7d-9f12-bef64a84a1e1" id="6e57b70b-283d-4a7d-9f12-bef64a84a1e1"><strong>Prefix validation</strong></h3><p>LINX is validating prefixes at ingress on all route servers. The validation is based on RPKI and IRR Object presence.</p><p>For RPKI validation we build a ROA table from IRR trust anchors and for IRR Object presence we build a list of valid origin ASN and prefixes based on route objects. Refines/more specifics of valid route objects are rejected.</p><p>We are looking for a valid AS-SET in the members PeeringDB record. If no valid AS-SET is found, we use the members ASN only, unless the member has provided us other information.</p><p>The results of the validation is reflected in communities which are being added at ingress:</p><ul><li><p><strong>213797:1001:1</strong> = Prefix is present in an AS's announced AS/AS-SET</p></li><li><p><strong>213797:1001:6</strong> = Prefix is not present in an AS's announced AS/AS-SET</p></li><li><p><strong>213797:1001:2</strong> = Prefix has valid Origin AS in AS-SET</p></li><li><p><strong>213797:1001:5</strong> = Prefix has no valid Origin AS in AS-SET</p></li><li><p><strong>213797:1000:1</strong> = Prefix is RPKI VALID</p></li><li><p><strong>213797:1000:4</strong> = Prefix is RPKI INVALID</p></li><li><p><strong>213797:1000:2</strong> = Prefix is RPKI UNKNOWN</p></li></ul><p>The prefix validation will always occur, and members can check the communities being set to their prefixes, and as such see the result of the validation checks through the route server looking glass interface.</p><p>Prefixes will only be accepted on the following criteria where,</p><ol><li><p>Prefixes tagged with communities 213797:1001:2 (valid Origin AS in AS-SET) &amp; 213797:1000:1 (RPKI VALID) or</p></li><li><p>Prefixes tagged with communities 213797:1001:2 (valid Origin AS in AS-SET) &amp; 213797:1001:1 (Prefix is present in an AS's announced AS/AS-SET) &amp; 213797:1000:2 (RPKI UNKNOWN).</p></li></ol><p>All other prefixes will be filtered at egress.</p><p>Any member who prefers to receive an unfiltered set of prefixes can request to opt-out of the filtering by contact our NOC at <a class="text-interactive hover:text-interactive-hovered" rel="noopener noreferrer nofollow" href="mailto:support@linx.net"><u>support@linx.net</u></a>.</p><h3 class="text-lg" data-toc-id="dda90972-fea5-4c04-94af-ff4501fffa65" id="dda90972-fea5-4c04-94af-ff4501fffa65"><strong>Vendor issues</strong></h3><p><strong>Corrupt AS path &amp; malformed AS-Path issues</strong></p><p>Some members who use Cisco, Brocade and Huawei devices to peer with may encounter issues in establishing peering sessions and may see notifications of invalid or corrupt AS path and Malformed AS-path in their device logs. Something similar to:</p><pre><code>Sep 1 08:40:40.498 UTC: %BGP-5-ADJCHANGE: neighbor 195.66.225.230 Up Sep 1 08:40:41.506 UTC: %BGP-5-ADJCHANGE: neighbor 195.66.225.230 Down BGP Notification sentSep 1 08:40:41.506 UTC: %BGP-3-NOTIFICATION: sent to neighbor 195.66.225.230 3/11 (invalid corrupt AS path) 11 bytes 40020802 033C3424 580097</code></pre><p>This issue is caused where the peering device does not like to receive updates from the route-server where the first AS in the path is not the route-server AS.</p><p>To work around this please use one of the vendor specific commands in your router configuration.</p><p><strong>Cisco/Quagga/Brocade/Arista</strong></p><pre><code>router bgp &lt;ASN&gt;
no bgp enforce-first-as</code></pre><p><br><strong>Huawei</strong></p><pre><code>bgp &lt;ASN&gt;
undo check-first-as</code></pre><p>If members are having trouble peering with the route servers please contact <a class="text-interactive hover:text-interactive-hovered" rel="noopener noreferrer nofollow" href="mailto:support@linx.net"><u>support</u></a>.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LINX Portal: Latest Updates and What's Coming Next]]></title>
            <description><![CDATA[We're pleased to share the latest improvements now live on the LINX Portal:

Improved bandwidth selection and ordering experience

Following feedback that the previous experience was difficult to use, we'...]]></description>
            <link>https://community.linx.net/news-mvei3wws/post/linx-portal-latest-updates-and-what-s-coming-next-Oqz2IOCfELwrTrA</link>
            <guid isPermaLink="true">https://community.linx.net/news-mvei3wws/post/linx-portal-latest-updates-and-what-s-coming-next-Oqz2IOCfELwrTrA</guid>
            <dc:creator><![CDATA[Marketing Admin]]></dc:creator>
            <pubDate>Tue, 30 Jun 2026 12:51:52 GMT</pubDate>
            <content:encoded><![CDATA[<p>We're pleased to share the latest improvements now live on the LINX Portal:</p><p><strong>Improved bandwidth selection and ordering experience</strong></p><p>Following feedback that the previous experience was difficult to use, we've completely redesigned the bandwidth selection and ordering flow:</p><ul><li><p>Delivery constraints are now presented upfront, reducing confusion and invalid selections</p></li><li><p>Port selection now includes third party fabrics</p></li><li><p>The experience is consistent whether you're ordering as a member or managing services as a reseller</p></li></ul><p><br><strong>Order summaries</strong></p><p>Order summaries are now live. For any completed order that results in a billing change, including new orders, bandwidth changes, and location moves, you can download a standardised PDF directly from portal to support internal finance reconciliation.</p><p><br><strong>BGP session visibility</strong></p><p>You can now view the health of your BGP sessions directly in portal, without needing to contact the NOC or use Looking Glass. This includes:</p><ul><li><p>Session status and uptime</p></li><li><p>Prefix counts</p></li><li><p>Rejection reasons and session health indicators</p></li></ul><p><br><strong>Service health and maintenance visibility</strong></p><p>You can now see which of your services are affected by scheduled or active maintenances and outages directly within My Services, without navigating away. This includes:</p><ul><li><p>Visual indicators at service level showing maintenance or outage status</p></li><li><p>A summary banner showing how many of your services are affected, with the ability to filter to affected services only</p></li><li><p>A detail view with event information for each affected service</p></li></ul><p><strong>Coming soon</strong></p><ul><li><p><strong>Portal notifications</strong>: proactive notifications for order lifecycle events, scheduled maintenances and outages, and access and role changes, delivered in-portal and via email</p></li><li><p><strong>Portal stats improvements</strong>: restoring missing metrics, surfacing optics data, and usability improvements across the stats views</p></li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Peering Health Check]]></title>
            <description><![CDATA[Keeping your peering setup running smoothly is essential for performance, resilience, and long‑term efficiency. Join the LINX team for a practical, member‑focused Peering Health Check Webinar, ...]]></description>
            <link>https://community.linx.net/events-zyy1nbfb/post/peering-health-check-dmEJrUc17O644r6</link>
            <guid isPermaLink="true">https://community.linx.net/events-zyy1nbfb/post/peering-health-check-dmEJrUc17O644r6</guid>
            <dc:creator><![CDATA[Marketing Admin]]></dc:creator>
            <pubDate>Wed, 24 Jun 2026 14:55:07 GMT</pubDate>
            <content:encoded><![CDATA[<p>Keeping your peering setup running smoothly is essential for performance, resilience, and long‑term efficiency. Join the LINX team for a practical, member‑focused Peering Health Check Webinar, designed to help you get the most out of your LINX connection and confidently navigate the LINX Portal and NOC services.</p><p>This session is ideal for network engineers, operations teams, and anyone responsible for managing peering and other services at LINX.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LINX17 & EGM]]></title>
            <description><![CDATA[Registration for LINX127 & EGM is opening soon!

_______________________

Join us for:

 * Industry expert insights, hands-on workshops, and LINX updates

 * Meaningful connections with peers in focused networking ...]]></description>
            <link>https://community.linx.net/events-zyy1nbfb/post/linx127-egm-E72GeF361hIpN9G</link>
            <guid isPermaLink="true">https://community.linx.net/events-zyy1nbfb/post/linx127-egm-E72GeF361hIpN9G</guid>
            <dc:creator><![CDATA[Marketing Admin]]></dc:creator>
            <pubDate>Fri, 19 Jun 2026 09:34:14 GMT</pubDate>
            <content:encoded><![CDATA[<p><strong>Registration for LINX127 &amp; EGM is opening soon!</strong></p><p><strong>_______________________</strong></p><p><strong>Join us for:</strong></p><ul><li><p>Industry expert insights, hands-on workshops, and LINX updates</p></li><li><p>Meaningful connections with peers in focused networking sessions</p></li><li><p>Direct access to LINX specialists and leadership teams</p></li></ul><p>&nbsp;</p><p>18 – 19 November 2026<br>&nbsp; Convene, 133 Houndsditch, London</p><p>LINX127 &amp; EGM with updates, external speakers, networking, and evening social.</p><p>The webcast will be available for those unable to attend in-person, this time hosted on <a href="https://community.linx.net/" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered">LINX Community</a>.</p><p><strong>_______________________</strong></p><p><strong>Check out our previous member meetings</strong></p><p><a href="https://www.linx.net/events-category/linx-meeting-archive/" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"><strong>See More</strong></a></p><p><strong>_______________________</strong></p><p><strong>Sponsor a LINX meeting</strong></p><p>There are many exciting benefits to sponsoring a LINX member meeting. Gain direct access to our engaged community by showcasing your organisation’s products and services in our breakout space, submitting a presentation topic, and featuring in our widely-read newsletter. Sponsorship offers a unique opportunity to boost brand visibility, connect with industry leaders, and position your organisation at the heart of the networking community.</p><p>Over the years, our LINX meetings have seen;</p><ul><li><p>3,500+ In-Person Attendees</p></li><li><p>1,000+ Attendees via our WebCast</p></li><li><p>350+ Member Organisations Attend</p></li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Alliance to Strengthen Digital Infrastructure Across the North]]></title>
            <description><![CDATA[Greater Manchester Combined Authority (GMCA) [https://www.greatermanchester-ca.gov.uk/], Cooperative Network Infrastructure (CNI) [https://www.cni.coop/] and the London Internet Exchange (LINX) have announced the formation of the Digital Infrastructure North Alliance...]]></description>
            <link>https://community.linx.net/news-mvei3wws/post/new-alliance-to-strengthen-digital-infrastructure-across-the-north-xwbQV5KBHlToFEJ</link>
            <guid isPermaLink="true">https://community.linx.net/news-mvei3wws/post/new-alliance-to-strengthen-digital-infrastructure-across-the-north-xwbQV5KBHlToFEJ</guid>
            <dc:creator><![CDATA[Linx Bot]]></dc:creator>
            <pubDate>Wed, 17 Jun 2026 12:40:38 GMT</pubDate>
            <content:encoded><![CDATA[<p><a href="https://www.greatermanchester-ca.gov.uk/">Greater Manchester Combined Authority (GMCA)</a>, <a href="https://www.cni.coop/">Cooperative Network Infrastructure (CNI)</a> and the London Internet Exchange (LINX) have announced the formation of the Digital Infrastructure North Alliance — a collaborative initiative aimed at strengthening digital infrastructure across the North of England and making the case for greater investment in the region’s digital future.</p>
<p>The announcement was made at <a href="https://din26.com/">Digital Infrastructure North 2026 (DIN26)</a>, a senior-level summit convened by the three organisations together with Manchester Digital, bringing together public sector leaders, infrastructure operators, technology companies and research organisations at Circle Square, Manchester.</p>
<h3>Why this matters</h3>
<p>The UK’s digital infrastructure — its internet exchanges, data centres and high-capacity networks — remains heavily concentrated in London and the South East. This creates real risks: to resilience, as over-concentration in one geography creates systemic vulnerability; to sustainability, as renewable energy generated in the North cannot easily be used where digital demand is concentrated; and to sovereignty, as public sector organisations become increasingly dependent on a small number of external platforms for critical services.</p>
<p>The North has the assets, the energy and the innovation ecosystems to help address this. The Digital Infrastructure North Alliance is a commitment by three organisations to work together — and to help catalyse a wider conversation — about how that potential can be realised.</p>
<p>Stephen Young, CEO of Salford City Council said</p>
<blockquote><p>“The Digital Infrastructure North Alliance marks a step forward in a shared commitment to strengthening the digital future of Greater Manchester and the North. Digital infrastructure underpins how we create places that are more connected, competitive, inclusive and resilient. By working together, we can accelerate the investment, innovation and collaboration needed to support growth and deliver better outcomes for communities across Greater Manchester and beyond.”</p>
<p>&nbsp;</p></blockquote>
<h3>What the Alliance brings together</h3>
<p>The Alliance combines complementary capabilities across three organisations, each with a stake in the North’s digital future:</p>
<ul>
<li>GMCA is the established mayoral strategic authority for Greater Manchester. It plays a central role in supporting the digital infrastructure, inclusion and innovation needed for residents and businesses to access opportunities, services and growth across the city region</li>
<li>LINX is one of the world’s largest Internet exchanges, operating a regional peering facility in Manchester that keeps internet traffic local, reducing latency and improving resilience for organisations across the North</li>
</ul>
<p>Jennifer Holmes, CEO for the London Internet Exchange (LINX) said;</p>
<blockquote><p>“LINX Manchester has become a vital hub for digital growth in the North. We are proud to be extending its reach and collaborative opportunities to key stakeholders in the North for the good of the Internet and connectivity experiences within the public sector. This alliance allows us to extend the benefits of peering to more organisations, keeping traffic local and enabling faster, more efficient services.”</p></blockquote>
<ul>
<li>CNI is a cooperative providing shared passive infrastructure — dark fibre and colocation — across Greater Manchester, Blackpool and beyond, with existing connectivity into <a href="https://www.linx.net/about/network/linx-manchester/">LINX Manchester</a></li>
</ul>
<p>&nbsp;</p>
<h3>What the Alliance will do</h3>
<p>The Alliance’s first act is to <a href="https://www.linkedin.com/feed/update/urn:li:activity:7460276314063929344">convene DIN26</a> — intended as the first of an annual series of summits sustaining a long-term, inclusive conversation about digital infrastructure strategy in the North.</p>
<p>Beyond the summit, the Alliance will work together on infrastructure initiatives where the capabilities of its members are complementary. One project under active consideration would bring <a href="https://www.linx.net/services/peering-services/">LINX peering</a> capacity directly into CNI’s Ashton Old Baths Digital Exchange, where it could connect to networks including GM One — the high-speed core network connecting over 1,200 public sector sites across Greater Manchester. If realised, this would allow public sector organisations to exchange internet traffic locally and access major cloud platforms without routing through London or crossing the public internet — with potential benefits for performance, resilience and cost.</p>
<p>The Alliance will also advocate jointly for greater infrastructure investment in the North, and contribute a credible northern perspective to digital infrastructure strategy at a national level.</p>
<p>Tim Rainey, CNI, said:</p>
<blockquote><p>“CNI exists to make shared infrastructure work for its members and for the communities where we operate. This alliance is about taking that principle to a larger scale — bringing together organisations that each bring something different, to make a collective case for the North that none of us could make as effectively alone.”</p></blockquote>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><strong>About the Organisations</strong></p>
<p><em>Cooperative Network Infrastructure (CNI) is a cooperative society providing shared passive digital infrastructure — including dark fibre and colocation — across Greater Manchester, Blackpool, Sussex and beyond. CNI’s cooperative model enables public and private sector organisations to share infrastructure assets, reducing costs and avoiding duplication. www.cni.coop</em></p>
<p><em>LINX (London Internet Exchange) is one of the world’s largest Internet exchanges, providing neutral interconnection services to networks across the UK and internationally. LINX Manchester is a regional peering facility serving organisations across the North of England. www.linx.net</em></p>
<p><em>Greater Manchester Combined Authority (GMCA) is the established mayoral strategic authority for Greater Manchester, working with its ten constituent local authorities and a wide range of partners to drive economic growth, improve public services and deliver the Greater Manchester Strategy. [www.greatermanchester-ca.gov.uk</em></p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LINX Reinforces Commitment to Network Community with New Initiative at LINX NoVA]]></title>
            <description><![CDATA[The London Internet Exchange (LINX), a leading global Internet Exchange Point (IXP) operator and not-for-profit, member-owned organization, today announced a new initiative at its Northern Virginia ...]]></description>
            <link>https://community.linx.net/news-mvei3wws/post/linx-reinforces-commitment-to-network-community-with-new-initiative-at-dM6tEn5xNvhdwiL</link>
            <guid isPermaLink="true">https://community.linx.net/news-mvei3wws/post/linx-reinforces-commitment-to-network-community-with-new-initiative-at-dM6tEn5xNvhdwiL</guid>
            <dc:creator><![CDATA[Linx Bot]]></dc:creator>
            <pubDate>Wed, 17 Jun 2026 12:40:32 GMT</pubDate>
            <content:encoded><![CDATA[<p>The London Internet Exchange (LINX), a leading global Internet Exchange Point (IXP) operator and not-for-profit, member-owned organization, today announced a new initiative at its Northern Virginia interconnection hub, <a href="https://www.linx.net/network/linx-nova/">LINX NoVA</a>. The initiative reflects its ongoing commitment to supporting the operational needs of the network community, on a regional and global level.</p>
<p>With over three decades of experience delivering production-grade interconnection services, LINX continues to align its approach with the evolving requirements of ISPs, content networks, cloud platforms, and enterprise companies operating in one of the world’s most critical connectivity markets.</p>
<h3>Supporting a Changing Operating Environment</h3>
<p>As networks navigate increasing cost pressures and continued traffic growth, LINX has introduced a 15-month no-charge period covering port access and peering services at LINX NoVA.</p>
<p>This initiative is open to existing LINX members undertaking service upgrades, as well as organizations joining LINX for the first time. The promotion will be available for a limited period from 1 June 2026 and applies to an 18-month service term, of which the first 15 months will be provided at no charge.</p>
<p>Rather than a short-term incentive, the move reflects LINX’s broader philosophy as a member-owned organization—to listen, respond, and reinvest in ways that directly benefit the community it serves.</p>
<p>Jennifer Holmes, CEO of LINX, said:</p>
<blockquote><p>“We recognize that network operators are managing a complex environment right now, from capacity planning to cost control. As a member-owned organization, our role is to listen carefully to the feedback from our membership and monitor trends in the industry, acting where we can. This initiative is about supporting our community in a practical way—creating space for networks to plan, grow, and adapt without immediate pressure.”</p></blockquote>
<h3>A Neutral Interconnection Platform in One of the World’s Busiest Hub</h3>
<p>Since launching in 2014, LINX NoVA has established itself as a key interconnection point within Ashburn’s “Data Center Alley”, widely recognized as one of the largest and most strategically important internet hubs globally.</p>
<p>Operating as a fully resilient, carrier-neutral Internet Exchange, LINX NoVA provides a platform where networks can interconnect efficiently, keep regional traffic local, and simplify their routing architectures across multiple facilities.</p>
<p>The exchange spans five major data center campuses — Equinix, Digital Realty, Iron Mountain, CoreSite, and QTS — and supports a growing ecosystem of over 50 connected networks, including global content delivery platforms like Akamai and Amazon, service providers, and regional ISPs.</p>
<p>Through LINX’s multi-site fabric, participants can establish broad peering relationships via a single connection, reducing complexity while improving connectivity reach.</p>
<h3>Enabling Growth Without Friction</h3>
<p>The initiative allows existing LINX members to expand their presence within the Ashburn platform, while also giving networks new to LINX the opportunity to integrate, test, and evaluate interconnection strategies over a longer timeframe.</p>
<p>By removing immediate cost barriers, LINX aims to encourage more open peering, greater traffic localization, and stronger interconnection density within the region—outcomes that benefit the wider ecosystem.</p>
<p>Jennifer Holmes continues;</p>
<blockquote><p>“We want to remind our members why LINX has remained a global leader in interconnection for over 30 years. The difference is in the engineering discipline, the resilience of the platform, and the depth of operational support we provide. Not all IXPs are built the same—and when networks rely on interconnection for critical traffic paths, there’s very little margin for error. Packet loss, instability, or downtime can have a direct and immediate impact on revenue and customer experience. At LINX, we’ve built our reputation on removing that risk, delivering a level of reliability and support that our members can depend on without question.”</p></blockquote>
<h3>Built Around Operational Confidence</h3>
<p>LINX’s approach continues to focus on delivering a stable and reliable interconnection environment, backed by:</p>
<ul>
<li>A fully redundant exchange architecture designed for high availability</li>
<li>Continuous monitoring and support via a 24/7 Network Operations Center (NOC)</li>
<li>A distributed and interconnected platform spanning multiple data center sites for resilience, redundancy and flexibility</li>
<li>Scalable infrastructure supporting evolving capacity requirements</li>
</ul>
<p>&nbsp;</p>
<h3>A Long-Term Community Focus</h3>
<p>As a mutually governed organization, LINX reinvests into its platform and services for the benefit of its members, rather than external shareholders. This structure underpins its long-term approach to growth, resilience, and community collaboration.</p>
<p>This latest initiative reflects that model in action—providing tangible support where it is needed, while continuing to build a stronger, more interconnected internet ecosystem.</p>
<p><a href="https://www.linx.net/network/linx-nova/" class="btn blue">Find out more</a></p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LINX Join Mplify: Further Collaboration on LSO APIs to Accelerate Interconnection Automation]]></title>
            <description><![CDATA[Mplify [https://www.mplify.net/], a global alliance of network, cloud, cybersecurity, and enterprise organizations working together to accelerate the AI-powered digital economy, today announced the expansion of its ecosystem ...]]></description>
            <link>https://community.linx.net/news-mvei3wws/post/linx-join-mplify-further-collaboration-on-lso-apis-to-accelerate-4XcKbzqhMuWkzHD</link>
            <guid isPermaLink="true">https://community.linx.net/news-mvei3wws/post/linx-join-mplify-further-collaboration-on-lso-apis-to-accelerate-4XcKbzqhMuWkzHD</guid>
            <dc:creator><![CDATA[Linx Bot]]></dc:creator>
            <pubDate>Wed, 17 Jun 2026 12:40:31 GMT</pubDate>
            <content:encoded><![CDATA[<p><a href="https://www.mplify.net/">Mplify</a>, a global alliance of network, cloud, cybersecurity, and enterprise organizations working together to accelerate the AI-powered digital economy, today announced the expansion of its ecosystem to include Internet Exchange (IX) providers. As part of this expansion, AMS-IX, DE-CIX, and LINX have joined Mplify to collaborate on the use and evolution of Mplify’s Lifecycle Service Orchestration (LSO) APIs for IP peering, cloud on-ramp connectivity, and emerging AI-driven traffic exchange.</p>
<p>The expansion reflects Mplify’s strategy to extend standardized automation and orchestration across a broader set of digital infrastructure and interconnection services. As cloud adoption, AI workloads, and data-intensive applications continue to accelerate, the industry is facing growing demand for scalable, standards-based frameworks that enable providers to automate connectivity, improve interoperability, and support more programable Network-as-a-Service (NaaS) environments.</p>
<p>Internet Exchanges play a central role in global digital infrastructure, connecting thousands of internet service providers, cloud providers, enterprises, and content platforms worldwide. Collectively, these exchanges facilitate a massive volume of interconnection activity across the global digital ecosystem, making their participation an important step toward broader automation and interoperability. Their participation expands the reach of Mplify’s LSO APIs into a broader interconnection ecosystem, helping establish a more consistent automation framework across providers and domains.</p>
<p>“We are excited to see the leading Internet Exchanges engaging with Mplify LSO APIs as part of their broader automation strategies,” said Kevin Vachon, COO of Mplify. “Their participation represents another important step in extending the reach of milestone in the movement towards the adoption of Mplify’s API framework across the interconnection ecosystem and creating new opportunities for automation across providers, exchanges, cloud platforms, and emerging AI infrastructure.”</p>
<p>The collaboration reflects growing industry alignment around standardized APIs for interconnection automation. By leveraging Mplify’s LSO API framework, Internet Exchanges, service providers, data centers, and enterprises can support more automated, scalable, and interoperable service delivery and consumption across peering, cloud, and emerging AI-driven connectivity environments.</p>
<p>Internet Exchanges have played an important role in advancing automation through initiatives such as the Apache-licensed IX-API project. Mplify provides an opportunity to build on that work and explore broader interoperability across providers, exchanges, cloud platforms, and emerging AI infrastructure.</p>
<p>“By collaborating with Mplify, we want to explore extending the IX-API project into a complementary subsection of the LSO API portfolio, so the work the community has already done gains broader reach without losing its open, vendor-neutral character. Our IX-API project, released under Apache and shaped by the IX community, will continue, and we believe this is an opportunity to widen the surface across which all IX services can be managed and consumed,” said Riccardo Verzeni, Director of Software Engineering, LINX</p>
<p>Through its LSO API portfolio, Mplify enables automated service ordering, provisioning, orchestration, and lifecycle management across multiple provider and technology domains. The framework supports broader ecosystem interoperability and more programable service delivery across AI-ready NaaS environments.</p>
<p><em>News originally features here https://www.mplify.net/news/</em></p>
<p>&nbsp;</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LINX Launches Cost Effective Approach to Network Resilience in London]]></title>
            <description><![CDATA[The London Internet Exchange (LINX) exclusively announced a new solution at LINX126, their member meeting and AGM in London last week with one goal, to highlight the importance of complete network ...]]></description>
            <link>https://community.linx.net/news-mvei3wws/post/linx-launches-cost-effective-approach-to-network-resilience-in-london-pn9GnZiisvA1QCS</link>
            <guid isPermaLink="true">https://community.linx.net/news-mvei3wws/post/linx-launches-cost-effective-approach-to-network-resilience-in-london-pn9GnZiisvA1QCS</guid>
            <dc:creator><![CDATA[Linx Bot]]></dc:creator>
            <pubDate>Wed, 17 Jun 2026 12:40:29 GMT</pubDate>
            <content:encoded><![CDATA[<p>The London Internet Exchange (LINX) exclusively announced a new solution at LINX126, their member meeting and AGM in London last week with one goal, to highlight the importance of complete network resilience.</p>
<p><strong>LINX Metro Resilience </strong>launches on 1<sup>st</sup> July 2026 and has been developed to enable members and prospective networks to take mirrored services for less on LINX’s unique , <a rel="noopener" href="https://www.linx.net/network/lon1/">LON1</a> and <a rel="noopener" href="https://www.linx.net/network/lon2/">LON2</a>.</p>
<h4 style="margin: 14px 0 14px;"><strong>What is an Internet Exchange Point (IXP)?</strong></h4>
<p>An Internet Exchange Point or IXP is a physical location where different networks connect and exchange internet traffic directly, rather than routing through third-party networks.</p>
<p>Internet Exchange Points play a key role in helping the Internet operate efficiently and with low latency. They provide a way for a wide range of networks, including Internet Service Providers (ISPs), Content Delivery Networks (CDNs), plus other networks that rely on the Internet, to exchange traffic locally, reducing the need for longer routing paths and helping to improve overall performance.</p>
<p>When LINX first launched in 1994, there was only a single IXP in London, LON1, but as LINX became a core component of the UK’s internet infrastructure and scaled, so did the importance of reducing single points of failure and improving resilience for members.</p>
<p><a href="https://www.linx.net/lon2-and-the-linx-dual-lan-in-london/">LON2 was therefore launched in 2002,</a> and is accessible from the same data centres as the LON1 LAN but run using alternative technology for network diversity and resilience.</p>
<p>Network resilience has become increasingly critical in recent years, with networks now facing growing challenges around cybersecurity and the need to prepare for potential disruptions caused by third-party outages.</p>
<p>Last month, <a href="https://www.digit.fyi/kings-speech-outlines-cyber-security-and-resilience-bill/">the King’s speech</a> outlined a series of priorities on the Cyber Security and Resilience Bill, which is designed to strengthen the protection for critical infrastructure in the UK following a wave of major cyber-attacks.</p>
<p>As for the UK, LINX are always listening to member feedback regarding resilience and cost constraints, whilst also taking a bird’s eye view of the state of the ecosystem and where a difference can be made.</p>
<p>Megan Atkins, CCO for LINX commented;</p>
<p><em>“As a not-for-profit, membership organisation, our focus is on enhancing the resilience of our members’ networks in an increasingly fast-moving ecosystem. By developing solutions that improve stability and redundancy, we are also able to deliver meaningful cost efficiencies for our community.”</em></p>
<p>LINX Metro Resilience in London will see networks benefit from a 60% reduction on LON2 if they have mirrored services on LON1.</p>
<p>Megan continues;</p>
<p><em>“This is a great opportunity for our members and global networks to take a resilient set up in the London metro. We are pleased to be able to offer a substantial discount and what’s more, our LON2 infrastructure has had a full network refresh this year making it 400GE capable and scalable for growth.”</em></p>
<p>This initiative from LINX highlights their commitment to the networking community in the UK and internationally and will hopefully encourage further discussion around network resilience.</p>
<p>For more details see <a rel="noopener" href="https://www.linx.net/network/linx-in-london/">https://www.linx.net/network/linx-in-london/</a></p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upgrading LINX Infrastructure: New NTP Servers and a Management Network Upgrade]]></title>
            <description><![CDATA[We’ve recently completed an NTP server refresh and a management and OSS upgrade, two pieces of the infrastructure our network and exchanges quietly depend on. Below, we look at what went into each and...]]></description>
            <link>https://community.linx.net/news-mvei3wws/post/upgrading-linx-infrastructure-new-ntp-servers-and-a-management-network-YOqxnHn1U34B3wU</link>
            <guid isPermaLink="true">https://community.linx.net/news-mvei3wws/post/upgrading-linx-infrastructure-new-ntp-servers-and-a-management-network-YOqxnHn1U34B3wU</guid>
            <dc:creator><![CDATA[Linx Bot]]></dc:creator>
            <pubDate>Tue, 09 Jun 2026 11:16:14 GMT</pubDate>
            <content:encoded><![CDATA[<p>We’ve recently completed an NTP server refresh and a management and OSS upgrade, two pieces of the infrastructure our network and exchanges quietly depend on. Below, we look at what went into each and why they matter.</p>
<h4>Time Server Hardware Refresh</h4>
<p>NTP (Network Time Protocol) is how devices across a network keep their clocks in sync, distributing time from a small number of accurate sources. Those sources are time servers, and we run our own rather than relying on someone else’s – with a lot of key mechanisms all depending on it such as: log correlation during incidents, certificate validity, scheduled jobs and much more.</p>
<p>We have operated an NTP service since 1999, and the current hardware that has been operational since 2007 is now reaching end of support, which prompted this refresh. As a result we sought an ideal replacement and worked with the same engineer that supplied the original solution, <a rel="noopener" href="https://www.meinbergglobal.com/">Meinberg</a>.</p>
<p>When first launched our servers were atomic clocks, however our system now utilises a highly accurate Oven Controlled Crystal Oscillator (OCXO) that is extremely power efficient and uses about a tenth of power an atomic clock would. We operate three NTP servers, located in two different data centres. Two of these track the German time signal from Mainflingen (DCF77) and the other tracks the UK time signal from Anthorn in Cumbria (MSF) – GPS satellite time also runs on all three servers, as this approach helps protect against outages and spoofed signals.</p>
<p>Our NTP servers are also available to members if they want an additional time source.</p>
<h4>Upgrading our Management and Operational Support System (OSS)</h4>
<p>Our management and OSS runs on Juniper kit and that enables us to reach our entire estate, covering all LINX infrastructure, our exchanges and our managed exchanges.</p>
<p>As with any software and hardware, it naturally reaches end of life, and as this was approaching for us we’ve spent the past year upgrading that kit. This involved software upgrades across our internal, management and out-of-bound devices, alongside hardware upgrades at remote sites such as Wales and Manchester, as well as London.</p>
<p>This now means we have an additional two years before any mass upgrades are needed again, but equally important, it gave us a chance to test our internal networks pre and post maintenance validation checks which came about and were strengthened because of this work.</p>
<p>We pride ourselves on automation and get it in wherever we can, those validation checks run on a series of Python scripts driven by NAPALM, though the upgrades themselves we handle manually. When we come to do this again, we’d look to introduce more pre-maintenance testing alongside additional hardware in our lab.</p>
<p>In total, across a year we upgraded the following kit:</p>
<ul>
<li>London – 22 external and 4 internal (the four internal devices sit on the OSS network for our core infrastructure)</li>
<li>Manchester – 14 external facing</li>
<li>Scotland – 4 external and 2 internal</li>
<li>Wales – 2 external</li>
<li>North Virginia – 7</li>
<li>Nairobi – 4</li>
<li>Mombasa – 2</li>
<li>Accra – 3</li>
<li>KSA – 4</li>
</ul>]]></content:encoded>
        </item>
    </channel>
</rss>