isitdownrightnow.app
  1. Home
  2. Services
  3. Threads
Threads threads.net

Is Threads down right now? Live status and outage tracker

No, Threads is up.

No outage detected, and no user reports in the last hour.

Live Data refreshes every 5 minutes
Not working for you? Help centre
User reports, last 24 hours, 15 minutes a segment: 96 flowing, 0 slow (elevated), 0 jammed (outage)

User reports, last 24 hours

22 reports in total, counted in 15-minute windows

No problem reports came in for Threads in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 22 reports. Worldwide, most recent reports were about login (75%) and website (25%). There has been no spike in reports since 13 October. These are user reports from the US, where most people report Threads problems.

Around the world right now: normal in 71 other countries. By country

In the past 24 hours, 22 user reports came in for Threads. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day. The busiest 15-minute window had 4 reports, about 14 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Reports, last hour
0
Quiet
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
4
4 reports, 14 h ago
Last 24 hours

Threads outages and problems

In the past 24 hours, 22 user reports came in for Threads. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 4 reports, about 14 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for Threads stayed at their usual level the whole time.
This month

Threads in November 2026

Problem reports in November
31

Monthly report for November 2026

What went wrong

What people said was wrong in recent problem reports for Threads worldwide.

  1. Login75%
  2. Website25%

Share of 4 recent reports that said what was wrong, from every country listed below.

World map

Threads reports around the world

In the last 24 hours, 33 problem reports about Threads came in from 7 countries. Right now reports are at the usual level in every country.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.
CountryNowLast hour24 hours
The US numbers above Normal 225
Indonesia Normal 02
Taiwan Normal 02
France Normal 01
Sweden Normal 01
Canada Normal 01
Brazil Normal 01
The UK Normal 00
Ireland Normal 00
Croatia Normal 00
Belgium Normal 00
Germany Normal 00

Each country's status compares its reports with the usual level there. 60 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

Threads problem spikes, last 30 days

Since 13 October, Threads had no outage spikes or periods of elevated reports.

  • Sun 4 Oct: no data
  • Mon 5 Oct: no data
  • Tue 6 Oct: no data
  • Wed 7 Oct: no data
  • Thu 8 Oct: no data
  • Fri 9 Oct: no data
  • Sat 10 Oct: no data
  • Sun 11 Oct: no data
  • Mon 12 Oct: no data
  • Tue 13 Oct: 2 reports
  • Wed 14 Oct: 0 reports
  • Thu 15 Oct: 0 reports
  • Fri 16 Oct: 0 reports
  • Sat 17 Oct: 0 reports
  • Sun 18 Oct: 3 reports
  • Mon 19 Oct: 0 reports
  • Tue 20 Oct: 0 reports
  • Wed 21 Oct: no data
  • Thu 22 Oct: 0 reports
  • Fri 23 Oct: 0 reports
  • Sat 24 Oct: 0 reports
  • Sun 25 Oct: 0 reports
  • Mon 26 Oct: 0 reports
  • Tue 27 Oct: 0 reports
  • Wed 28 Oct: 10 reports
  • Thu 29 Oct: 23 reports
  • Fri 30 Oct: 28 reports
  • Sat 31 Oct: 22 reports
  • Sun 1 Nov: 23 reports
  • Mon 2 Nov: 8 reports

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

  • The US115
  • Indonesia12
  • Canada10
  • Hong Kong10
  • Brazil7
  • India5
  • The UK4
  • Taiwan4

Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 13 October 2026. Monthly reports for all services

Troubleshooting

How to fix Threads not working

Threads is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach threads.net over your own connection, right now. Nothing is sent to us or stored.

  1. Force quit Threads

    Swipe the app card away in your recent apps view, then open Threads again. This clears a stuck feed or a reply that will not send. Force quit does not log you out.

  2. Update Threads

    Open the App Store or Google Play, then install any pending update for Threads. An old build can fail to load replies or post after the service changes something on its end. If no update is listed, skip this step.

  3. Sign out of Threads

    In the app, go to your profile, tap the menu icon at the top right, open Settings, then choose Account and Log out. Sign back in with the same method you used before. A broken session can block posting and loading, and this rebuilds it.

  4. Reinstall Threads

    Delete the app from your home screen or app drawer, then install it again from the App Store or Google Play. This removes the local copy and any cached data. You will need to sign in again.

