<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>News on all2all</title>
    <link>https://all2all.org/en/news/</link>
    <description>Recent content in News on all2all</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 01 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://all2all.org/en/news/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Network intervention completed successfully</title>
      <link>https://all2all.org/en/news/network-router-upgrade-completed-20260701/</link>
      <pubDate>Wed, 01 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://all2all.org/en/news/network-router-upgrade-completed-20260701/</guid>
      <description>The planned intervention on our main router was completed successfully, including hardware replacement, migration from Quagga to FRR and improved internal redundancy.</description>
    </item>
    <item>
      <title>Planned network maintenance: router replacement on 1 July 2026</title>
      <link>https://all2all.org/en/news/planned-router-replacement-20260701/</link>
      <pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://all2all.org/en/news/planned-router-replacement-20260701/</guid>
      <description>all2all will replace one router on Wednesday 1 July 2026 between 00:00 and 05:00 CEST. Short and sporadic connectivity interruptions may occur during BGP re-establishment, routing tests and traffic checks.</description>
    </item>
    <item>
      <title>Planned network maintenance completed</title>
      <link>https://all2all.org/en/news/maintenance-reseau-planifiee-effectuee-20260626/</link>
      <pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://all2all.org/en/news/maintenance-reseau-planifiee-effectuee-20260626/</guid>
      <description>The network maintenance initially planned for 17 June 2026, later postponed to 26 June 2026, has been completed with a short overnight interruption.</description>
    </item>
    <item>
      <title>New all2all site: continuity, update, clarification</title>
      <link>https://all2all.org/en/news/nouveau-site-continuite-mise-a-jour-clarification/</link>
      <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
      <guid>https://all2all.org/en/news/nouveau-site-continuite-mise-a-jour-clarification/</guid>
      <description>A technical and editorial update of the all2all website, in continuity with our work around open standards and independent infrastructure.</description>
    </item>
    <item>
      <title>Mail infrastructure update</title>
      <link>https://all2all.org/en/news/mail-infrastructure-update/</link>
      <pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://all2all.org/en/news/mail-infrastructure-update/</guid>
      <description>Internal mail infrastructure adjustments to improve reliability, protocol consistency and compatibility with current standards.</description>
    </item>
    <item>
      <title>Outgoing mail recipient limits</title>
      <link>https://all2all.org/en/news/mail-recipient-limits/</link>
      <pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://all2all.org/en/news/mail-recipient-limits/</guid>
      <description>Standard all2all mail accounts are limited to 50 recipients per outgoing message to preserve reliable delivery.</description>
    </item>
  </channel>
</rss>
