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

09.12.22

docs.landlordsguild.com Issues logging in to Tenancy Builder

If you have a space in your username, you will not be able to login into the Tenancy Builder (but you can log in to all other parts of the website). A fix is being worked on, but you can gain access by going to your profile page (you will be able to log in to that part) and remove any spaces from your username. Save the change and try logging into Tenancy Builder. That will work. We apologise for the trouble.

Referencing Service Referencing not working properly

We are aware that referencing isn't going through currently, and we apologise for the trouble. There is an issue with the third-party credit bureau authorising requests, and we have reported the problem and awaiting a response.

  • As a further update, the credit bureau has restored API access, and the referencing functions normally. We apologise for the trouble.

  • The third-party still has not fixed API access, but we will manually put requests through. Complete the form as usual, and we will do the report, which will be emailed to you. Reports may take a little longer than expected and won't appear in the Builder section. We apologise for any trouble.

  • We are still waiting for the bureau to resolve the issue.

    • 08.12.22

    docs.landlordsguild.com Tenancy Builder showing 500 error

    We are aware of an issue affecting a small number of customers who see a 500 error when trying to access Tenancy Builder. We apologise for the trouble, and we are investigating.

  • We found the issue and deployed a fix. In the meantime, if you see a 500 error, please log in using your username instead of your email, which should work whilst the fix is populated across the internet.

  • We have deployed a fix, although some customers still see the same. We are waiting for the fix to populate across the internet.

    • 07.12.22

    No incidents reported

    06.12.22

    No incidents reported

    05.12.22

    No incidents reported

    04.12.22

    No incidents reported

    03.12.22

    No incidents reported