Skip to main content
Vendor reliability

Vendor record

Pusher

Vendor reports Operational

Checked

Front door check counts and Pusher’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We have no front door checks against Pusher in the last 30 days. That does not show whether it was reachable.

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Pusher product, region or your app worked.

How we count front door checks

Pusher says

Incident posts from Pusher’s status page, with its titles, impact levels and times. They say what Pusher chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

2

incidents Pusher posted, last 90 days

All vendors’ incidents

Most recent records · all dates

  • Elevated Errors on us2

    Not specified

    Started, per Pusher

    Closed in our record(3h 52m)

    Pusher’s post

  • Elevated errors on us2 cluster

    Not specified

    Started, per Pusher

    Closed in our record(1h 37m)

    Pusher’s post

  • Intermittent API errors in US2 cluster

    Minor

    Started, per Pusher

    Closed in our record(1h 13m)

    Pusher’s post

  • Cluster SA1: Delayed Channels webhook delivery on SA1 cluster

    Minor

    Started, per Pusher

    Closed in our record(19m)

    Pusher’s post

Your code, your dependencies

See which of your code paths call Pusher

Connect GitHub or GitLab to find where your public or private repository uses Pusher. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Pusher status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · PusherStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/pusher?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Pusher status badge"></iframe>

Frequently Asked Questions

Is Pusher currently down?

Pusher's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Pusher last have an outage?

The most recent closed incident record began 54 days ago and spans 3h 52m. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Pusher?

No. CheckUpstream does not run front door checks against Pusher. The incident history on this page is what Pusher reported, not a measure of how often it was available.

How do I monitor Pusher in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Pusher?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors