Follow the recent outages and downtime for Pusher Channels WebSocket client API in the table below.
Start Time |
Type |
Length |
Message |
Details |
|||||
---|---|---|---|---|---|---|---|---|---|
April 04, 2024 20:52 UTC |
DOWN |
about 5 hours |
High Latency in US2 on Channels WebSocket Client API |
See more
|
|||||
April 04, 2024 20:27 UTC |
WARN |
25 minutes |
High Latency in US2 on Channels WebSocket Client API |
See more
|
|||||
April 04, 2024 19:17 UTC |
WARN |
35 minutes |
High Latency in US2 on Channels WebSocket Client API |
See more
|
|||||
December 05, 2023 17:37 UTC |
DOWN |
10 minutes |
Public EU cluster outage |
See more
|
|||||
December 01, 2023 20:32 UTC |
WARN |
about 1 hour |
US2 Customers may be experiencing latency issues with or unable to utilize the Channels WebSocket and REST API |
See more
|
|||||
2024-04-14 17:36:23 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-14 17:36:23 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-14 17:36:23 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-14 17:36:23 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-14 17:36:23 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more |
Sign Up for More Pusher Channels WebSocket client API History
StatusGator has about 9 years of Pusher Channels WebSocket client API status history.
Pusher Channels WebSocket client API status, last 24 hours:
Up: 24 hours
Warn: 0 minutes
Down: 0 minutes
Maintenance: 0 minutes
We've been monitoring Pusher Channels WebSocket client API outages since March 9, 2015.
Here's the history of service outages we've observed from the Pusher Channels WebSocket client API Status Page:
Pusher Channels WebSocket client API is a Development solution that StatusGator has been monitoring since March 2015. Over the past about 9 years, we have collected data on on more than 365 outages that affected Pusher Channels WebSocket client API users. When Pusher Channels WebSocket client API publishes downtime on their status page, they do so across 11 components using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.
More than 100 StatusGator users monitor Pusher Channels WebSocket client API to get notified when it's down, is under maintenance, or has an outage. This makes it one of the most popular development services monitored on our platform. We've sent more than 4,500 notifications to our users about Pusher Channels WebSocket client API incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
If 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 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.
Pusher Channels WebSocket client API posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Pusher Channels WebSocket client API enters a pre-planned maintenance window, keeping you up to date.
Since 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 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 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 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.
Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!
Are you experiencing issues with Pusher Channels WebSocket client API? Sign up to receive notifications when Pusher Channels WebSocket client API publishes outages.
Pusher Channels WebSocket client API Down or not working? Never be taken by surprise again.
StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,580 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.
Looking for recent downtime and outages of Pusher Channels WebSocket client API?
Sign up for StatusGator and see all historical information about Pusher Channels WebSocket client API outages and performance issues. Get free, instant notifications when Pusher Channels WebSocket client API goes down.