PX logo

Is PX Down?

MarketingLive status, outages, and incident history

No. PX is up right now.

Every monitored PX system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment PX breaks

PX is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official PX status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

PX Status Summary

As of 13:26 UTC on 14 November 2026, PX is operational. PulsAPI checked PX's official status page and found 7 of 7 components operational, with no active incidents. The latest incident, "Leadflow & Callflow Outage", was on Sep 2, 2026 and lasted 1h 6m.

Cite as: PulsAPI, “PX status”, checked 14 November 2026, 13:26 UTC. https://www.pulsapi.com/services/px

PX Component Status

The main PX systems on this page. All 7 are operational right now.

7operational
Branded Flows
Operational
Call&Lead
Operational
Lead Score API
Operational

4 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking PX Calls, PX Open API, PX Ping Post and Direct Post, PX UI and Reporting.

See all of them free

Component statuses may change independently during partial outages.

Recent PX Outages & Incidents

Incident history from the official PX status page, including resolution updates.

Leadflow & Callflow OutageResolved Sep 2, 2026 · 1h 6mResolved

This incident has been resolved. --- [2026-09-02T13:52:10.638-04:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-02T13:35:26.762-04:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-09-02T13:05:10.036-04:00] (investigating) We’re partly experiencing a service outage. Our team is currently working to resolve the problem. We apologize for any inconvenience and will post another update as soon as we know more. Please keep an eye on this status page. You can always contact support@px.com for any requests.

IncidentResolved Sep 1, 2026 · 58 minResolved

This incident has been resolved. --- [2026-09-01T09:40:40.440-04:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-01T09:04:59.731-04:00] (investigating) We’re partly experiencing a service outage. Our team is currently working to resolve the problem. We apologize for any inconvenience and will post another update as soon as we know more. Please keep an eye on this status page. You can always contact support@px.com for any requests.

IncidentResolved Aug 17, 2026 · 41 minResolved

We’ve fully resolved the issue that was impacting Lead and call flows on PX. All services are now functioning normally, and system performance is stable. Our teams will continue to monitor closely, but no further impact is expected. A detailed incident report will follow to share our findings and the steps we’re taking to prevent similar issues in the future. If you’re still encountering any issues, please don’t hesitate to contact us at support@px.com. Thank you for your trust and continued partnership. – The PX Team --- [2026-08-17T08:41:44.116-04:00] (investigating) We’re currently investigating an issue on PX that is at least partially impacting our users and partners’ ability to post leads into PX and leads processing by PX platform. our initial investigation shows that ping post leads are not delivered to buyers direct post leads are not delivered to buyers calls are not delivered to buyers leads posted by publishers are not arriving calls posted by publishers are not arriving Our engineering team is actively working to identify the root cause and restore full functionality as quickly as possible. We understand how critical lead flow and performance visibility are to your business, and we’re treating this with the highest urgency. We’ll provide updates every 30 minutes or sooner if we have meaningful progress to share. Thank you for your understanding and continued partnership. – The PX Team

PX Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a PX incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live PX Outage Reports

Problems reported by engineers using PX. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No PX problems reported yet.

Something wrong with PX on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About PX

Is PX down? Its official status page at status.px.com reports on 7 components, including Branded Flows, Call&Lead and Lead Score API. PulsAPI checks it every few minutes and can alert you when PX reports an incident.

PX Status FAQ

Is PX down right now?

The verdict at the top of this page comes from the latest poll of the official PX status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if PX is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until PX recovers.

How do I check PX uptime history?

PulsAPI tracks PX uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever PX changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect PX outages?

PulsAPI reads the official PX status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual PX components?

Yes. PulsAPI monitors 7 individual PX components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when PX goes down?

Yes. Create a free account and subscribe to PX: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with PX to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot PX problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor PX?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so PX plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track PX with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services