down
Is Pinax down?
Check Pinax availability, incident history, downtime reports, and website performance.
https://pinax.network/en ↗Mapped components are operational in the latest status update; individual experiences can vary.
Service disruption activity for Pinax
Last 24 hoursObserved disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.
Latest observation: 2026-11-11 03:58:44 UTC. Refreshes automatically while this page is visible.
No user-submitted outage reports in the last 24 hours.
Pinax outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Pinax website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-11-11 03:38:05 UTC.
Public endpoint monitoring — this lightweight resource measures website connectivity and response time. It does not test the application, login, or API. Check official component status below for product availability.
Checked address: https://pinax.network/en
DNS lookup: 8 ms · TCP connection: 1 ms · TLS handshake: 5 ms.
100%
Successful website checks (24h)
22 successful / 22 measurable checks
119 ms
Median response time
300 ms
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
Pinax official status · fetched 2026-11-11 03:58:44 UTC
25 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| Cloud Backend - Pinax Authenticator | operational |
| API - REST API | operational |
| API - MCP | operational |
| Arbitrum One Mainnet | operational |
| Avalanche C-Chain | operational |
| Base Chain | operational |
| BNB Smart Chain Mainnet | operational |
| Ethereum Mainnet | operational |
| HyperLiquid - Core | operational |
| HyperEVM Mainnet | operational |
| OP Mainnet | operational |
| Polygon Mainnet | operational |
| Solana Mainnet | operational |
| Unichain Mainnet | operational |
| Ethereum Consensus Layer | operational |
| Ethereum Hoodi Consensus Layer | operational |
| Ethereum Sepolia Consensus Layer | operational |
| Gnosis Consensus Layer | operational |
| Ethereum Consensus Layer | operational |
| Ethereum Hoodi Consensus Layer | operational |
| Ethereum Sepolia Consensus Layer | operational |
| Gnosis Consensus Layer | operational |
| Solana Mainnet | operational |
| Vaulta Mainnet | operational |
| Vaulta Jungle4 Testnet | operational |
Official incident timeline
Ingestion delays on Base Chain · resolved · 2026-11-05T18:49:29Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
The issue is now fixed.
- · investigating
We are now Investigating the incident
RPC Degraded Performance on HyperEVM Mainnet · resolved · 2026-11-05T16:12:52Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
The issue is now fixed.
- · investigating
We are investigating reports of performance issues for HyperEVM Mainnet in the RPC service.
- · investigating
We are investigating reports of performance issues for HyperEVM Mainnet in the RPC service.
RPC Degraded Performance on zkSync Mainnet · resolved · 2026-11-04T14:03:20Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
Things are are working normally for zkSync Mainnet in the RPC service and we closed this issue. If you are noticing any unusual issues please report the issue via normal support channels. !
- · investigating
We are investigating reports of performance issues for zkSync Mainnet in the RPC service.
RPC Degraded Performance on zkSync Mainnet · resolved · 2026-11-03T14:56:06Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
Things are are working normally for zkSync Mainnet in the RPC service and we closed this issue. If you are noticing any unusual issues please report the issue via normal support channels. !
- · investigating
We are investigating reports of performance issues for zkSync Mainnet in the RPC service.
Issue with token-api · resolved · 2026-10-30T03:01:18Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
The issue is now fixed.
- · identified
we are working on the solution
- · investigating
We are investigating the problem.
- · monitoring
A fix was applied for service API - Live Sink on network BNB Smart Chain Mainnet. We are now monitoring stability.
Ingestion delays on Hyperliquid - Core · resolved · 2026-10-30T00:36:42Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
The issue is now fixed.
- · investigating
We are now Investigating the incident
Firehose Degraded Performance on Blast Mainnet · resolved · 2026-10-29T20:18:21Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
Issue resolved for [Firehose](https://app.incident.io/pinaxworkspace/catalog/01JZB2AEBHSH43X1YNCFK1AS8Q/01K0W7KA6RV83N2PB70PH3JC7X), [RPC](https://app.incident.io/pinaxworkspace/catalog/01JZB2AEBHSH43X1YNCFK1AS8Q/01KQA7Q5Q2HVTPSDEKZQ6SG9B2) on [blast](https://app.incident.io/pinaxworkspace/catalog/01K1XSAS64XRJ1Q7H2TJ9DC930/01K22VCMYP3H13DY7TG51BM75B).
- · investigating
Blast is experiencing an upstream network disruption, delaying new block data across our Blast RPC, Firehose, and Substreams services. We are monitoring the network and will provide another update when progress resumes.
- · investigating
We are having an issue with [Firehose](https://app.incident.io/pinaxworkspace/catalog/01JZB2AEBHSH43X1YNCFK1AS8Q/01K0W7KA6RV83N2PB70PH3JC7X) on [blast](https://app.incident.io/pinaxworkspace/catalog/01K1XSAS64XRJ1Q7H2TJ9DC930/01K22VCMYP3H13DY7TG51BM75B). Investigating it now.
Ingestion delays on BNB Smart Chain Mainnet · resolved · 2026-10-29T17:00:26Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
The issue is now fixed.
- · resolved
The issue is now fixed.
- · identified
Ingestion is a few minutes behind.
- · resolved
The issue is now fixed.
- · investigating
We are now Investigating the incident
Recovery tracker
No recent recovery can be established from available evidence.
0 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
More successful checks are needed to establish a response-time baseline.
Recent median: unknown · Earlier median: 127 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Query “pinax” · observed 2026-11-11 03:02:05 UTC · 0 newly observed problem phrases.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Pinax.
No active incidents recorded.
- Changes to Cloudflare Workers are not producing Event Subscription events · investigating
- Fedramp Customers have Delayed Purges · identified
About Pinax status on Iszdown
Check Pinax availability, incident history, downtime reports, and website performance.
This page combines the available Pinax report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
25 product-matched official components are listed above. Latest public website measurement: 2026-11-11T03:38:05.000Z.
Visit the official Pinax website · Official provider status · How it works
What to check when Pinax is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Pinax will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
Pinax is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Pinax outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Ingestion delays on Base Chain | 13 min | resolved | |
| RPC Degraded Performance on HyperEVM Mainnet | 10 min | resolved | |
| RPC Degraded Performance on zkSync Mainnet | 572 min | resolved | |
| RPC Degraded Performance on zkSync Mainnet | 173 min | resolved | |
| Ingestion delays on Hyperliquid - Core | 25 min | resolved | |
| Firehose Degraded Performance on Blast Mainnet | 211 min | resolved | |
| Firehose Degraded Performance on HyperEVM Mainnet | 26 min | resolved | |
| Ingestion delays on Hyperliquid - Core | 175 min | resolved |
Frequently asked questions about Pinax
Is Pinax down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-11T04:08:38.000Z.
How many Pinax outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-10T04:00:00.000Z to 2026-11-11T04:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Pinax show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Pinax feature.
When was Pinax status last updated?
The latest status observation was 2026-11-11T03:58:44.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has Pinax had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Pinax or report a problem?
Use “Watch this service” to save Pinax in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Pinax
Check a related product separately; its status can differ from Pinax.