Getblock logo

Is Getblock Down?

SaaSLive status, outages, and incident history

No. Getblock is up right now.

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

OperationalChecked 3m agoLive · every 60s

Know the moment Getblock breaks

Getblock 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.

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

Status report

Getblock Status Summary

As of 13:26 UTC on 9 November 2026, Getblock is operational. PulsAPI checked Getblock's official status page and found 12 of 12 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Getblock, counting degraded performance as up.

Cite as: PulsAPI, “Getblock status”, checked 9 November 2026, 13:26 UTC. https://www.pulsapi.com/services/getblock

Getblock Component Status

The main Getblock systems on this page. All 12 are operational right now.

12operational
Arbitrum Mainnet Shared Archive
Operational
Arbitrum Mainnet Shared Full
Operational
Base Mainnet Shared Archive
Operational

9 more components tracked

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

Also tracking Base Mainnet Shared Full, BSC Mainnet Shared Archive, BSC Mainnet Shared Full, Ethereum Mainnet Shared Archive, Ethereum Mainnet Shared Full, Polygon Mainnet Shared Archive, Polygon Mainnet Shared Full, Solana Mainnet Shared Full, Sui Mainnet Shared Full.

See all of them free

Component statuses may change independently during partial outages.

Recent Getblock Outages & Incidents

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

No recent incidents reported by the vendor.

Getblock Uptime History

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

Uptime history91 days observed
Aug 1199.80% average · 5 days with incidentsNov 9

Going further back: Getblock uptime by month and every recorded Getblock outage.

Live Getblock Outage Reports

Problems reported by engineers using Getblock. 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 Getblock problems reported yet.

Something wrong with Getblock on your end?

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

About Getblock

Getblock publishes a public status page at status.getblock.io covering 3 components, including eu-central-1 Shared, us-east-1 Shared and ap-southeast-1 Shared. PulsAPI tracks Getblock outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Getblock uptime at 100.00%. Response times, incident history, and SLA tracking for Getblock are available on the PulsAPI dashboard.

Getblock Status FAQ

Is Getblock down right now?

The verdict at the top of this page comes from the latest poll of the official Getblock 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 Getblock 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 Getblock recovers.

How do I check Getblock uptime history?

PulsAPI tracks Getblock uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Getblock changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Getblock outages?

PulsAPI reads the official Getblock 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 Getblock components?

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

Can I get alerts when Getblock goes down?

Yes. Create a free account and subscribe to Getblock: 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 Getblock 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 Getblock problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Getblock?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Getblock 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 Getblock with the rest of your stack

2660+ 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