Ouriginal Outage History

Ouriginal is up right now

Ouriginal had 2 outages in the last 2 years totaling 1h 29m of downtime — averaging 0.1 incidents per month.

There were 2 Ouriginal outages since October 30, 2025 totaling 1h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://pckyl3dhlrb4.statuspage.io

Notice June 4, 2026

Ouriginal Service Incident - 4th of June 2026

Detected by Pingoru
Jun 04, 2026, 03:05 PM UTC
Resolved
Jun 04, 2026, 10:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 04, 2026, 03:05 PM UTC

    We've fixed it! Due to an unexpected service incident, users using SSO may have been unable to access reports or log in to Ouriginal by Turnitin today. We are pleased to advise that service has been restored. The incident occurred between the following times: PDT: Thursday, 4th June, 02:00 - Thursday, 4th June 07:19 BST: Thursday, 4th June, 10:00 - Thursday, 4th June, 15:19 AEST: Thursday, 4th June, 19:00 - Friday, 5th June, 00:19 CEST: Thursday 4th June, 11:00 - Thursday 4th June, 16:19 We regret any inconvenience this may have caused if you were impacted by today's incident.

Read the full incident report →

Minor October 30, 2025

Unexpected Service Incident

Detected by Pingoru
Oct 30, 2025, 07:37 AM UTC
Resolved
Oct 30, 2025, 09:07 AM UTC
Duration
1h 29m
Affected: Ouriginal Plagiarism Detection Result Interface
Timeline · 2 updates
  1. investigating Oct 30, 2025, 07:37 AM UTC

    We've run into some issues. Ouriginal by Turnitin is currently experiencing an unexpected service incident. During this time, you may find that reports load slowly or fail to display. We invite you to track the progress of this incident while we work to bring the service back to optimum health.

  2. resolved Oct 30, 2025, 09:07 AM UTC

    We've fixed it! Due to an unexpected degradation of the Ouriginal plagiarism detection result interface, you may have experienced that that reports loaded slowly or failed to display in Ouriginal by Turnitin today. We are pleased to advise that service has been restored. The incident occurred between the following times: PDT: Wednesday 29th, 01:11am - Thursday 30th, 01:23am GMT: Wednesday 29th, 08:11am - Thursday 30th, 08:23am AEDT: Wednesday 29th, 19:11 - Thursday 30th, 19:23 We regret any inconvenience this may have caused if you were impacted by today's incident.

Read the full incident report →