Overview

The TripBuilder Status Page, also known as the "Control Room", provides real-time updates on the status of all TripBuilder services, and is used to provide information on detected incidents, ongoing actions and historical data on past incidents.

In addition, we will post scheduled outages from external suppliers (if notified in advance) on the status page. This will keep you informed of any potential service disruptions, whether they are directly or indirectly related to TripBuilder.

How to access the Control Room

The TripBuilder Control Room is accessible without a login, so you do not need a username or password to view the information.

Information Available in the Control Room

The Control Room provides an overview of TripBuilder's service uptime over the past 90 days. A bar represents each day: green indicates 100% uptime, while yellow indicates a partial outage or service disruption.

You can view historical uptime information by clicking on View historical uptime. This allows the sorting of historical data in two ways:

Incidents

Navigate to the Incidents tab to view a comprehensive list of historical incidents organised by month.

Click on any incident to view the full incident report.

In the detailed view of each incident, you can access updates on the actions being taken or completed.

Uptime

Service downtime can be filtered by day and month with the following colour code:

• Grey: No data has been loaded for that specific day
• Green: No downtime recorded for the specific day
• Yellow: A partial outage was recorded for that specific day. Click the text under the Related section to open the complete incident report.

Scheduled Maintenance

This section lists all planned and communicated outages from Nezasa and third-party suppliers. It is designed to inform you proactively about possible service downtimes.

Service disruptions from third-party suppliers that are not proactively communicated to Nezasa will be displayed here only once we detect them. In such cases, they will be categorised as incidents rather than Scheduled Maintenance.