Rebrandly Outage History
5 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Rebrandly Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 31, 2026 | Scheduled Maintenance: Database Engine UpgradeThe scheduled database engine upgrade has been completed successfully. All services are fully operational. Total upgrade time: 2 minutes 38 seconds with no impact to link redirects or click tracking. | -1410 min | Scheduled |
| Aug 11, 2026 | Elevated DNS resolution failures on customer domainsOur 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… | 4h 22m | Resolved |
| Jul 5, 2026 | Elevated errors accessing API and web applicationThis incident has been resolved. | 32 min | Resolved |
| May 12, 2026 | Elevated error rate on link creation APIThis incident has been fully resolved. The link creation API is operating normally and the underlying cause has been addressed. Authentication and link redirection were not affected throughout the incident. We apologize… | 2h 42m | Resolved |
| Nov 18, 2025 | Intermittent 500 Errors on Generic Domain RedirectionThis incident has been resolved. | 4h 19m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Rebrandly incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Rebrandly Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Rebrandly acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Rebrandly outage in this window ran 4h 22m, against a mean recovery of 2h 59m. If you depend on Rebrandly in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.