Why Are Some Memorial University Online Services Still Delayed After the Cybersecurity Vulnerability?

Updated

Memorial University says most of its online services and websites have been restored following a recent global cybersecurity vulnerability, but some users may still see delays while technical staff work to bring the remaining services back "as quickly and safely as possible." If a service is slow or unavailable, the practical response is to retry later, check mun.ca for current notices, and contact Memorial's technical support if the problem persists. This guidance applies to students, faculty, and staff trying to reach Memorial web services; it does not mean every system is fully back to normal.

What Memorial's notice actually says

The notice on the Memorial University homepage (mun.ca) makes three points:

  • Most services are back. "Many of Memorial University's online services and websites have been restored" after the vulnerability.
  • Some delays remain. Users "may experience delays" while staff restore what is left.
  • Restoration is ongoing and deliberate. Staff are working to restore remaining services "as quickly and safely as possible" — the safety qualifier explains why recovery is staged rather than instant.

The notice does not list which specific systems are still affected, does not give a completion date, and does not describe the vulnerability itself. Treat any claim about a specific system's status as unconfirmed unless Memorial posts it.

Why delays persist after a "restored" notice

A restoration notice describes the majority state, not every system. Three things typically explain the gap:

  1. Staged restoration. Systems are brought back in sequence, with verification between steps, so lower-priority services come back later.
  2. Load after reopening. When a service returns, a backlog of users and queued processes can make it slow even though it is technically up.
  3. Partial functionality. A site may load while a dependent function (login, forms, file access) still lags.

For example, a student who can open the main memorial site but finds a specific portal slow is seeing exactly the pattern the notice describes — restored overall, delayed in places.

What to do if a Memorial service is slow or down

  1. Confirm the current status first. Go to mun.ca and read the latest notice before assuming your account or device is the problem. The homepage notice is Memorial's own channel for this update.
  2. Retry after a short interval. Delays during restoration are often temporary; a later attempt may succeed without any action on your part.
  3. Reduce what you're asking for. Try the main page before a deep link, and avoid repeated rapid refreshes, which add load during a recovery period.
  4. Check for campus-wide alerts if relevant. Memorial's homepage references MUN safe campus alerts and a sign-up; these are the channel for safety-related campus notices, not a substitute for IT status updates.
  5. Contact technical support if the issue persists. The notice directs affected users to staff who are handling restoration; persistent, repeatable failures on your account are worth reporting rather than waiting out.

Expected result: you either reach the service on a later attempt, or you have a specific, reproducible problem to report — which is more useful to support than "the site is slow."

Common sticking points

  • Assuming a restored site means every feature works. The notice explicitly allows for delays; test the specific function you need, not just the homepage.
  • Treating the cybersecurity notice as a safety alert. MUN safe campus alerts cover campus safety; the services notice covers IT restoration. Don't wait on one for news about the other.
  • Repeated hard refreshes. These can worsen slowness during recovery and don't speed restoration.
  • No record of the failure. Note the time, the service, and the exact error so support can act on it.

Bottom line

Memorial's own notice is the authoritative source: most services are restored, some delays are expected, and staff are completing the remainder. Check mun.ca for updates, retry before escalating, and contact technical support with specifics if a problem persists on your account.