Tor Project status

[Resolved] DNSSEC outage

Sat, 20 Sep 2025 17:40:10 +0000

All services are affected by a major DNS outage.

It seems like DNSSEC key rotations happened sooner than expected: the rotation was planned for November 2025, and it happened today, breaking DNS resolution for all torproject.org domains around 2025-09-20 17:40:10UTC.

Keys were updated in the .org registry at around 19:32UTC. With the one hour time-to-live record on .org DS records, we expect this outage will be fully resolved by 20:32UTC.

The .net domains have a much longer time to live (a full day), and we believe this lessened the impact of the outage on that domain. The DS keys were updated at 20:32UTC, which gave a window of about three hours for the outage on that domain, for which the outage is actually a full day, with service fully returning on 2025-09-21 20:32.

Details in the GitLab incident tpo/tpa/team#42297.

[Resolved] GitLab maintenance

Wed, 25 Jun 2025 10:52:41 -0400

GitLab is having various issues: mail not going out, merge requests failing. On top of that, it’s running out of disk space.

We’re doing an emergency maintenance on the server, we’re hoping for this to resolve within one or two hours.

Details of this are available in tpo/tpa/team#42218 which, of course, might not be available right now archive.org copy.

[Resolved] Graphs on Metrics website are not updated beyond 2025-05-31

Tue, 10 Jun 2025 11:00:00 +0000

We’re aware of a problem that prevents the graphs on metrics.torproject.org from updating beyond 2025-05-31. Requesting data and graphs for timeframes before that is working fine, though. We are actively working on resolving this issue as soon as possible.

[Resolved] BridgeDB graphs on Metrics website are not shown

Thu, 10 Apr 2025 13:00:00 +0000

We’re aware of a problem that prevents the BridgeDB related information on metrics.torproject.org from being rendered. This affects the BridgeDB requests by transport and distributor graphs in particular. The underlying data is available in the respective .csv files, though. We are actively working on resolving this issue as soon as possible.

[Resolved] Issues with Ubuntu packages on deb.torproject.org and its Onion Service

Tue, 25 Feb 2025 10:02:59 -0500

We are aware of two issues related to deb.torproject.org that we are working on fixing:

The first issue is the Ubuntu packages are missing when using apt. Tor has, for a while, had flaky CI across our entire infrastructure due to Docker upstream adding rate-limiting for their images, and our different teams have been working on moving to our own Docker images with our own container registry.

Things went a bit too fast here, but we expect to have x86-64 and aarch64 packages for the Ubuntu releases out again very soon. This should NOT negatively impact your current installs of Tor, but apt will be unhappy when you do an apt update until this is resolved (expected eta: 1 day).

Followup on this issue in tpo/tpa/team#42052.

In addition to the situation with the Ubuntu packages, we are also aware of an issue with the Onion Service provided for deb.torproject.org being unreachable/unstable, see tpo/tpa/team#42054.

Update: The Ubuntu builds for focal,jammy,noble and oracular are back, as are the arm64 builds for all suites on both Debian and Ubuntu.

We dropped the lunar and mantic Ubuntu releases after we experienced some issues building these packages. Since both releases have been out of support for several months at this point, hopefully that won’t be too much of an issue.

If you notice the unfamiliar package version suffix, +tpo1, that’s expected: those are packages specific to deb.torproject.org.

[Resolved] Router maintenance at Hetzner

Tue, 03 Dec 2024 03:30:00 +0000

Hetzner has planned an emergency maintenance window on all of their routers, which will cause a network outage on all of our hosts in their datacenters. The maintenance window is planned on December 3rd 2024 from 3:30 UTC to 5:30 UTC, during which the network may experience spurious outages.

Services should come back online automatically as soon as network connectivity is restored by Hetzner.

[Resolved] GitLab migration to another machine cluster

Thu, 28 Nov 2024 18:00:00 +0000

Starting on November 28th at 18:00 UTC, gitlab.torproject.org will be taken offline in order to migrate it to our other machine cluster.

The transfer time is currently estimated at 18h, so gitlab will be coming online on the next day, friday 29th. If we’re lucky the transfer might finish sooner.

If you have any issues during that time, please reach out to us on IRC or via email.

[Resolved] Nextcloud down

Mon, 25 Nov 2024 13:15:00 +0000

Tor’s Nextcloud (https://nc.torproject.net) is down since at least Nov 25th 13:01 UTC. Our service provider (Riseup) has been notified and we’ll update this page as soon as we have more information.

UPDATE: Service is back, we don’t yet have info about what happened.

[Resolved] Switching mail servers

Mon, 25 Nov 2024 11:00:00 +0000

On November 25st 2024, starting at 11:00 UTC, we will be switching to new mail servers for receiving and forwarding mail sent to torproject.org. If all goes well, there will be no downtime and deliverability to external providers like gmail will improve.

If all does not go well, please reach out on IRC or file an issue on Gitlab, do not mail us since e-mail may obviously not be reliable. For more details on how to get in touch and how to report e-mail problems, see: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/support

Update: all went well :)

[Resolved] Power maintenance at Qupra

Thu, 21 Nov 2024 00:00:00 +0000

Qupra had planned a power maintenance window for their entire datacenter, which could have caused outage on two of the Tails servers that are hosted there. The maintenance window was planned on November 21st 2024, but no exact time window has been communicated.

The maintenance did not result in any downtime.

[Resolved] Riseup network unreachable

Tue, 12 Nov 2024 04:00:00 +0000

The network in which our Nextcloud instance and large sections of the Tails infrastructure are hosted is currently unreachable.

Riseup is working with their upstream providers to resolve the issue, but there is currently no clear indication when it will be resolved. More information can be found on Riseup’s own status page.

Update, 2024-11-12, 13:10 UTC: we have moved the Nextcloud instance to a new IP address and it should become available again once DNS caches have expired (this may take up to three hours).

[Resolved] Mailman 3 upgrade

Mon, 04 Nov 2024 14:00:00 +0000

TL;DR: Mailman 3 upgrade happened on November 4th, starting at 14:00 UTC, and ending around 21:00 UTC. Report issues on GitLab.

As mentioned in early October, we’re in the process of upgrading our main mail server, which includes upgrading to the shiny new Mailman 3 platform. This will involve short per-list outage as each migrates over to the new server. It’s unclear how long the maintenance will last, but assume mailing lists will be disrupted all day, although each migration should only take a couple of minutes each.

We have, right now, a prototype mailman 3 server available at:

https://lists-01.torproject.org/

The TPA mailing list has been succesfully migrated already and next week, I’ll start migrating the other mailing lists (including this one!).

Be warned that Mailman 3 is a significant upgrade from Mailman 2. There are some great things (like unified authentication), and some less great things (like a more complex design and “shinier” web interface that might not be everyone’s taste).

As a reminder, we’re doing this upgrade a little rushed because the main mail server is now unsupported for security upgrades. See the details of the proposal here:

https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-71-emergency-email-deployments-round-2

… with the upgrade work being tracked in this issue:

https://gitlab.torproject.org/tpo/tpa/team/-/issues/40471

[Resolved] schleuder maintenance

Mon, 07 Oct 2024 12:00:00 +0000

Schleuder lists administration will be down for maintenance on Monday around 12:00 UTC, equivalent to 05:00 US/Pacific, 09:00 America/Sao_Paulo, 08:00 US/Eastern, 14:00 Europe/Amsterdam.

Schleuder lists will be migrated to a new server with a more recent schleuder version. Mail delivery should be unaffected, but changes in the list configuration or keys made during the maintenance window may be lost.

The migration is expected to take no more than one hour, but no less than 15 minutes.

See the discussion issue for more information and feedback:

https://gitlab.torproject.org/tpo/tpa/team/-/issues/41796

[Resolved] donate website maintenance

Wed, 02 Oct 2024 16:00:00 +0000

Donation site will be down for maintenance on Wednesday around 14:00 UTC, equivalent to 07:00 US/Pacific, 11:00 America/Sao_Paulo, 10:00 US/Eastern, 16:00 Europe/Amsterdam.

Update: maintenance was delayed by 2 hours, so this is now 09:00 US/Pacific, 13:00 America/Sao_Paulo, 12:00 US/Eastern, 16:00 UTC, 18:00 Europe/Amsterdam.

We’re having latency issues with the main donate site. We hope that migrating it from our data center in Germany to the one in Dallas will help fix those issues as it will be physically closer to the rest of the cluster.

