Skip to main content

Is Linktree Down?

No — Linktree is up

Reachable from all 8 checked regions

Average response time: 377ms

Last checked · checks run every 6 hours

Official status page: https://status.linktr.ee

Linktree uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
268ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 18 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

18-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: 100.00% uptime, 16 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 39 checks
Aug 17: 100.00% uptime, 31 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 40 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
24ms
DNS 0ms TCP 1ms TLS 6ms TTFB 13ms
arn
18ms
DNS 0ms TCP 0ms TLS 5ms TTFB 9ms
bom
2105ms
DNS 0ms TCP 20ms TLS 43ms TTFB 1999ms
cdg
25ms
DNS 0ms TCP 1ms TLS 8ms TTFB 18ms
dfw
114ms
DNS 0ms TCP 0ms TLS 94ms TTFB 105ms
ewr
59ms
DNS 0ms TCP 7ms TLS 16ms TTFB 33ms
sjc
188ms
DNS 0ms TCP 1ms TLS 6ms TTFB 181ms
syd
16ms
DNS 0ms TCP 0ms TLS 5ms TTFB 8ms
yyz
660ms
DNS 0ms TCP 0ms TLS 5ms TTFB 652ms

What Linktree does

Linktree hosts a single landing page holding every link a creator or business wants to share, used mostly from the one link an Instagram or TikTok profile allows. A visitor taps the profile link, lands on the linktr.ee page and chooses a destination. For a lot of small businesses it is the only route from social media to a shop, a booking page or a mailing list.

What an outage looks like

The linktr.ee page returns an error or a blank screen for visitors while your own editor still loads, because the public profiles and the admin side are reported as separate components. Pages load without their images or theme. An edit saves without taking effect for visitors, and tap analytics stop recording, so traffic looks like it dried up rather than like the page failed.

What to do about it

Check status.linktr.ee, which reports Profiles, the public page visitors reach, separately from Admin, the editor you sign into, each with a seven-day uptime figure. Open your own linktr.ee address in a private window to see what a visitor sees. If Profiles is affected, point the link in your social profile at a direct destination for the duration rather than waiting it out.

Is it down for everyone, or just you?

If this page says Linktree is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Webflow
Webflow
Buffer
Buffer
Patreon
Patreon
Hootsuite
Hootsuite

Linktree outage FAQ

Is my Linktree down, or is it Instagram?
Open your linktr.ee address directly in a browser rather than through the app. Instagram and TikTok open links in an in-app browser that can fail on its own, so a page that works in a normal browser but not from the profile points there rather than at Linktree. If neither works, status.linktr.ee reports Profiles separately from Admin and will tell you which side is affected.
Can I still edit my page while it is down?
Sometimes. Admin and Profiles are separate components, so the editor can be unavailable while public pages serve normally, or the reverse. An edit made while Profiles is degraded may save correctly and simply not reach visitors yet. Avoid making the same change repeatedly, and check the public page in a private window once the incident closes rather than trusting the editor preview.
Do I lose my links during an outage?
No. Links are stored on Linktree's side, and an availability incident stops the page being served rather than emptying it. Everything returns when the service does. What is genuinely lost is analytics for the period, since taps can only be counted on a page that loads. A page that stays gone after the incident closes is an account matter rather than an outage.
What should I do while it is down?
Change the link in your social profile to a direct destination, usually your shop, booking page or newsletter signup, and change it back afterwards. That takes a minute and keeps the traffic you would otherwise lose. Posting that your link is broken helps much less than giving people somewhere to go, because most visitors do not come back for a second attempt.
Why does my page load for me but not for someone else?
Caching is the usual reason. A page you visited recently can be served from your browser or a network cache while a fresh request fails, which makes an incident look specific to one person's device. A private window, a different device or a mobile connection gives a truer answer. Visitors in different regions can also see different results during the same incident.

How we measure this

  • We request Linktree's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Linktree publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Linktree goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required