Is Rebrandly down?
Last checked 8m agoNo incidents right now.
Rebrandly is operational right now. Last checked 8m ago; the most recent incident resolved 20d ago.
Real-time Rebrandly status, recent outages, and incident history — pulled directly from Rebrandly's official status page at https://status.rebrandly.com every 5 minutes. Pingoru tracks 10 Rebrandly services and has captured 3 incidents in the last 90 days (99.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Rebrandly reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Branded Links redirect (Domain Names registered via Rebrandly)
Timeline · 7 updates
- identified · Aug 11, 2026, 07:04 PM UTC
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.
- identified · Aug 11, 2026, 07:39 PM UTC
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.
- monitoring · Aug 11, 2026, 07:58 PM UTC
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.
- monitoring · Aug 11, 2026, 10:02 PM UTC
We are continuing to monitor for any further issues.
- monitoring · Aug 11, 2026, 10:08 PM UTC
We are continuing to monitor for any further issues.
- monitoring · Aug 11, 2026, 10:09 PM UTC
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.
- resolved · Aug 11, 2026, 11:26 PM UTC
Our DNS provider has restored the hosted DNS service, and we have verified that domain names registered via Rebrandly are resolving normally again. Links and QR codes on these domains are working. If a specific domain still does not open for you, it is most likely lingering DNS cache and should clear typically within an hour, and in rare cases up to a few hours depending on your network's DNS provider. We will publish a review of this incident after we complete our follow-up with the provider.
Latest: Our DNS provider has restored the hosted DNS service, and we have verified that domain names registered via Rebrandly are resolving normally again. Links and QR codes on these doma…
-
- Rebrandly DashboardRebrandly API (Classic Workspaces)Rebrandly API (Extended Workspaces)Login / Signup
Timeline · 3 updates
- identified · Jul 05, 2026, 01:00 PM UTC
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.
- monitoring · Jul 05, 2026, 01:04 PM UTC
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.
- resolved · Jul 05, 2026, 01:33 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Started Aug 11, 2026, 07:04 PM UTC · Resolved Aug 11, 2026, 11:26 PM UTC · 4h 22m
- Started Jul 05, 2026, 01:00 PM UTC · Resolved Jul 05, 2026, 01:33 PM UTC · 32m