Skip to main content

This is for internal use by the PaaS team. Public-facing documentation is located at

Support manual

What are we supporting

We are supporting the GOV.UK PaaS platform; we’re not providing user support for users of the apps hosted on it. However, in some cases service teams can’t self diagnose or fix problems (yet) so we need to be flexible about what we support.

We’re supporting live services, teams who are using PaaS for prototyping and individuals within teams who are trying it out.

Support hours

  • In hours: Monday to Friday 9am to 5pm, excluding bank holidays
  • Out of hours: no longer offered

Service Targets

  • First Response: Within 2 working days

Triaging issues

An issue could be something which is raised through our monitoring, alerting, ZenDesk or slack.

Triaging an issue is higher priority than other work. Once the issue has been triaged, it will be categorised (P1, P2 etc) and prioritised.

The following questions should be answered when triaging/prioritising:

  • What’s the urgency and why?
  • What’s the impact to our users, systems and reputation?
  • What’s the extent of the issue, how many systems and users are affected?
  • Is it a known issue - is there a workaround?
  • If there is uncertainty about which classification an issue should be given, the Tech Lead will be responsible for making a final call.
  • If the Tech Lead is not available, you should use the triage questions to make a decision based on the information you have at the time.

Severity Levels

We classify issues by their impact to users (tenants and their users, and the PaaS team) and react accordingly. This allows us to set expectations about how we will work, and what other teams should expect.

For most types of issue, our priority is to ensure high availability of the service.

An incident is any issue which causes significant problems for many platform users. This will include all P1 issues, and some P2 issues.

The exceptions to this are for some categories of security breach or vulnerability, and for some incidents where there is a risk of data corruption.

(Note this table is copied from overview doc - keep in sync. More detail may be needed later)

Classification AKA Example In hours Out of hours
P1 Critical Incident
  • Apps no longer being served due to an issue with our platform
  • serious security breach on the platform
  • You are unable to push an emergency fix to an app due to the PaaS API not being available
  • your live production app has a P1 issue which cannot be resolved without us
Start work & respond: 20 min

Update time: 1 hr
P2 Major Incident
  • Can’t update/push apps due to platform issue
  • Upstream vulnerabilities
  • elevated error rates
  • Complete component failure
  • substantial degradation of service
Start work & respond: 30 min

Update time: 2 hr
P3 Significant Users (tenants or end users) experiencing intermittent or degraded service due to platform issue. Start work & respond: 2 hr

Update time: 4 hr n/a
P4 Minor Component failure that is not immediately service impacting Respond: 1 business day

Update time: 2 business days

Support tickets

You can access our support ticketing tool ZenDesk here

If you don’t have an account ask the PaaS delivery manager to add you. You can adjust your notifications yourself.

Tips and good practice

  • Try to keep a descriptive name in the ZenDesk tickets. If the user added a not very descriptive name (e.g failure pushing app), change it to something that uniquely identifies the story (e.g failure pushing app: invalid mode 0444). Always notify the tenant about this change and why it is done.
  • Try to close the tickets if there is no action required from us.
  • If we are waiting for a ticket in the backlog, add note in the ticket saying that we need to inform the user once this is done and accepted.
  • Always notify the user that we are closing the ticket, why we are closing it and why the issue is resolved or it does not require more work from us.
  • Let the user know that they can always reopen the ticket if required.

Incident Process

This is now in its own section.