bonusly Outage History

12 incidents recorded over the last 365 days, 11 of them resolved, 1 still open. 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 bonusly Incident

bonusly incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Rewards Fulfillment OutageWe are continuing to work with our providers on this issue. We are also looking for other ways to restore more catalog options in the interim.—Investigating
Oct 26, 2026Difficulty Claiming RewardsWe’re looking into an issue affecting some reward redemptions. If you recently redeemed points for a reward, it may show as “pending” in your account. Our team is actively investigating, and we’ll post an update here…19 minResolved
Sep 30, 2026Redemptions failingOk, all failed reward redemptions have been reprocessed. We're good to go, and the system is working nominally.1h 28mResolved
Apr 7, 2026Degraded Rewards ExperienceThis incident has been resolved.3h 0mResolved
Mar 6, 2026Activity Feed Performance IssueMonitoring the situation confirms performance is nominal. Thanks for your patience!6h 33mResolved
Mar 2, 2026Rewards Fulfillment IntermittentWe've successfully retried all failed redemptions from this morning. New rewards are being fulfilled as expected. Thanks for riding through this with us!1h 23mResolved
Jan 30, 2026Slower than normalPerformance continues to be nominal after several hours of monitoring, and we're marking this incident as resolved.2h 40mResolved
Jan 9, 2026Bonusly Support System IssueOur partners have resolved the issue.1h 19mResolved
Dec 24, 2025Captcha verifications are failing.Our fix is now deployed and we're seeing normal volume of successful username/password logins.1h 13mResolved
Dec 19, 2025Performance IssueThis is now resolved40 minResolved
Nov 21, 2025Rewards Catalog UnavailableThis issue has been resolved, Rewards are now accessible.9 minResolved
Nov 18, 2025Bonusly AvailabilityService continues to operate as normal. This issue with Cloudfare is now resolved.7h 21mResolved

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 bonusly 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 bonusly 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 bonusly 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 bonusly outage in this window ran 7h 21m, against a mean recovery of 2h 22m. If you depend on bonusly 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.