Is Bitly Down?

No — Bitly is up

Bitly's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 528 ms

Right now

The verdict is the worse of these two. How we decide

Bitly's status page

status.bitly.com · read 4 minutes ago · checked every 3 minutes

Operational

Bitly's components, as its status page reports them
Component	Status
Bit.ly Redirects	Operational
Custom Domain Redirects	Operational
Website (Bitly.com)	Operational
API	Operational
Metrics	Operational
Webhook Delivery	Operational
Bitly Pages	Operational

Open their status page

FlareWarden checks

bitly.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 528 ms
Checked: 1 hour ago

By region

Ashburn reachable, 106 ms
Frankfurt reachable, 395 ms
Johannesburg reachable, 966 ms
London reachable, 327 ms
Los Angeles reachable, 501 ms
Newark reachable, 211 ms
São Paulo reachable, 750 ms
Tokyo reachable, 970 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	65 ms	1 ms	5 ms	97 ms
Frankfurt	6 ms	2 ms	6 ms	123 ms
Johannesburg	213 ms	2 ms	5 ms	455 ms
London	63 ms	3 ms	7 ms	175 ms
Los Angeles	190 ms	3 ms	5 ms	277 ms
Newark	126 ms	8 ms	11 ms	172 ms
São Paulo	151 ms	1 ms	5 ms	303 ms
Tokyo	174 ms	1 ms	5 ms	366 ms

We check that bitly.com loads, not every feature behind it. Test it yourself

History

Incidents Bitly reported

Since Oct 22, 15 days · from status.bitly.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Bitly website availability

Measured by FlareWarden · bitly.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 515ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of bitly.com from multiple regions every 6 hours. Bitly's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three 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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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 the verdict is the worse of what it reports and what our checks see: a major outage of Bitly itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Bitly goes down

We check Bitly every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required