All systems are operational

Past Incidents

8th June 2020

No incidents reported

7th June 2020

No incidents reported

6th June 2020

No incidents reported

5th June 2020

No incidents reported

4th June 2020

No incidents reported

3rd June 2020

No incidents reported

2nd June 2020

No incidents reported

1st June 2020

No incidents reported

31st May 2020

No incidents reported

30th May 2020

No incidents reported

29th May 2020

No incidents reported

28th May 2020

No incidents reported

27th May 2020

No incidents reported

26th May 2020

No incidents reported

25th May 2020

No incidents reported

24th May 2020

No incidents reported

23rd May 2020

No incidents reported

22nd May 2020

No incidents reported

21st May 2020

No incidents reported

20th May 2020

No incidents reported

19th May 2020

Compute Nodes dal116 unavailable

We are aware of an issue with node dal116 being unavailable, We are looking into the issue.

18th May 2020

No incidents reported

17th May 2020

ghm91 high disk io, scheduled 2 months ago

We've identified lag issues caused by high disk io wait time.

We will be replacing all drives (one at a time) on this machine and resyncing the RAID arrays to ensure data redundancy.

Compute Nodes ghm91

We've identified continuing performance issues with Grantham #91, we will be migrating all users off this node immediately.

16th May 2020

Switch replacement, scheduled 2 months ago

We will be upgrading(replacing) a core network switch in Nottingham which some of our peering connections pass through, this may cause loss of connection for some clients in Grantham but services will remain accessible for the majority.

15th May 2020

No incidents reported

14th May 2020

No incidents reported

13th May 2020

No incidents reported

12th May 2020

lax122 node restart., scheduled 2 months ago

We are aware of an issue with node lax122 and will need to restart the node to resolve the issue. We expect downtime to be less than 15 minutes.

syd50 node restart., scheduled 2 months ago

We are aware of an issue with node syd50 and will need to restart the node to resolve the issue. We expect downtime to be less than 15 minutes.