Rebrandly logo

Is Rebrandly Down?

AnalyticsLive status, outages, and incident history

No. Rebrandly is up right now.

Every monitored Rebrandly system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · every 60s

Know the moment Rebrandly breaks

Rebrandly is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Rebrandly status page
How we know: the official Rebrandly status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Rebrandly Status Summary

As of 22:54 UTC on 9 November 2026, Rebrandly is operational. PulsAPI checked Rebrandly's official status page and found 10 of 10 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Rebrandly, counting degraded performance as up.

Cite as: PulsAPI, “Rebrandly status”, checked 9 November 2026, 22:54 UTC. https://www.pulsapi.com/services/rebrandly

Rebrandly Component Status

The main Rebrandly systems on this page. All 10 are operational right now.

10operational
Branded Links redirect · Domain Names managed outside Rebrandly
Operational
Branded Links redirect · Domain Names registered via Rebrandly
Operational
Generic short URLs redirect
Operational

7 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Login / Signup, Rebrandly API, Rebrandly Apps, Rebrandly clicks tracking, Rebrandly Dashboard, Rebrandly Website.

See all of them free

Component statuses may change independently during partial outages.

Recent Rebrandly Outages & Incidents

Incident history from the official Rebrandly status page, including resolution updates.

No recent incidents reported by the vendor.

Rebrandly Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Rebrandly incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history90 days observed
Aug 12100.00% averageNov 9

Going further back: Rebrandly uptime by month and every recorded Rebrandly outage.

Live Rebrandly Outage Reports

Problems reported by engineers using Rebrandly. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Rebrandly problems reported yet.

Something wrong with Rebrandly on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Rebrandly

Rebrandly publishes a public status page at status.rebrandly.com covering 10 components, including Rebrandly Website, Rebrandly Dashboard and Generic short URLs redirect. PulsAPI tracks Rebrandly outages, degraded performance and incident history in real time, alongside the rest of your analytics stack.

Over the past 30 days, PulsAPI has measured Rebrandly uptime at 100.00%. Response times, incident history, and SLA tracking for Rebrandly are available on the PulsAPI dashboard.

Rebrandly Status FAQ

Is Rebrandly down right now?

The verdict at the top of this page comes from the latest poll of the official Rebrandly status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Rebrandly is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Rebrandly recovers.

How do I check Rebrandly uptime history?

PulsAPI tracks Rebrandly uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Rebrandly changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Rebrandly outages?

PulsAPI reads the official Rebrandly status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Rebrandly components?

Yes. PulsAPI monitors 10 individual Rebrandly components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Rebrandly goes down?

Yes. Create a free account and subscribe to Rebrandly: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Rebrandly to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Rebrandly problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Rebrandly?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Rebrandly plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Rebrandly with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services