Bitly incident

Intermittent Provider Issues

Minor Resolved View vendor source →
Started
Feb 12, 2026, 05:49 PM UTC
Resolved
Feb 20, 2026, 02:21 AM UTC
Duration
7d 8h
Detected by Pingoru
Feb 12, 2026, 05:49 PM UTC

Affected components

Bit.ly Redirects

Update timeline

  1. monitoring Feb 12, 2026, 05:49 PM UTC

    We have received reports of intermittent DNS resolution issues on bit.ly due to residual caching from a recent provider outage. These issues should dissipate over the next several hours. We continue to monitor the situation. Note that while you may see interruptions in connections your audience may not.

  2. monitoring Feb 17, 2026, 12:40 AM UTC

    We continue to monitor this issue with several ISPs showing resolution. If you are encountering this issue, we would appreciate knowing what ISP (Internet Service Provider) you are on when you report the issue. We are working with affected ISPs to get the erroneous DNS entries cleared from their residual cache layers.

  3. monitoring Feb 20, 2026, 12:34 AM UTC

    This incident has been resolved at the root cause layer for several days, and it seems that residual DNS cache layers have now cleared.

  4. resolved Feb 20, 2026, 02:21 AM UTC

    This incident has been resolved.

Looking to track Bitly downtime and outages?

Pingoru polls Bitly's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Bitly reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Bitly alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Bitly for free

5 free monitors · No credit card required