Bitly status history
Current state: operational — “All Systems Operational” per https://status.bitly.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Bitly incidents last?
From 7 incidents with a vendor-posted start and resolve time. Longest on record: Intermittent Provider Issues — 7.4 days (2026-02-12 17:49 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (7)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-04-25 23:04 UTC | Major Service Outage - Bitly.com Website Unavailable | resolved | critical | 6 min |
| 2026-03-16 19:42 UTC | Partial Outage Impacting Pricing and Packaging | resolved | none | 37 min |
| 2026-02-12 17:49 UTC | Intermittent Provider Issues | resolved | minor | 7 d 8 h |
| 2026-01-05 21:42 UTC | Sporadic Login Issues with Support Portal | resolved | major | 1 h 21 min |
| 2025-09-12 12:38 UTC | Provider outage affecting email sends | resolved | none | 1 h 32 min |
| 2025-09-12 08:46 UTC | Provider outage affecting email sends | resolved | none | 1 h 37 min |
| 2025-09-11 23:21 UTC | Provider outage affecting [product functonality] | resolved | major | 59 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Bitly with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"bitly"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
