Bitly Outage History
4 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Bitly Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Apr 25, 2026 | Major Service Outage - Bitly.com Website UnavailableThe incident affecting availability of bitly.com has been resolved and the website is fully operational. | 6 min | Resolved |
| Mar 16, 2026 | Partial Outage Impacting Pricing and PackagingThe issue has been identified and resolved. We will continue to monitor. | 37 min | Resolved |
| Feb 12, 2026 | Intermittent Provider IssuesThis incident has been resolved. | 176h 31m | Resolved |
| Jan 5, 2026 | Sporadic Login Issues with Support PortalThis incident has been resolved. | 1h 21m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Bitly incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Bitly Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Bitly acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Bitly outage in this window ran 7d 8h, against a mean recovery of 1d 20h. If you depend on Bitly in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.