All systems are operational

About This Site

This page shows currently known incidents. You can also view the uptime of all websites.

You can report an incident by creating a helpdesk ticket.

Success events shown on the graph are taken from various sources but are mainly from Tenancy Builder after a successful build.

Past Incidents

20.06.22

docs.landlordsguild.com Tenancy agreements not displaying

We are aware of an issue where some customers can’t see their tenancy agreements in the list. We’re working on this now.

  • The issue has been fixed. We apologise for the inconvenience. There are some new features such as view and archive which have been accidentally pushed and not ready but they might work in part.

    • 19.06.22

    No incidents reported

    18.06.22

    No incidents reported

    17.06.22

    Section 8 Notice Section 8 not accepting pence in the rent amount field

    If you are generating a section 8 notice and the arrears have a pence amount (e.g. 1234.56), the field is not accepting pence. We apologise for the inconvenience. It's taken a little longer to fix than we expected, and we hope to complete it by the 18th of June AM.

  • The issue has now been fixed.

    • 16.06.22

    https://www.landlordsguild.com Some links not working

    We are aware of an issue where some links on the main website (mostly news and guidance articles) are not working and are trying to find the cause. We apologise for the trouble.

  • The issue has been fixed. Apologies for the trouble.

    • Section 21 Notice Section 21 and 8 notice creation issues

    We are aware of an issue where trying to generate a section 21 notice produces a server error. We are also mindful of the problem with section 8, where pence cannot be entered. A fix is being implemented, and we apologise for the trouble.

  • The creation and download issue has been fixed.

  • We have identified the issue, which also affects section 8 plus 13 notices. We have implemented a fix on our test server and checking everything is working correctly. We will push it to the live server tomorrow (17 June) when we are confident it is fully fixed. We apologise for the inconvenience.

    • 15.06.22

    No incidents reported

    14.06.22

    No incidents reported