> For the complete documentation index, see [llms.txt](https://docs.pullbay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pullbay.com/documentation/platform-best-practices/service-health.md).

# Service Health

## Service Health

Pullbay continuously monitors all services and endpoints. This page explains how to check status and what the indicators mean.

***

### Where to Check Status

#### Dashboard

Your Pullbay dashboard shows the current status of all endpoints you use. The overview page displays:

* Overall platform status
* Status of each service
* Recent incidents (if any)

***

#### Status Page

A public status page shows current and historical uptime for all services.

Bookmark it to check during outages.

***

### Status Indicators

Each service and endpoint displays one of the following states:

| Status         | Icon | Meaning                                             |
| -------------- | ---- | --------------------------------------------------- |
| Operational    | 🟢   | Working normally                                    |
| Degraded       | 🟡   | Working but with reduced performance or reliability |
| Partial outage | 🟠   | Some endpoints or regions affected                  |
| Outage         | 🔴   | Service unavailable                                 |

***

### What Each Status Means

#### Operational

Everything is working as expected.\
Request success rates are normal and response times are within expected ranges.

***

#### Degraded

The service is working but you may experience:

* Slower response times
* Occasional timeouts
* Lower success rates than normal

Requests may still succeed, but with higher latency.\
Consider adding extra timeout buffer in your integration.

***

#### Partial Outage

Some parts of the service are affected:

* Specific endpoints might be unavailable while others continue working
* Certain regions may be impacted
* Specific data sources may be temporarily unavailable

Check the incident details to understand which parts are affected.

***

#### Outage

The service is unavailable. Requests will fail.

During outages:

* Implement fallback logic if available
* Queue requests for retry after recovery
* Monitor the status page for updates

***

### Incident Communication

When incidents occur, Pullbay communicates through:

* Status page updates (immediate)
* Dashboard notifications
* Email notifications (for significant incidents)

Incident reports typically include:

* What’s affected
* When it started
* Current status
* Expected resolution time (when known)
* Root cause (in post-incident reports)

***

### Monitoring Your Usage

Beyond service health, you should monitor your own usage:

* **Success rate** — What percentage of your requests succeed
* **Response times** — Whether responses are getting slower
* **Error patterns** — Whether certain endpoints are failing more frequently

Your dashboard provides these metrics broken down by endpoint and time period.

***

### Recommendations

To build resilient integrations:

* Monitor both platform status and your own usage metrics
* Adjust timeouts when performance degrades
* Implement retry logic for transient failures
* Use fallback strategies where possible
* Track error patterns to detect issues early


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pullbay.com/documentation/platform-best-practices/service-health.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.