Outage is expected to take no more than two hours, but no less than 15 minutes.

See the discussion issue for more information and feedback:

https://gitlab.torproject.org/tpo/tpa/team/-/issues/41775

[Resolved] Network Performance Issues

Tue, 14 May 2024 00:00:00 +0000

We’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.

[Resolved] Tor Weather outage

Tue, 19 Mar 2024 15:00:00 +0000

We are in the process of upgrading Tor Weather to version 2.0. For more information about the details and expected downtime, see the tracking ticket. We are sorry for the inconvenience.

[Resolved] Tor Check outage

Wed, 31 Jan 2024 03:25:07 +0000

We are currently investigating a Tor Check outage that started after upgrading the underlying operating system to the latest Debian Stable release. Details and more context can be found in our Gitlab bug tracker. Sorry for the inconvenience.

[Resolved] ExoneraTor outage

Tue, 02 Jan 2024 19:25:00 +0000

We are currently investigating an unusually high and sustained load on the ExoneraTor service, causing most queries to time out, resulting in a 502 “Proxy Error” page. Details and more context can be found in our Gitlab bug tracker Sorry for the inconvenience.

[Resolved] Gitlab and CollecTor outage

Wed, 06 Dec 2023 14:00:00 +0000

We’ve experienced heavy load and unresponsiveness on some of our services (e.g. Gitlab and CollecTor) leading to outages and disruptions.

The issue seems to have resolved itself, investigation seemed to show this was a routing issue upstream.

Update: issue have crept up again, root cause was elevated temperature with the hard drives on the affected server. Upstream has replaced fans in the server and situation has returned to normal.

See issue tpo/tpa/team#41429 for detailed analysis and updates.

[Resolved] Tor Weather data loss

Fri, 27 Oct 2023 06:23:11 +0000

The Tor Weather service broke during an upgrade to Debian Bookworm. The database was destroyed (but eventually recovered from backups) and the service was down for about a week.

Specifically, all changes made after 2023-10-27 06:23:11 UTC have been lost. The service itself went offline some time before 2023-10-31 20:33UTC, therefore about 4 days of data was lost. The data loss was due to a flaw in the bookworm upgrade procedure, since then corrected, combined with expiration of the continuous backups which would normally have allowed full recovery.

If you have registered or made any changes on Tor Weather after October 27th, you will need to redo those changes.

The service was restored on November 8th (2023-11-08 18:29UTC) from the October 27th backup. So the service was offline for a little over 8 days, from October 31th to November 8th.

A more detailed discussion and post-mortem can be found in issue 41388, including a full timeline of the incident, heroic deleted file recovery procedures, and future improvements to our systems that should keep this specific problem from happening again.

It is not in our habit to lose data, and we apologize profusely for this mishap.

[Resolved] donate website maintenance

Tue, 30 May 2023 03:00:00 +0000

Planned maintenance on the donate.torproject.org website will make it inaccessible for a few hours.

The service should be restored at 2023-05-30 05:00:00 +0000.

For details, see https://gitlab.torproject.org/tpo/tpa/team/-/issues/41109

[Resolved] donate website maintenance

Mon, 08 May 2023 02:00:00 +0000

Planned maintenance on the donate.torproject.org website will make it inaccessible for a few hours.

The service should be restored at 2023-05-08 05:00:00 +0000.

For details, see https://gitlab.torproject.org/tpo/tpa/team/-/issues/41109

[Resolved] Tor Weather outage

Tue, 04 Apr 2023 21:00:00 +0000

We needed to take down Tor Weather temporarily as it was spamming the tor-commits mailing list. Once we have an acceptable solution to that problem it will be re-enabled. Sorry for the inconvenience.

[Resolved] Tor Weather outage

Thu, 30 Mar 2023 12:41:00 +0000

Shortly after launching our new Tor Weather service the relay operator tornth found a serious violation of privacy expectations that resulted in suspending the Tor Weather service until that issue gets fixed. We are sorry for that inconvenience.

[Resolved] outage at main provider

Sat, 04 Feb 2023 01:57:31 +0000

We are witnessing a large outage at our main service provider, Hetzner. According to the information we have gathered so far, four switches (4!) have failed and that affects four (yes, again, 4!) of the servers in the 8-node Ganeti cluster.

Affected servers:

