Graduway Outage History

Graduway partial outage · 1 active incident View live status →

Graduway had 22 outages in the last 2 years totaling 441h 37m of downtime — averaging 0.9 incidents per month.

There were 22 Graduway outages since September 13, 2024 totaling 441h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.graduway.com

Critical August 22, 2026

"502 Bad Gateway"

Detected by Pingoru
Aug 22, 2026, 04:00 PM UTC
Resolved
Aug 24, 2026, 05:19 PM UTC
Duration
2d 1h
Affected: Web App & Database - US Region
Timeline · 5 updates
  1. investigating Aug 24, 2026, 03:19 PM UTC

    We are currently investigating an issue with Peerpal platform access and function. API is not impacted and is still working.

  2. investigating Aug 24, 2026, 03:21 PM UTC

    We are currently investigating an issue with Peerpal platform access and function. API is not impacted and is still working.

  3. identified Aug 24, 2026, 03:57 PM UTC

    An issue was identified with a beck-end process manager. Our team is currently working to correct the issue.

  4. monitoring Aug 24, 2026, 03:59 PM UTC

    A fix has been deployed to the Peepal platform. We’ll continue monitoring for stability.

  5. resolved Aug 24, 2026, 05:19 PM UTC

    This item has been resolved.

Read the full incident report →

Major July 29, 2026

Salesforce API Reconnection - Raise Saleforce Integrations

Detected by Pingoru
Jul 29, 2026, 05:34 PM UTC
Resolved
Jul 30, 2026, 07:40 PM UTC
Duration
1d 2h
Affected: Data Loads & Writebacks - Salesforce
Timeline · 3 updates
  1. investigating Jul 29, 2026, 05:34 PM UTC

    Recent Salesforce security enhancements have introduced new connection requirements. As a result, existing access and refresh tokens may have expired, requiring affected Salesforce connections to be reauthenticated. We are actively investigating additional requirements that are currently preventing certain clients from successful reconnection to the Salesforce API.

  2. monitoring Jul 30, 2026, 01:14 PM UTC

    A fix has been implemented to allow Salesforce API connections to be successfully reauthenticated. If you experience any issues while reconnecting, please contact [email protected] for further assistance.

  3. resolved Jul 30, 2026, 07:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 28, 2026

Salesforce API Blocked Connections - Raise Salesforce Clients

Detected by Pingoru
Jul 28, 2026, 07:20 PM UTC
Resolved
Jul 29, 2026, 10:01 AM UTC
Duration
14h 40m
Affected: Data Loads & Writebacks - Salesforce
Timeline · 6 updates
  1. investigating Jul 27, 2026, 03:34 PM UTC

    An IP address restriction is blocking Raise connections to all Salesforce API calls (data loads and writebacks). We are actively investigating and working with outside vendors to restore access.

  2. investigating Jul 27, 2026, 08:11 PM UTC

    We continue to investigate with outside vendors to restore access to the Salesforce API

  3. investigating Jul 28, 2026, 01:08 PM UTC

    We are continuing to work with our external vendors to restore access to the Salesforce API

  4. identified Jul 28, 2026, 07:16 PM UTC

    The issue has been identified and a fix is being implemented.

  5. monitoring Jul 28, 2026, 07:20 PM UTC

    A fix has been implemented and we continue to monitor. Writebacks and data loads should be caught up in overnight processes.

  6. resolved Jul 29, 2026, 10:01 AM UTC

    We have identified the root cause and resolved the Salesforce synchronization issue affecting data loads and write-backs. Root Cause: A recent Salesforce security enhancement introduced new connection requirements, which caused our integration to be blocked once the change took effect. Resolution: The required connection settings have been updated, and Salesforce connectivity has been fully restored. Our team is continuing to monitor the integration to ensure synchronization remains stable. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Minor June 12, 2026

FATV Video Portal Loading Issues

