CheckUpstream does not yet run an independent probe against Infura, so no availability figure is published for it — only Infura's own disclosure record below. 30 incidents were recorded in the past 12 months; the most recent resolved 46 days ago after 35 days. Status signals are polled from Infura's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Infura yet, so we publish no availability figure for it. What follows is Infura's own disclosure record, which is a different thing.
Infura posted no incidents in this window. That is either a clean run or a communication policy — from outside, the two look identical.
Fewer incidents in the last 30 days than 44% of 232 tracked services.
Share of each window with no impact declared by Infura
7d
100.000%
30d
100.000%
90d
100.000%
180d
94.163%
1y
97.122%
Does Infura actually matter to you?
A Infura outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Jul 22, 07:22 UTC · resolved in 1h 32m · Resolved
Jul 16, 08:12 UTC · resolved in 34d 11h · Resolved
Jul 14, 03:34 UTC · resolved in 7h 45m · Resolved
2signals across 1 source
active_probe 2
All of these are CheckUpstream's own probes. Nobody else has reported Infura in this window, so nothing here is corroboration.
Live Infura status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/infura)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Infura is currently Operational. CheckUpstream tracks Infura in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Infura down" view? See the Infura Live status page.
Jul 11, 08:16 UTC · resolved in 1h 38m · Resolved
Jun 14, 05:11 UTC · resolved in 21h 18m · Resolved
Jun 13, 18:18 UTC · resolved in 5h 13m · Resolved
Jun 10, 09:54 UTC · resolved in 4d 11h · Resolved
Jun 2, 11:20 UTC · resolved in 4h 10m · Resolved
Jun 1, 18:38 UTC · resolved in 5h 46m · Resolved
May 27, 18:42 UTC · resolved in 2h 38m · Resolved
May 23, 18:19 UTC · resolved in 8h 20m · Resolved
Apr 29, 15:39 UTC · resolved in 3h 51m · Resolved
Apr 28, 12:59 UTC · resolved in 7h 30m · Resolved
Apr 28, 11:36 UTC · resolved in 3h 34m · Resolved
Infura's last resolved incident started 46 days ago and lasted 34d 11h (a partial outage).
We don't publish one. CheckUpstream runs no independent probe against Infura yet, and the only other figure available would be derived from Infura's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Infura to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Infura's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.