While Threads is down: what to use instead

  • Instagram Use it when you want to share updates with photos, Stories, or short videos.
  • Bluesky Try it for text posts and public conversations while the app is unavailable.
  • Mastodon Choose it for community-based discussions across independent servers.
  • X Use it for short public updates, replies, and live event conversations.
Your device

Fix Threads on Windows, Mac, Android and iPhone

Threads on Windows

Fix
Clear your browser cache or try accessing Threads through a different browser like Chrome or Edge. If using the Windows app, reset or reinstall it via the Microsoft Store.
Check
Try loading the Threads website in an incognito window to see if it loads. You can also check online outage detectors to see if others are experiencing issues with Threads.
Command Prompt
ping threads.netTest whether Threads's servers reply
nslookup threads.netCheck that Threads's DNS resolves
tracert threads.netTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

Threads on Mac

Fix
Clear Safari or Chrome's cache and cookies, or try disabling browser extensions that might block Threads. Ensure your macOS is updated to prevent compatibility issues.
Check
Attempt to open Threads in a private Safari window to rule out local browser issues. Check if other websites load normally to verify your Mac's internet connection.
Terminal
ping -c 4 threads.netTest whether Threads's servers reply
nslookup threads.netCheck that Threads's DNS resolves
traceroute threads.netTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Threads on Android

Fix
Force stop the Threads app and clear its cache in your Android settings, or update it via the Google Play Store. Reinstalling the Threads app can also resolve persistent launch errors.
Check
Check if other apps load content to confirm your Android device is online. You can also look at the Google Play Store reviews for Threads to see if others are reporting recent bugs.

Threads on iPhone and iPad

Fix
Force close the Threads app and reopen it, or check the App Store for any pending updates. If Threads still won't load, reinstall the app from the App Store.
Check
Verify your iPhone's connection by loading a webpage, or check the App Store reviews for Threads to see if a recent update is causing widespread issues.
Busiest times

When people report Threads problems

The busiest hour for reports about Threads is 17:00 to 18:00 Central European time, and the busiest day is Thursday.

By hour of the day

  • 00:00 to 01:00: 0.3 reports on an average day
  • 01:00 to 02:00: 0.28 reports on an average day
  • 02:00 to 03:00: 0.15 reports on an average day
  • 03:00 to 04:00: 0.38 reports on an average day
  • 04:00 to 05:00: 0.3 reports on an average day
  • 05:00 to 06:00: 0.09 reports on an average day
  • 06:00 to 07:00: 0.11 reports on an average day
  • 07:00 to 08:00: 0.05 reports on an average day
  • 08:00 to 09:00: 0 reports on an average day
  • 09:00 to 10:00: 0 reports on an average day
  • 10:00 to 11:00: 0.07 reports on an average day
  • 11:00 to 12:00: 0.17 reports on an average day
  • 12:00 to 13:00: 0.12 reports on an average day
  • 13:00 to 14:00: 0.07 reports on an average day
  • 14:00 to 15:00: 0.27 reports on an average day
  • 15:00 to 16:00: 0.24 reports on an average day
  • 16:00 to 17:00: 0.27 reports on an average day
  • 17:00 to 18:00: 0.41 reports on an average day
  • 18:00 to 19:00: 0.34 reports on an average day
  • 19:00 to 20:00: 0.13 reports on an average day
  • 20:00 to 21:00: 0.16 reports on an average day
  • 21:00 to 22:00: 0.29 reports on an average day
  • 22:00 to 23:00: 0.08 reports on an average day
  • 23:00 to 00:00: 0.3 reports on an average day

By day of the week

  • Monday: 2.2 reports on an average Monday
  • Tuesday: 0.5 reports on an average Tuesday
  • Wednesday: 3.3 reports on an average Wednesday
  • Thursday: 7.5 reports on an average Thursday
  • Friday: 7 reports on an average Friday
  • Saturday: 5.5 reports on an average Saturday
  • Sunday: 6.4 reports on an average Sunday

Each bar is the average number of user reports in that hour, or on that day of the week, from 26 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

About

What happens when Threads goes down

Threads is a text-based social app from Instagram where people post short updates and reply to each other. When it goes down, your home feed stops loading and new posts or replies fail to send, which interrupts casual scrolling and the work of creators who use the app to talk with their audience.