Detected by Pingoru
Jun 12, 2026, 09:16 PM UTC
Resolved
Jun 15, 2026, 02:12 PM UTC
Duration
2d 16h
Affected: Ocelot
Timeline · 3 updates
  1. investigating Jun 12, 2026, 09:43 PM UTC

    We are currently investigating reports of loading issues affecting the Ocelot financial aid video portal.

  2. monitoring Jun 13, 2026, 06:58 PM UTC

    FATV videos are loading successfully and the previous data fetch errors have been resolved. We will monitor the portal over the next few days to ensure continued stability.

  3. resolved Jun 15, 2026, 02:12 PM UTC

    FATV videos remain stable and fully functional.

Read the full incident report →

Major May 5, 2026

Service Interrupted for Raise Dashboards

Detected by Pingoru
May 05, 2026, 05:10 PM UTC
Resolved
May 05, 2026, 09:08 PM UTC
Duration
3h 58m
Affected: Web App & Database - US RegionWeb App & Database - CA Region
Timeline · 3 updates
  1. investigating May 05, 2026, 05:10 PM UTC

    We are investigating reports of access issues for users to the MyRaise and legacy dashboard. Our engineers are diagnosing the event and working to resolve it for you as quickly as possible. Please continue to reference this page for updates.

  2. monitoring May 05, 2026, 07:59 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 05, 2026, 09:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 5, 2026

Raise: Service Interrupted for MyRaise Dashboard

Detected by Pingoru
May 05, 2026, 01:42 PM UTC
Resolved
May 05, 2026, 03:40 PM UTC
Duration
1h 57m
Affected: Raise Prompts - US RegionRaise Prompts - CA RegionWeb App & Database - US RegionWeb App & Database - CA RegionData Loads & Writebacks - Raiser's Edge NXTData Loads & Writebacks - SalesforceData Loads & Writebacks - All Other CRMsEmail Integration - Nylas APIFTP Site - HostedFTP
Timeline · 4 updates
  1. identified May 05, 2026, 01:42 PM UTC

    We are currently investigating the issue.

  2. identified May 05, 2026, 01:46 PM UTC

    We are investigating reports of access issues for users to the MyRaise and legacy dashboard. Our engineers are diagnosing the event and working to resolve it for you as quickly as possible. Please continue to reference this page for updates.

  3. monitoring May 05, 2026, 02:27 PM UTC

    A fix is in the process of being implemented and we are monitoring the results.

  4. resolved May 05, 2026, 03:40 PM UTC

    This incident has been resolved, access to the legacy and MyRaise dashboard has been restored.

Read the full incident report →

Critical April 7, 2026

Advance - US Region - 502 Bad Gateway Errors

Detected by Pingoru
Apr 07, 2026, 04:30 PM UTC
Resolved
Apr 07, 2026, 04:30 PM UTC
Duration
Timeline · 2 updates
  1. resolved Apr 08, 2026, 03:15 PM UTC

    Our engineers have identified a load spike in the US region causing 502 Bad Gateway errors across the region.

  2. postmortem Apr 08, 2026, 03:16 PM UTC

    A system outage occurred when a routine resource scale-up triggered an unexpected de-provisioning of our environment by AWS. Services are now stable. We are currently investigating the underlying cause with AWS support to ensure this does not recur.

Read the full incident report →

Minor October 29, 2025

Raise: Temporary Raiser's Edge NXT Data Load Disruptions Due to Microsoft Outage

Detected by Pingoru
Oct 29, 2025, 08:22 PM UTC
Resolved
Oct 30, 2025, 01:07 PM UTC
Duration
16h 44m
Affected: Raise Prompts - US RegionRaise Prompts - CA RegionWeb App & Database - US RegionWeb App & Database - CA RegionData Loads & Writebacks - Raiser's Edge NXT
Timeline · 2 updates
  1. monitoring Oct 29, 2025, 08:22 PM UTC

    Notice: Microsoft is experiencing a widespread outage affecting Azure services used by Blackbaud authentication. Raise clients integrated with Blackbaud may see temporary data load failures. We’re monitoring the issue and will automatically re-run failed loads once service is restored.

  2. resolved Oct 30, 2025, 01:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

Service Restored Following AWS Outage

