PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Bolt.new is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Bolt.new. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Bolt.new issues today?

As of Oct 13, 2026 23:36 UTC, 0 users had reported issues with Bolt.new in the previous 24 hours.

How can I report a Bolt.new outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Other

Is Bolt.new down right now?

NormalOfficial status last polled Oct 13, 2026 22:25 UTCbolt.new Official status page

Are you on the Bolt.new team and see something inaccurate? Report it to us. We respond within one business day.

Is Bolt.new down right now?

No. Bolt.new has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 13, 2026 23:36 UTC

Normal

Bolt.new is operating normally

As of Oct 13, 2026 23:36 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Oct 6, 2026 10:30 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Bolt.new.

Incident days

No recorded incident

2h 23m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Bolt.new. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

2h 23m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Bolt.new: vendor-reported minor incident on October 6 (tracked 1h 22m)

Oct 6, 09:07 AM → Oct 6, 10:30 AM · 1h 22m · medium

Bolt.new reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 1 hour and 22 minutes, closing it on 2026-10-06T10:30:42.598Z.

Duration

1h 22m

tracked by PulseWatch

Impact

PulseWatch recorded zero user reports for this incident and therefore cannot describe what users experienced. The incident is known from Bolt.new's status page.

Incident timeline

Oct 6, 09:07 AM
The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it
Oct 6, 09:07 AM
Status updated: possible issue
Oct 6, 10:30 AM
PulseWatch closed the incident

Official updates

Oct 6, 09:07 AM
Bolt.new reported the incident on its status page.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.67%

90-day uptime

89.2%

Calculated from Bolt.new's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

Bolt.new: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/6/2026, 9:07:50 AM · 1h 22m

09:07 AM10:30 AM

Detection10/6/2026, 9:07:50 AM · 7d ago

Detected — medium severity

ResolvedMedium

Bolt.new: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/14/2026, 8:50:34 AM · 1h 0m

08:50 AM09:50 AM

Detection9/14/2026, 8:50:34 AM · 29d ago

Detected — medium severity

Bolt.new: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

ResolvedMedium