During an outage, the home feed usually stalls first: pull to refresh spins and older posts stay in place. Posting and replying often hang next, and direct messages can sit unsent with a retry option that does nothing until service returns. Problems are frequently partial, so you might load your feed on Wi-Fi while a friend on mobile data sees the same failure; regional clusters are common because reports depend on where people are and which network they use. If the trouble lasts, check the help centre at https://help.threads.net/ for login or account access questions, but this page only counts user problem reports above their usual level and does not test the service itself.

Servers and network

Threads IP address, servers and network

IPv4 address
57.144.248.192
IPv6
2a03:2880:f37a:c0:face:b00c::43fe
Network
AS32934 · Facebook, Inc., registered in Ireland
DNS hosted by
Meta
HTTPS certificate
Issued by DigiCert Inc, valid until 9 Nov 2026 (6 days)
HTTP/3
Supported
Our check
Answered in 387 ms

Checked from our server in Frankfurt, Germany, 20 h ago, for www.threads.net. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from www.threads.net. Fastest from Vienna (61 ms), slowest from Singapore (186 ms). Every location connected through Facebook, Inc. (AS32934), using 11 different addresses.

LocationResultTimeAddress reached
FrankfurtGermanyUp · HTTP 30162 ms57.144.154.192
ViennaAustriaUp · HTTP 30161 ms31.13.84.52
MilanItalyUp · HTTP 301110 ms157.240.203.63
ParisFranceUp · HTTP 301183 ms157.240.196.63
AmsterdamNetherlandsUp · HTTP 301113 ms57.145.4.192
MadridSpainUp · HTTP 301120 ms57.144.118.192
WarsawPolandUp · HTTP 301147 ms57.144.110.192
Los AngelesUSAUp · HTTP 30190 ms57.144.202.192
São PauloBrazilUp · HTTP 301148 ms57.144.232.192
SingaporeSingaporeUp · HTTP 301186 ms57.144.186.192
TokyoJapanUp · HTTP 301148 ms157.240.31.63

Checked with check-host.net from its servers in these cities 20 h ago, for www.threads.net. Time is how long each server took to load the page.

Questions

Threads FAQ

Is Threads down right now?
The status at the top of this page shows whether problem reports for the service are above their usual level, counted in 15-minute windows over the last 24 hours. This site does not ping or probe the service, so it cannot tell you if a server is down from your specific location. If other apps and websites load on the same connection but Threads alone fails, the problem is probably on the service side; if everything fails, switch to another network or device to confirm.

Why does my Threads feed say "Couldn't refresh feed"?
That message usually means the app cannot reach its servers or your session needs a refresh. Close the app from the app switcher and open it again; if the error stays, check whether the service is having a wider problem by looking at the report level on this page. Logging out and back in through your Instagram account fixes a stale token for some people.

Why can't I log in to Threads with my Instagram account?
If your Instagram login works elsewhere but the app rejects it, the issue is often a password change or a locked Instagram account. Try logging in to Instagram directly first, then return to the app; if Instagram asks for a security check, finish that before trying again. The Threads help centre at https://help.threads.net/ has account recovery steps if the problem follows your Instagram account.

Why won't photos or videos upload to Threads?
Uploads fail most often because the file is too large or the connection dropped mid-post. Check that the photo or video opens in your gallery, then grant photo access in your phone settings and try a smaller file. If the post still sits on a spinning circle, close and reopen the app, then check the report level here to see if others are hitting the same wall.

Why does Threads say "Sorry, something went wrong" when I like or reply?
That error often appears when the app cannot complete a small write action, which can happen during a partial outage or after a long time offline. Tap the like or reply again after a few seconds; if it fails twice, restart the app and test a different action, such as opening a profile or scrolling the feed. If the same error hits every action, the problem is likely on the service side.
For your site

Put the Threads status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

Threads status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/threads/"><img src="https://isitdownrightnow.app/badge/threads.svg" alt="Threads status" height="20"></a>
Markdown, for README files
[![Threads status](https://isitdownrightnow.app/badge/threads.svg)](https://isitdownrightnow.app/services/threads/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track Threads

The status on this page comes from user-submitted problem reports for Threads, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Threads, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Threads doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.

Elsewhere

Check other services

See all 500+ services

Problems elsewhere right now

Strips: user reports, last 6 hours, 15 minutes a segment.