Graduway Outage History

Graduway is up right now

Graduway had 10 outages in the last 2 years totaling 252h 50m of downtime — averaging 0.4 incidents per month.

There were 10 Graduway outages since October 20, 2025 totaling 252h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.graduway.com

Minor September 8, 2026

Advance: Content Builder Editing Unavailable

Detected by Pingoru
Sep 08, 2026, 01:42 PM UTC
Resolved
Sep 11, 2026, 04:50 PM UTC
Duration
3d 3h
Affected: Web App, Database & API - US RegionWeb App, Database & API - EU RegionWeb App, Database & API - CA RegionWeb App, Database & API - APAC Region
Timeline · 5 updates
  1. investigating Sep 08, 2026, 01:42 PM UTC

    We are investigating an issue affecting Content Box Section editing in Advance, also known as the CMS editor, which Platform Admins access via the “Edit this section” hyperlink. Administrators may encounter a blank page when attempting to edit these sections. Our team is actively investigating and working to resolve the issue as quickly as possible. Please continue to reference this page for updates.

  2. identified Sep 08, 2026, 05:48 PM UTC

    The issue has been identified and a fix has been implemented to allow for site sections to be edited.

  3. monitoring Sep 08, 2026, 05:49 PM UTC

    A fix has been implemented and we are actively monitoring the functionality.

  4. monitoring Sep 08, 2026, 10:16 PM UTC

    Identified outstanding issue for Canada (CA) region during monitoring stage, other regions working and operational as expected.

  5. resolved Sep 11, 2026, 04:50 PM UTC

    All regions correctly working for page content box system and resolved.

Read the full incident report →

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, 02:15 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 →