Resolved Prior Outages

2025 - July

On Saturday Friday 25 July at about 08h00EDT/13h00BST it was noticed that TRP wasn't accessible. This was subsequently identified as an issue with the underlying server running the site. We are currently waiting on a resolution to this issue from our service provider.

Added by Admin Jonathan on Saturday Friday 25 July 2025 at 13h30EDT

The issue we were experiencing with the TRP has now been resolved and TRP has been running normally since around 09h30EDT/14h30BST on Saturday 26 July 2025

Last updated by Admin Martin on Saturday 26 July 2025 at 18h30BST

2025 - June

On Sunday 15 June, at about 04h00EDT/09h00BST it was noticed that TRP wasn't accessible. This was subsequently identified as an issue with the underlying server running the site.  The issue was resolved around 21h15EDT  Sunday  / 02h15BST Monday 16 June

Last updated by Admin Martin on Monday 16 June 2025 at 08h30BST

2023 - October

On Sunday 08 October, at about 20h00EDT it was noticed that TRP wasn't accessible. This was identified as an issue with the underlying server running the site.  At the present time (20h49EDT), we cannot give a resolution time but will update here when we know more or have it resolved.

Added by Admin Jonathan on Sunday 8 October 2023 at 20h49EDT

The issue we were experiencing with the underlying virtual server has been resolved overnight and TRP has been running normally since before 08h00BST/03h00EDT.

Last updated by Admin Martin on Monday 09 October 2023 at 08h30BST

2021 - October

On Monday 18 October, a report from a user at about 01h25BST indicated that TRP wasn't accessible.  This was subsequently identified as an issue with the underlying virtual server and we have enlisted the assistance of our hosting provider (11h30 BST).  At the present time (13h30BST), we do no know how long this make take to resolve.

Added by Admin Martin at 13h30BST on Monday 18 October 2021

The issue we were experiencing with the underlying virtual server has been resolved and TRP has been running normally since 16h00BST

Last updated by Admin Martin on 18 October 2021 at 17h25BST

2019 - January

In line with the notifications previously issued, the TRP site was placed in read only mode at about 19h00GMT / 14h00EST on Friday 4 January 2019 in anticipation of upgrading the underlying operating system and tiki software. The upgrade went more smoothly than we had dared to hope and the system came out of read only mode around 20h00GMT/15h00EST on Saturday 5 January 2019.

Last updated by Admin Martin on Saturday 5 January 2019

2017 - December 2017 to March 2018

TRP suffered a major outage in December 2017, which necessitated significant changes to the underlying platform and an upgrade to the wiki software used by TRP. See separate page "Service Disruption - Dec 2017 - Mar 2018" for fuller details of this incident.

2017 - November

On Tuesday 28 November 2017, a report from a user at about 14h35EST/19h35GMT indicated that TRP was not accessible.  On attempting to access TheReevesProject.org a blank screen is returned. BR has been advised.

Last Updated by Admin Martin on Wednesday 29 November 2017 at 09h30GMT/04h30EST

BR advised that the issue had been referred to the hosting provider and subsequently resolved. Normal service was resumed on Thursday 30 November by 10h50GMT/05h50EST.

Last updated by Admin Martin on Thursday 30 November at 19h30GMT/14h30EST

2017 - April

On Thursday 27 April 2017, a report from a user at about 09h50EDT/14h50BST indicated that TRP was not accessible.  On attempting to access TheReevesProject.org an "Internal Server Error" message is received. BR has be advised.

Updated by Admin Martin on Thursday 27 April 2017 at 16h45BST/11h45EDT

BR advises that the problem has been referred to the hosting provider for investigation/resolution.

Updated by Admin Martin on Friday 28 April 2017 at 17h10BST/12h10EDT

The problem has been resolved by the hosting provider and normal service resumed on Friday 28 April 2017 by 18h00BST/13h00EDT

Last Updated by Admin Martin on Friday 28 April 2017 at 18h35BST/13h35EDT

2017 - January

On Wednesday 25 January, a report from users at about 3h15EST/08h15GMT indicated  that TRP was not accessible.  On attempting to access TheReevesProject.org an "Internal Server Error" message is received.

Updated by Admin Martin on Monday 25 January 2017 at 08h30GMT/03h30EST

The system was working normally again by 10h40GMT/05h40EST.

Updated by Admin Martin on Monday 25 January 2017 at 12h05GMT/07h05EST

2014 - April

On Sunday 6 April 2014, report from users at about 15h20EDT/19h20GMT that TRP was not accessible.  At 22h43EDT/02h43GMT Barry confirms he is unable to access TRP and identifies the issue as being a DNS problem at the hosting provider, for which an incident ticket was opened.

System logs indicate users regained access from 23h27EDT on 6 April (03h27GMT on 7 April).

This event was not reflected on this site at the time and is recorded for completeness only.

Updated by Admin Martin on Monday 07 April at 07h40BST/06h40GMT/02h40EDT

2013 - October

Some users are reporting they are unable to access TRP, receiving either DNS error messages or 404 Page Not Found messages.

Updated by Admin Martin on Monday 28 October at 17h50GMT/12h50EST

Our systems admin, Barry, has confirmed that the TRP server is running normally, although it was crawled by an unknown bot yesterday (28 Oct 2013), which generated a huge amount of network traffic (well huge for TRP anyway).

However, it remains the case that for some users, the web is unable to resolve our domain name TheReevesProject.org to an IP Address, rendering the site inaccessible for those users.  Investigation continues...

Updated by Admin Martin on Tuesday 29 October at 12h00GMT/07h00EST

Following changes to DNS entries, which globally propagated overnight (UK time) 29/30 October, normal service has been resumed. After a few quick spot checks, the status reflected here was updated at 06h50GMT

Updated by Admin Martin on Wednesday 30 October at 06h50GMT/01h50EST

2013 - January

TRP suffered a failure late on Friday 25 January 2013 (EST).  Barry Reeves was working with his hosting provider to get the service restored as soon as possible.

The initial error seen was "Tiki is not properly set up". We were first alerted to this around 01h30GMT on Saturday 26 Jan /20h30EST on Friday 25 Jan.

Sometimes the error message simply reads "Internal Server Error", as seen at 18h10GMT/13h10EST on Sunday 27 January.

Updated by Admin Martin on Monday 28 January at 10h10GMT/05h10EST

Normal service resumed around 11h00GMT on Tuesday 29 January 2013. After a few quick spot checks, the status reflected here was updated  at 12h45GMT.

Updated by Admin Martin on Tuesday 29 January at 12h50GMT/07h50EST