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

Raisely incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 5, 2026Scheduled 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 0mScheduled
Oct 19, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.30 minScheduled
Oct 9, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Oct 6, 2026Australian campaign sites slow or unavailableThe fix has been deployed. Thank you for your patience while we resolved the issue.13 minResolved
Aug 14, 2026Intermittent Service DisruptionThis incident has been resolved.1h 27mResolved
Jul 28, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.2h 30mScheduled
Jul 16, 2026Scheduled MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Jul 6, 2026Strava 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 minResolved
Jul 6, 2026Disruptions to Raisely ServicesAPI performance has returned to normal. This issue is now resolved. Thank you for your patience.3 minResolved
Jun 22, 2026Disruptions to Raisely ServicesThis incident has been resolved.2h 32mResolved
Jun 15, 2026Intermittent Disruptions to API ServicesThe incident has been resolved.2h 49mResolved
Jun 1, 2026Service 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 0mResolved
May 25, 2026Service 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 minResolved
May 19, 2026Blank pages being detected for some usersThis incident has been resolved.24 minResolved
Apr 21, 2026Profile Page Loading IssuesWe have resolved an issue that was preventing profile pages from loading. All systems are now operating normally.-156 minResolved
Apr 6, 202643 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 minResolved
Mar 18, 2026Raisely images showing broken iconsThis issue is now resolved. Images are loading correctly across the platform.35 minResolved
Mar 12, 2026Custom Email Sending Domain Verification ErrorThis issue has been resolved.23h 9mResolved
Mar 11, 2026Issue loading css on specific campaign templatesThis incident has been resolved.16 minResolved
Mar 6, 2026Minor increase in database load resulting in intermittent performance degradation on the Raisely appThis incident has been resolved.74h 47mResolved
Feb 6, 2026Raisley 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 minResolved
Feb 4, 2026Issue 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 4mResolved
Jan 29, 2026Message 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 0mResolved
Jan 16, 2026Raisely 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 minResolved
Jan 5, 2026SMS Two-Factor Authentication (2FA) FailuresThis incident has been resolved.11h 0mResolved
Dec 9, 2025Donation Pages Loading SlowlyThis incident has been resolved.1h 10mResolved
Dec 9, 2025Donation Events not Syncing IntermittentlyThis incident has been resolved3h 38mResolved
Nov 23, 2025Scheduled MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Nov 18, 2025Cloudflare Global OutageThis incident has been resolved.7h 41mResolved
Nov 10, 2025User Login Auth ErrorsThis issue has been fully resolved. We appreciate your patience and apologize for any inconvenience caused by this.22 minResolved
Nov 10, 2025Message Processing DelaysThis issue is resolved now. The performance of the messaging queue has returned to normal.174h 6mResolved

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.