General Issues

Incident Report for Bitly

Postmortem

A configuration error related to deprecation of an unrelated API endpoint incorrectly affected API calls to POST /v4/custom_bitlinks causing them to error with a HTTP 500 response in some circumstances .

From 2020-08-17 through 2020-09-13 this caused 5.4% of API requests to error.
From 2020-09-14 00:00 UTC through 2020-09-14 21:26 UTC all requests errored.

Posted Sep 16, 2020 - 17:52 EDT

Resolved

This incident has been resolved.

Posted Sep 14, 2020 - 17:34 EDT

Monitoring

Good news, community: if you were impacted by the earlier issues on our /v4/custom_bitlinks API, you should now be able to use these endpoints without any problems. Thanks for bearing with us! For more info on this incident please see our status page: status.bitly.com

Posted Sep 14, 2020 - 17:29 EDT

Identified

Update: We're continuing to investigate errors on our /v4/custom_bitlinks API endpoints. Our team is laser-focused on implementing a fix. Thanks for your patience!

Posted Sep 14, 2020 - 16:36 EDT

Investigating

Hi community. We’re seeing indications of elevated errors impacting our /v4/custom_bitlinks API endpoints for some of our users. We’re looking into this now and will share an update within 30 minutes.

Posted Sep 14, 2020 - 16:25 EDT

This incident affected: API.

Subscribe to Incident