<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link rel="alternate" type="text/html" href="https://torprojectstatus.org/"/>
    <title>V3 Onion Services on Tor Project status</title>
    <link>https://torprojectstatus.org/affected/v3-onion-services/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2024-05-14T00:00:00+00:00</lastBuildDate>
    <updated>2024-05-14T00:00:00+00:00</updated>
    
    
    
      <atom:link href="https://torprojectstatus.org/affected/v3-onion-services/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] Network Performance Issues</title>
        <link>https://torprojectstatus.org/issues/2024-05-14-network-performance-issues/</link>
        <pubDate>Tue, 14 May 2024 00:00:00 +0000</pubDate>
        <guid>https://torprojectstatus.org/issues/2024-05-14-network-performance-issues/</guid>
        <category>2024-06-28 00:00:00 &#43;0000</category>
        <description>We&amp;rsquo;ve been experiencing an unusally high load on the Tor network during the last couple of weeks, which impacts the performance of onion services and non-onion services traffic. We are currently investigating potential mitigations.</description>
        <content type="html">&lt;p&gt;We&amp;rsquo;ve been experiencing an unusally high load on the Tor network during the last
couple of weeks, which impacts the performance of onion services and non-onion
services traffic. We are currently investigating potential mitigations.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Network DDoS</title>
        <link>https://torprojectstatus.org/issues/2022-06-09-network-ddos/</link>
        <pubDate>Thu, 09 Jun 2022 14:00:00 +0000</pubDate>
        <guid>https://torprojectstatus.org/issues/2022-06-09-network-ddos/</guid>
        <category>2023-05-09 09:00:00</category>
        <description>We are experiencing a network-wide DDoS attempt impacting the performance of the Tor network, which includes both onion services and non-onion services traffic. We are currently investigating potential mitigations.
Update, 2023-04-05: The DDoS has significantly reduced in volume over the last month, although there are intermittent spikes that can still affect the performance of relays that get hit by them. Overall performance has improved, but can occasionally be slower when using affected relays.</description>
        <content type="html">&lt;p&gt;We are experiencing a network-wide DDoS attempt impacting the
performance of the Tor network, which includes both onion services and
non-onion services traffic. We are currently investigating potential
mitigations.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update, 2023-04-05&lt;/strong&gt;: The DDoS has significantly reduced in volume over the last month, although there are intermittent spikes that can still affect the performance of relays that get hit by them. Overall performance has improved, but can occasionally be slower when using affected relays. We are making significant progress on implementing our &lt;a href=&#34;https://gitlab.torproject.org/tpo/core/tor/-/issues/40634&#34;&gt;Proof of Work defense&lt;/a&gt;, which should eliminate the incentive for much of these attacks. Other, more general DDoS defense work will happen after that.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update, 2022-10-25 12:00UTC&lt;/strong&gt;: There are several different kinds of overload going on that we are working on addressing. We are seeing performance degredation from an overload of exit connections and onion service circuit handshakes, causing our relays to deny circuit creations and degrade performance. Until we are able to determine mechanisms for rate limiting this activity, through development, experimentation, and testing, this DoS activity will continue to cause performance and reliability problems on the network. For details, see a &lt;a href=&#34;https://lists.torproject.org/pipermail/tor-relays/2022-October/020858.html&#34;&gt;recent thread&lt;/a&gt; on our tor-relays mailing list.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update, 2022-07-07 13:00UTC&lt;/strong&gt;: the overload we saw in the past few weeks seems
to be gone now and performance improved over the last couple of days. However,
the DDoS is not over yet, but changed its nature. We are currently investigating
how we can mitigate the new overload, which is affecting, e.g., our directory
authorities. For details, see a
&lt;a href=&#34;https://lists.torproject.org/pipermail/tor-relays/2022-July/020686.html&#34;&gt;recent thread&lt;/a&gt;
on our tor-relays mailing list.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Disruption of v3 onion services and consensus building</title>
        <link>https://torprojectstatus.org/issues/2021-01-28-dir-auth/</link>
        <pubDate>Wed, 27 Jan 2021 23:00:00 +0000</pubDate>
        <guid>https://torprojectstatus.org/issues/2021-01-28-dir-auth/</guid>
        <category>2021-01-29 05:30:00</category>
        <description>We&amp;rsquo;re currently facing stability issues with respect to our v3 onion services and consensus building. We are actively working on resolving those issues as soon as possible.</description>
        <content type="html">&lt;p&gt;We&amp;rsquo;re currently facing &lt;a href=&#34;https://lists.torproject.org/pipermail/network-health/2021-January/000661.html&#34;&gt;stability issues&lt;/a&gt; with respect to our v3 onion services and consensus building. We are actively working on resolving those issues as soon as possible.&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
