Raisely Outage History
31 incidents recorded over the last 365 days, 25 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 Raisely Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 5, 2026 | Scheduled MaintenanceWe're doing a quick system update to keep Raisely running smoothly. The platform may be unavailable for approximately 15 minutes during the times below: - PST: 6:30AM - 7:30AM (Monday, November 9th) - AEDT: 1:30AM -… | 1h 0m | Scheduled |
| Oct 19, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Oct 9, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Oct 6, 2026 | Australian campaign sites slow or unavailableThe fix has been deployed. Thank you for your patience while we resolved the issue. | 13 min | Resolved |
| Aug 14, 2026 | Intermittent Service DisruptionThis incident has been resolved. | 1h 27m | Resolved |
| Jul 28, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 30m | Scheduled |
| Jul 16, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jul 6, 2026 | Strava integration incidentWhen: July 2 – July 6, 2026 (~11:50 AM Pacific) What happened: Strava changed their developer requirements and our app was temporarily inactive, so athletes could not connect or reconnect Strava. Impact: New links and… | -123 min | Resolved |
| Jul 6, 2026 | Disruptions to Raisely ServicesAPI performance has returned to normal. This issue is now resolved. Thank you for your patience. | 3 min | Resolved |
| Jun 22, 2026 | Disruptions to Raisely ServicesThis incident has been resolved. | 2h 32m | Resolved |
| Jun 15, 2026 | Intermittent Disruptions to API ServicesThe incident has been resolved. | 2h 49m | Resolved |
| Jun 1, 2026 | Service Disruption: Connectivity IssuesResolved – The connectivity issues affecting Raisely have been fully resolved. After a period of monitoring, we can confirm that all systems, dashboards, and campaign pages are completely stable and operating as… | 2h 0m | Resolved |
| May 25, 2026 | Service Disruption: Connectivity IssuesThe issues affecting the Raisely platform have been fully resolved. All systems are now 100% operational, and users should be able to us the platform as usual. We apologize for the disruption and appreciate your… | 2 min | Resolved |
| May 19, 2026 | Blank pages being detected for some usersThis incident has been resolved. | 24 min | Resolved |
| Apr 21, 2026 | Profile Page Loading IssuesWe have resolved an issue that was preventing profile pages from loading. All systems are now operating normally. | -156 min | Resolved |
| Apr 6, 2026 | 43 background donation webhook jobs failedA recent deployment caused 43 donation webhook events to fail. We identified and fixed the underlying issue promptly. Our team is working to process the failed webhook events ASAP. We apologise for the inconvenience. | 0 min | Resolved |
| Mar 18, 2026 | Raisely images showing broken iconsThis issue is now resolved. Images are loading correctly across the platform. | 35 min | Resolved |
| Mar 12, 2026 | Custom Email Sending Domain Verification ErrorThis issue has been resolved. | 23h 9m | Resolved |
| Mar 11, 2026 | Issue loading css on specific campaign templatesThis incident has been resolved. | 16 min | Resolved |
| Mar 6, 2026 | Minor increase in database load resulting in intermittent performance degradation on the Raisely appThis incident has been resolved. | 74h 47m | Resolved |
| Feb 6, 2026 | Raisley API LatencyBetween 4:00-4:20 AM PST, a spike requests to our API caused temporary delays across Raisely's APIs. We've identified the root cause and fixes will be implemented to prevent this going forwards. API performance has… | 0 min | Resolved |
| Feb 4, 2026 | Issue with Admin Design & Menu PreviewsThe issue affecting Admin design and menu previews has been resolved. Our team has verified the fix, and all preview functionality is now fully restored. Thank you for your patience while we worked to resolve this. | 1h 4m | Resolved |
| Jan 29, 2026 | Message Page Reloading Performance IssueThe issue with Message page reloads is fully resolved. We thank you for your patience while we worked towards a resolution. | 8h 0m | Resolved |
| Jan 16, 2026 | Raisely API Elevated Latency and TimeoutsWe experienced elevated latency on the Raisely API yesterday (15th Jan 2026), which resulted in request timeouts for downstream services. The root cause of the increased latency is still under investigation. | 0 min | Resolved |
| Jan 5, 2026 | SMS Two-Factor Authentication (2FA) FailuresThis incident has been resolved. | 11h 0m | Resolved |
| Dec 9, 2025 | Donation Pages Loading SlowlyThis incident has been resolved. | 1h 10m | Resolved |
| Dec 9, 2025 | Donation Events not Syncing IntermittentlyThis incident has been resolved | 3h 38m | Resolved |
| Nov 23, 2025 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Nov 18, 2025 | Cloudflare Global OutageThis incident has been resolved. | 7h 41m | Resolved |
| Nov 10, 2025 | User Login Auth ErrorsThis issue has been fully resolved. We appreciate your patience and apologize for any inconvenience caused by this. | 22 min | Resolved |
| Nov 10, 2025 | Message Processing DelaysThis issue is resolved now. The performance of the messaging queue has returned to normal. | 174h 6m | 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 Raisely 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 Raisely 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 Raisely 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 Raisely outage in this window ran 7d 6h, against a mean recovery of 11h 13m. If you depend on Raisely 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.