Story Protocol logo

Is Story Protocol Down?

SaaSLive status, outages, and incident history

No. Story Protocol is up right now.

Every monitored Story Protocol system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 19m agoLive · 60s while moving

Know the moment Story Protocol breaks

Story Protocol is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

How we know: the official Story Protocol status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Story Protocol Component Status

The main Story Protocol systems on this page. All 9 are operational right now.

9operational
Blockchain Explorer
Operational
Bootnode1
Operational
Bootnode2
Operational

6 more components tracked

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

Also tracking Official Website, Protocol Explorer, RPC, Staking Dashboard, Story API, story api availability -> Api Success Rate.

See all of them free

Component statuses may change independently during partial outages.

Recent Story Protocol Outages & Incidents

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

No recent incidents reported by the vendor.

Story Protocol Uptime History

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

Uptime history49 days observed
Aug 8100.00% averageSep 25

Live Story Protocol Outage Reports

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

Something wrong with Story Protocol on your end?

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

About Story Protocol

Is Story Protocol down? Story Protocol reports live availability for 4 components at status.story.foundation, among them Base, Mainnet and Aeneid Testnet. Track Story Protocol outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

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

Story Protocol Status FAQ

Is Story Protocol down right now?

The verdict at the top of this page comes from the latest poll of the official Story Protocol status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Story Protocol 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 Story Protocol recovers.

How do I check Story Protocol uptime history?

PulsAPI tracks Story Protocol 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 Story Protocol changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Story Protocol outages?

PulsAPI reads the official Story Protocol status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Story Protocol components?

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

Can I get alerts when Story Protocol goes down?

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

Is there a free way to monitor Story Protocol?

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

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