check-01
chives
colchicifolium
cupani
fsn-node-01
fsn-node-02
fsn-node-04
fsn-node-07
gitlab-02
gnt-fsn
henryi
loghost01
majus
materculae
media-01
onionoo-backend-01
onionoo-backend-02
onionoo-frontend-02
perdulce
polyanthum
relay-01
static-master-fsn
staticiforme
submit-01
tbb-nightlies-master
weather-01

Upstream resolved the situation after a few hours of downtime. According to Hetzner it was “a short disruption of a line card in one of our access routers”. Details of the incident are available in tpo/tpa/team#41057.

[Resolved] DNS services disruption

Wed, 07 Dec 2022 03:15:00 +0000

We are currently experiencing a higher than normal load on our DNS infrastructure, and have received several reports of DNS resolution failures, especially from users of Google DNS.

Update, 2022-12-08: We have deployed mitigations that appear to have successfully restored the service to usual levels.

See issue tpo/tpa/team#40996 for details.

[Resolved] Email delivery problems

Wed, 30 Nov 2022 20:00:00 +0000

We have had repeated reports over the past weeks of delivery failures, particularly at Gmail but it’s possible it affects mail delivery across the board.

Update, 2022-12-05: we are deploying emergency workarounds, see issue tpo/tpa/team#40981 for progress updates.

Update, 2022-12-14: DMARC, SPF records and DKIM signatures on outgoing mail hosts deployed, reputation improved. May impact negatively users not using the submission server.

Update, 2022-12-15: mail services considered restored, see TPA-RFC-45 or further improvements.

[Resolved] Network DDoS

Thu, 09 Jun 2022 14:00:00 +0000

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. We are making significant progress on implementing our Proof of Work defense, which should eliminate the incentive for much of these attacks. Other, more general DDoS defense work will happen after that.

Update, 2022-10-25 12:00UTC: 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 recent thread on our tor-relays mailing list.

Update, 2022-07-07 13:00UTC: 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 recent thread on our tor-relays mailing list.

[Resolved] routing issues at main provider

Tue, 25 Jan 2022 06:00:00 +0000

We are experiencing intermittent network outages that typically resolve themselves within a few hours. Preliminary investigations seem to point at routing issues at Hetzner, but we have yet to get a solid diagnostic. We’re following that issue in issue 40601.

[Resolved] Disruption of Metrics website and relay search

Thu, 03 Jun 2021 08:00:00 +0000

We’re currently facing stability issues with respect to our Metrics website and relay search. We are actively working on resolving those issues as soon as possible.

[Resolved] V2 Onion Services deprecation

Thu, 06 May 2021 16:45:00 +0000

If you are an onion site administrator, you must upgrade to v3 onion services as soon as possible.

As we announced last year, v2 onion services will be deprecated and obsolete in Tor 0.4.6.x. As of April 2021, Tor Browser Alpha uses this version of Tor and v2 addresses no longer work in this and future versions of Tor Browser Alpha.

When Tor Browser stable moves to Tor 0.4.6.x in October 2021, v2 onion addresses will be completely unreachable.

Why are we deprecating v2 onion services? Safety. Technologies used in v2 onion services are vulnerable to different kinds of attacks, and v2 onion services are no longer being developed or maintained. The new version of onion services provides improved encryption and enhanced privacy for administrators and users.

It’s critical that onion service administrators migrate to v3 onion services and work to inform users about this change as soon as possible.

[Resolved] Disruption of v3 onion services and consensus building

Wed, 27 Jan 2021 23:00:00 +0000

We’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.

[Resolved] Email delivery problems to Google

Mon, 25 Jan 2021 21:40:00 +0000

Google mail servers are currently bouncing some emails coming from @torproject.org, as sent from our main mail server (eugeni) and third-party servers. This includes lists but may not include all our mail servers (the donation platform, for example, seems to still work).

We are still investigating the problem, followup in issue 40149.

Update, 22:16UTC: it looks like only some emails are being bounced, especially a particular email from a particular sysadmin which made him jump the gun and post this disruption notice. We might actually be in our normal “somewhat disrupted” delivery situation. Stay tuned for more happy days.

Update, 2021-01-27 16:51UTC: it turns out this was a false alarm, and concerns only a single Google group that is refusing emails. Emails are being delivered to Google fine.