Is productboard Pusher Channels WebSocket client API down?
Current productboard Pusher Channels WebSocket client API status is UP

If productboard Pusher Channels WebSocket client API is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when productboard Pusher Channels WebSocket client API is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

productboard Pusher Channels WebSocket client API posts separate notifications for planned maintenance work. StatusGator will notify subscribers when productboard Pusher Channels WebSocket client API enters a pre-planned maintenance window, keeping you up to date.

Since productboard Pusher Channels WebSocket client API publishes a feed of proactive maintenance events on their status page, StatusGator will collect information about these events. Maintenance events for all your services can be viewed within StatusGator as a unified feed.

When productboard Pusher Channels WebSocket client API posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When productboard Pusher Channels WebSocket client API has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because productboard Pusher Channels WebSocket client API has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.