Detected by Pingoru
Oct 20, 2025, 08:12 PM UTC
Resolved
Oct 20, 2025, 02:15 PM UTC
Duration
Timeline · 1 update
  1. resolved Oct 20, 2025, 08:12 PM UTC

    Earlier today, our systems were impacted by a widespread outage within Amazon Web Services (AWS), specifically affecting the US-EAST-1 (N. Virginia) region. This incident caused intermittent errors and connectivity issues across multiple AWS services, including EC2, Lambda, DynamoDB, and related dependencies used by our infrastructure. As of 10.15am EST, full functionality across all Gravyty systems has been restored. Our engineering and DevOps teams closely monitored the recovery and verified that all environments and client services are now operating normally. AWS has confirmed that the root cause was an internal subsystem failure affecting network load balancer health checks and EC2 launch capacity. These issues have since been mitigated globally. We will continue monitoring AWS stability and our own systems to ensure no residual impact. No data loss or security exposure occurred during this event. Thank you for your patience and understanding.

Read the full incident report →

Major February 4, 2025

Raise - Writebacks Did Not Run Overnight

Detected by Pingoru
Feb 04, 2025, 02:44 PM UTC
Resolved
Feb 04, 2025, 08:22 PM UTC
Duration
5h 37m
Affected: Data Loads & Writebacks - Raiser's Edge NXTData Loads & Writebacks - SalesforceData Loads & Writebacks - All Other CRMs
Timeline · 3 updates
  1. investigating Feb 04, 2025, 02:44 PM UTC

    We are currently investigating reports of writebacks not processing overnight. Our engineers are diagnosing the issue to resolve it as quickly as possible for you. Please reference this page for updates.

  2. identified Feb 04, 2025, 05:13 PM UTC

    Our engineers have identified the issue which caused writebacks not to process overnight and are in the process of implementing a fix. Writebacks have restarted and are currently processing. Please reference this page for further updates.

  3. resolved Feb 04, 2025, 08:22 PM UTC

    Writebacks have all finished processing and have gone through successfully. We will continue to monitor the issue in order to confirm complete resolution and will update this site if any further issues occur.

Read the full incident report →

Major January 30, 2025

Raise - All Regions - 500 Errors when Accessing Web Editor

Detected by Pingoru
Jan 30, 2025, 01:49 PM UTC
Resolved
Jan 30, 2025, 09:30 PM UTC
Duration
7h 41m
Affected: Web App & Database - US RegionWeb App & Database - CA Region
Timeline · 5 updates
  1. investigating Jan 30, 2025, 01:49 PM UTC

    We are currently investigating reports of 500 errors when accessing the Raise Web Editor.

  2. identified Jan 30, 2025, 02:00 PM UTC

    Our engineers have identified the issue causing 500 errors when accessing the Web Editor and are in the process of implementing a fix. Please follow along on this page for updates.

  3. monitoring Jan 30, 2025, 04:04 PM UTC

    Our engineers have released a fix for the issue causing 500 errors when accessing the Web Editor, and we have confirmed that the Web Editor is now accessible. We are currently monitoring the effectiveness of the fix in order to ensure expected functionality continues. Please follow along here for additional updates.

  4. monitoring Jan 30, 2025, 05:02 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jan 30, 2025, 09:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 13, 2025

MyRaise CA Access Issue

Detected by Pingoru
Jan 13, 2025, 04:37 PM UTC
Resolved
Jan 13, 2025, 04:57 PM UTC
Duration
20m
Affected: Web App & Database - CA Region
Timeline · 2 updates
  1. identified Jan 13, 2025, 04:37 PM UTC

    We have identified an issue impacting MyRaise access for our Canadian (CA) fundraisers. Our engineers are working to diagnose the cause so that they can resolve it as quickly as possible for you. Please continue to reference this page for updates.

  2. resolved Jan 13, 2025, 04:57 PM UTC

    An issue impacting MyRaise access for our Canadian (CA) fundraisers is now resolved and services have been restored. If you have any questions about status in the future, you can always get updates at this page. Thank you.

Read the full incident report →

Critical November 29, 2024

Raise CA - First Draft Delivery Delays

