Start with the product you use
International Polymarket publishes a status page and public feeds. The US documentation links a separate US status service. These are different sources; a report for one does not establish the other’s condition.
This tool reads the public reports without account credentials. It does not submit a trade, inspect a wallet or measure uptime independently. The timestamp records when our server collected the snapshot, rather than claiming every component was tested at that moment.
A summary is not every component
The international summary feed omits component detail, so we read its separate component feed too. The US summary API includes component reports and notices. Product labels, group names and production or pre-production labels are retained so you can inspect the relevant system.
Do not apply a perpetuals component report to a prediction-contract API without checking its scope. Likewise, a pre-production issue does not establish a production outage. If component detail cannot be obtained, the tool says so rather than using the summary to fill in missing rows.
Maintenance and incidents have different states
A notice can be scheduled, in progress, monitoring or completed. Read the label and time together. A future maintenance window can coexist with an operational component report; it is not automatically a current outage.
For example, imagine a provider announces work for tomorrow while reporting normal service today. Treating that notice as an outage today would change its meaning. Conversely, a monitoring update still deserves inspection until the provider reports its current outcome.
If your order or account is failing
- Identify the exact product and the action that failed.
- Read the current component report and relevant notice.
- Save the message and observation time.
- Check the official app’s account-specific requirements separately.
- If unresolved, use official support with the exact action, time and error.
If an order response is uncertain, verify its actual state before retrying. A connection failure alone does not prove whether an order was accepted. Our Polymarket API guide explains the data and authentication boundaries; this page performs only public status reads.
Understand an unavailable result
A failed request can reflect the status source, our connection or another delivery problem. It is deliberately shown as unavailable rather than as a confirmed exchange outage. Partial-source warnings identify missing detail while preserving the other available report.
Refresh to request a recent snapshot. Old results disappear during a new request or after expiry. No historical uptime percentage is calculated here. For the other venue, use our Kalshi exchange status check, which reports different flags and scopes.