TurnItIn had advised that this issue was affecting all TurnItIn services worldwide, including access to the service, assignment submissions, the feedback studio, and similarity report processing.
We encountered a disruption between the following times: 14:52 – 07:06 GMT Feb 15-16, 2019. We’re pleased to announce that this has been resolved. Please accept our apologies if you were impacted by the disruption.
The following Turnitin services will be unavailable on January 5, 2019:
- Turnitin and TurnitinUK (including all integrations and Turnitin Early Adopter Program)
- Feedback Studio for iOS
To ensure that services remain stable, particularly during high submission periods, this maintenance will include several hardware updates and performance improvements.
When will services be unavailable?
GMT January 5 16:00 – 00:00 (January 6)
How will you be affected?
Turnitin’s machines require a health check every now and again… Users will be unable to submit, grade, or access our service during this maintenance window, so please ensure that any submission deadlines are adjusted to fall outside of the window.
Stay up to date with Turnitin system status by following @TurnitinStatus on Twitter.
Turnitin Service was unavailable from 10.56-13.19 – Resolved and confirmed at 13.30
Students and staff cited issues accessing TurnitinUK services this morning for the purposes of eSubmission, marking and also use of the Turnitin Feedback Studio for iPad app. Upon accessing inboxes and submission areas, users received a ‘503’ error. Turnitin Support resolved the issue and notified us at 13.19 on Thursday 25th October.
Following on from the prior day of March 27th, the Turnitin Feedback Studio was unavailable again on the 28th. The service seemed to be down from 11am through 5pm.
This outage was again an international issue with Turnitin’s servers, and was not localised to only the University of Brighton.
There may be continuing issues with the service, so we have labeled it “Service At Risk” over the Easter Holiday.
It was brought to our attention first thing on the morning of March 27th that users were unable to view content in the Feedback Studio in Turnitin. This disruption made it impossible to do marking with the service. The problem may have also effected syncing between the Turnitin App on iOS and the Turnitin system itself.
We’ve discovered that this problem was UK-wide and affected most institutions.
Turnitin engineers were informed of the problem. At approximatey 11:30am on the 27th, service was resumed, and the Feedback Studio began showing content once again.
We apologise for any issues that our staff may have had during this latest disruption to our Turnitin service.
Blog sites were not effected, meaning the pages were visible, however, Edublogs admin-areas were experiencing issues with re-directing, thus frustrating our users efforts to edit and create new blog posts/pages in Edublogs. Service seemed to be down sometime in the afternoon of March 13th.
We put in a ticket with our external supplier that afternoon. On Saturday the 17th, Edublogs contacted us, and told us that the problem was fixed. Upon testing the blogs on Monday morning on the 19th of March, we were pleased to confirm that the blogging system was back up and running correctly.
We apologise for any issues you may have encountered during this time-frame.
Current issues with logins to blogs.brighton.ac.uk
We are currently experiencing issues with logins to Edublogs (blogs.brighton.ac.uk). The blogs themselves are viewable and working properly, however the ability to edit and/or create new blogs is affected, you may see “redirect” error screens.
Our external provider for Edublogs has been contacted, and their developers are working to solve the problem.
Our apologies for the unexpected issue with the Edublogs service, please do not hesitate to contact us with any queries on this matter.
Service was lost sometime around 16:00 on the 13th of March.
Edublogs has been having some issues with the creation of new blogs. The problem was first reported on October 30th, 2017. This issue had to do with a mistaken institutional-wide installation of a particular plug-in called CoursePress.
The plug-in was disabled for our institution (but allowed for individual blogs). This seems to have fixed the redirect issue at the time by the morning of the the 30th of October, 2017.
A new re-direct issue has been found today November 10th. The redirect looks quite similar to the former problem, but is a bit different.
A ticket with CampusPress (our Edublogs provider) has been entered into the system by T.MacNeill at 9:30am on November 10th. We’re awaiting a response from our service provider.
UPDATE: As of 12 noon on November 10th, 2017 – The page for blog creation is now redirecting correctly. We are unsure as to the cause of this morning’s re-direct problems. Please ensure that you clear your browser history, before re-attempting to create a blog.
At approximately 14:25 on Tuesday October 17th, Edublogs returned a 404 error when someone attempted to use it. You may have also encountered a strange .php file error that looked something like this:
According to our external Edublogs-providers, there was a code update running that unexpectedly affected our network. The update was killed and the network was brought back online.
The blogs were down for only 30 minutes after the problem was discovered.
For approximately four hours, today 5-9-17, our ability to edit our Edublogs-hosted web pages and Blogs was lost.
The front-end of the pages continued working, thus this was not a serious service impact. The problem was noticed approximately around noon, and Edublogs was notified immediately. The backend system was restored by 15:45.
If any issues remain, please do contact the Service Desk at x4444