Detected by Pingoru
Nov 29, 2024, 01:54 PM UTC
Resolved
Nov 29, 2024, 02:15 PM UTC
Duration
21m
Affected: Raise Prompts - CA Region
Timeline · 2 updates
  1. identified Nov 29, 2024, 01:54 PM UTC

    We have identified an issue preventing First Draft prompts from being delivered automatically this morning to Canadian fundraisers. Our engineers are aware of the issue and are currently working on a fix. Please follow along with this page for further status updates.

  2. resolved Nov 29, 2024, 02:15 PM UTC

    The issue preventing First Draft prompts from being delivered to Canadian fundraisers has been resolved and prompts are going out now to all users. Please follow along with this page for any further updates. Thank you.

Read the full incident report →

Notice November 15, 2024

Gravyty Platform - Reported Salesforce Service Disruption

Detected by Pingoru
Nov 15, 2024, 03:22 PM UTC
Resolved
Nov 15, 2024, 03:22 PM UTC
Duration
Affected: Web App, Database & API - US RegionWeb App & Database - US RegionWeb App, Database & API - EU RegionWeb App & Database - CA RegionWeb App, Database & API - CA RegionWeb App, Database & API - APAC RegionData Loads & Writebacks - Salesforce
Timeline · 2 updates

Read the full incident report →

Major November 12, 2024

Raise Web App - US Region - Degraded Service

Detected by Pingoru
Nov 12, 2024, 02:47 PM UTC
Resolved
Nov 12, 2024, 03:33 PM UTC
Duration
46m
Affected: Web App & Database - US Region
Timeline · 3 updates
  1. investigating Nov 12, 2024, 02:47 PM UTC

    We have identified an issue impacting some users of the Raise Web App in the US region. Our engineers are currently working to diagnose the cause of the issue so they can resolve it as quickly as possible. Please continue to refer to this page for updates.

  2. monitoring Nov 12, 2024, 03:22 PM UTC

    A fix for the issue has been implemented and we are seeing significantly increased responsiveness from the Raise Web App. Our team is continuing to monitor the performance of the fix before considering the issue resolved. Please continue to refer to this page for updates.

  3. resolved Nov 12, 2024, 03:33 PM UTC

    Performance has held steady since implementation of the fix and services have been restored, so we are considering this issue resolved. If you have any questions about status in the future, you can always get updates at this page. Thank you.

Read the full incident report →

Minor November 4, 2024

Raise Prompts and Web App - Degraded Service

Detected by Pingoru
Nov 04, 2024, 06:17 PM UTC
Resolved
Nov 05, 2024, 02:50 PM UTC
Duration
20h 32m
Affected: Raise Prompts - US RegionWeb App & Database - US Region
Timeline · 3 updates
  1. identified Nov 04, 2024, 06:17 PM UTC

    We have identified an issue impacting some of our customers causing intermittent slowness, errors and delays in prompt delivery, and our engineers are actively working towards a resolution. If you have any questions about the status of this issue, please subscribe to this page for updates. Thank you.

  2. monitoring Nov 04, 2024, 07:42 PM UTC

    An issue impacting some of our customers causing intermittent slowness, errors and delays in prompt delivery is now resolved and services have been restored. Our engineers are also actively monitoring this. If you have any questions about status in the future, you can always get updates at this page. Thank you.

  3. resolved Nov 05, 2024, 02:50 PM UTC

    An issue impacting some of our customers causing intermittent slowness, errors and delays in prompt delivery is now confirmed to be resolved and services have been restored. If you have any questions about status in the future, you can always get updates at this page. Thank you.

Read the full incident report →

Minor October 7, 2024

Raise Slowdown

