Skip to main content
Bitly logo

Is Bitly Down?

No — Bitly is up

Reachable from all 8 checked regions

Average response time: 360ms

Last checked · checks run every 6 hours

Official status page: https://status.bitly.com

Bitly uptime

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

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 16 checks
Jun 29 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
161ms
DNS 0ms TCP 2ms TLS 5ms TTFB 107ms
arn
148ms
DNS 0ms TCP 5ms TLS 8ms TTFB 130ms
lhr
289ms
DNS 1ms TCP 1ms TLS 4ms TTFB 92ms
nrt
540ms
DNS 0ms TCP 1ms TLS 5ms TTFB 165ms
ord
140ms
DNS 0ms TCP 12ms TLS 21ms TTFB 80ms
sin
838ms
DNS 0ms TCP 1ms TLS 4ms TTFB 249ms
sjc
236ms
DNS 0ms TCP 9ms TLS 12ms TTFB 105ms
syd
729ms
DNS 0ms TCP 1ms TLS 5ms TTFB 276ms
yyz
91ms
DNS 0ms TCP 1ms TLS 3ms TTFB 38ms

What Bitly does

Bitly shortens links and measures the clicks on them, with custom domains for branded short links. Those links are printed on packaging, embedded in campaigns and shared in messages that cannot be edited afterwards, so a redirect failure breaks destinations that are already out in the world and beyond recall.

What an outage looks like

Short links fail to resolve, showing an error instead of forwarding to the destination, which affects everyone who clicks rather than only Bitly users. Custom domain redirects can fail while bit.ly links work, or the reverse. The dashboard will not load, blocking link creation. Click metrics stop updating and webhook deliveries stall, so reporting undercounts.

What to do about it

Check bitly.statuspage.io, which reports Bit.ly Redirects and Custom Domain Redirects separately from the website, the API, Metrics and Webhook Delivery, so a broken dashboard does not mean live links are failing. The redirect path is the one that matters to your audience; if it is affected, share the destination URL directly while it recovers.

Is it down for everyone, or just you?

If this page says Bitly 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

Bitly outage FAQ

Do my existing short links stop working during a Bitly outage?
Only if the redirect components are affected. Bitly reports Bit.ly Redirects and Custom Domain Redirects separately from the dashboard and API, so links frequently keep resolving while you cannot log in to create new ones. Test a link yourself rather than assuming that a dashboard you cannot reach means your audience is blocked.
Why do my custom domain links fail when bit.ly links work?
They are separate components with separate infrastructure. Custom domain redirects also depend on your own DNS pointing at Bitly, so a failure there can be your configuration rather than an incident. If bit.ly links resolve and yours do not while the status page is green, check the domain's DNS records before contacting support.
Are click statistics lost during an outage?
Metrics is its own component and can lag behind redirects. Clicks that happened while metrics were degraded may be counted late, or may not be recorded at all, so a dip in the graph does not necessarily mean a dip in traffic. Avoid drawing campaign conclusions from a window that overlapped an incident.
Can I create new links while Bitly is down?
Not if the website or API is affected, since both are needed to mint a link. For an urgent campaign, using the full destination URL is better than waiting, even though it is longer and untracked. A link you cannot create is a smaller problem than a deadline missed waiting for the dashboard.
What happens to links printed on materials if Bitly fails?
They fail for as long as the redirect is down, and there is nothing you can do about the printed copy. This is the structural risk of short links on physical media. Using a custom domain you control gives you a route to repoint DNS elsewhere in a prolonged incident, which a bit.ly link does not.

How we measure this

  • We request Bitly'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 Bitly publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Bitly 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