New Multi-region uptime checks and custom-domain status pages

Rebrandly Outage History

Daily provider-status observations and published incident history for Rebrandly.

Operational

Rebrandly is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Rebrandly for future changes.

100% of 36 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 30 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

3 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

August 2026
Elevated DNS resolution failures on customer domains
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
Recovery continues to progress. The majority of affected domains are resolving again, and we expect the remainder to follow shortly as caching clears across the internet. Our team is actively verifying restoration across affected domains. We will confirm full resolution here as soon as it's been verified.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
Our DNS provider has begun restoring service. Domain names registered via Rebrandly are progressively starting to resolve again. Because DNS answers are cached across the internet, individual domains can take up to an hour after restoration to work for all visitors. We are verifying recovery across affected domains and will confirm full resolution here.
identified
We continue to work with our third-party DNS provider to resolve the DNS resolution issue affecting domain names purchased through Rebrandly. The provider currently expects services to begin resolving in the next hour. We will confirm here as soon as service is restored, or sooner if anything changes.
identified
We have identified elevated DNS resolution failures affecting a large portion of domains purchased through Rebrandly. Affected domains, and any short links on them, may not resolve for visitors during this time. Domains not purchased through Rebrandly, and our core rebrand.ly and rb.gy links, are not affected. The issue originates with a third-party DNS hosting provider. They have identified the cause and are working on a fix. We will post an update as soon as we have more information.
July 2026
Elevated errors accessing API and web application
Source not attested
Last archived state: resolved
View archived record details
monitoring
A new SSL certificate has been deployed and service to our API and web application has been restored. We're now monitoring closely to confirm everything is functioning as expected.
identified
We're currently experiencing an issue affecting connections to our API and web application due to an expired SSL certificate. Users may see security warnings or be unable to load the dashboard and API endpoints. We've identified the root cause and are actively deploying a fix. We expect service to be fully restored within approximately 30 minutes. We'll post an update as soon as the fix is live. Thank you for your patience.
May 2026
Elevated error rate on link creation API
major Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been deployed and customer-facing error rates have returned to normal levels. We are monitoring for stability before declaring the incident fully resolved. Authentication and link redirection remain unaffected. We will provide another update within 1 hour.
identified
We have identified the cause as a cache configuration issue in our link creation path. A fix is now being deployed across our infrastructure, and we expect customer-facing error rates to begin returning to normal as the deployment completes. Authentication and link redirection remain unaffected. We will provide another update within 1 hour.
investigating
We have addressed one contributing factor (database write throttling) and are continuing to investigate a separate factor that is keeping customer-facing error rates elevated. Authentication and link redirection remain unaffected. We will provide another update within 1 hour.
investigating
We are investigating elevated error rates (403s & 500s)on the Rebrandly link creation API. Some customers may receive "permission denied" responses when creating links via the API, and bulk creation requests may complete with fewer links than requested. Authentication and link redirection are not affected, and existing links continue to work normally. We will provide an update within 1 hour