Detected by Pingoru
Oct 07, 2024, 03:18 PM UTC
Resolved
Oct 07, 2024, 07:43 PM UTC
Duration
4h 25m
Affected: Raise Prompts - US RegionWeb App & Database - US Region
Timeline · 4 updates
  1. investigating Oct 07, 2024, 03:18 PM UTC

    Our team is investigating reports of slow performance.

  2. investigating Oct 07, 2024, 03:42 PM UTC

    Our engineers are working to investigate potential causes of slow performance. Please continue to reference this page for updates.

  3. monitoring Oct 07, 2024, 04:31 PM UTC

    Our engineers are seeing improvements with Raise's performance, and functions are returning to normal. We will continue to monitor the situation closely. Please continue to reference this page for updates.

  4. resolved Oct 07, 2024, 07:43 PM UTC

    An issue impacting Raise is now resolved and services have been restored. If you have any questions about status in the future, you can always get updates at this page. Thank you.

Read the full incident report →

Minor October 2, 2024

Follow-Up Request Delays

Detected by Pingoru
Oct 02, 2024, 06:25 PM UTC
Resolved
Oct 03, 2024, 12:42 AM UTC
Duration
6h 17m
Affected: Raise Prompts - US Region
Timeline · 3 updates
  1. investigating Oct 02, 2024, 06:25 PM UTC

    Our engineers are aware of an issue leading to delays in processing Follow-Up requests. The team is actively investigating the underlying cause and working diligently to resolve the matter.

  2. monitoring Oct 02, 2024, 06:50 PM UTC

    The issue was identified, and our engineers have successfully implemented a fix. We are now monitoring the results.

  3. resolved Oct 03, 2024, 12:42 AM UTC

    After monitoring for several hours, this issue has been resolved and performance has returned to normal levels.

Read the full incident report →

Major September 18, 2024

Raise - Issue with NXT Data Loads

Detected by Pingoru
Sep 18, 2024, 08:30 AM UTC
Resolved
Sep 26, 2024, 02:01 PM UTC
Duration
8d 5h
Affected: Data Loads & Writebacks - Raiser's Edge NXT
Timeline · 5 updates
  1. identified Sep 18, 2024, 08:30 AM UTC

    We have identified and issue that is affecting most, but not all NXT data loads and causing them to fail. Our engineers are actively working on resolving the issue and we will update as soon as we have more details.

  2. identified Sep 18, 2024, 12:25 PM UTC

    Our engineers have identified the issues and are working on releasing a fix to production.

  3. monitoring Sep 18, 2024, 08:19 PM UTC

    Our engineering team has implemented the necessary changes to address the issue. We are now actively monitoring to ensure the updates are working as expected and that there are no further disruptions. We will continue to closely observe performance and provide updates as needed.

  4. monitoring Sep 23, 2024, 07:29 PM UTC

    Our engineers have resolved an issue and continue to monitor the performance now that all NXT have sync'd

  5. resolved Sep 26, 2024, 02:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 13, 2024

Raise Prompts - Email Processing Delays

Detected by Pingoru
Sep 13, 2024, 02:07 PM UTC
Resolved
Sep 13, 2024, 10:01 PM UTC
Duration
7h 54m
Affected: Raise Prompts - US Region
Timeline · 5 updates
  1. investigating Sep 13, 2024, 02:07 PM UTC

    We are currently investigating email processing delays which are affecting Raise prompt delivery via Rapid Fire. Users will experience this issue as apparent stoppages in automated Raise prompt delivery, or very long waiting times between acting on a prompt and receiving the next prompt. For the time being, taking a second action on a prompt can restart emails in many cases. The recommended second action is a Skip action with a reason of "Already Contacted". Please follow this page for further updates.

  2. identified Sep 13, 2024, 03:05 PM UTC

    Our engineering team has identified a potential root cause for the issue and is in the process of implementing a fix. Please be aware that we are expecting approximately 10 minutes of downtime in Raise prompt delivery when the fix is deployed. We will update this page before and after any periods of downtime.

  3. identified Sep 13, 2024, 03:08 PM UTC

    We are deploying the fix now and expect Raise prompt delivery to go down for approximately 10 minutes as of the time of this update. Please follow this page for the next update on the resumption of prompt delivery.

  4. monitoring Sep 13, 2024, 03:30 PM UTC

    We have implemented a fix and we are currently monitoring the results. Raise prompt delivery has restarted.

  5. resolved Sep 13, 2024, 10:01 PM UTC

    This incident has been resolved.

Read the full incident report →