[Dependency Check] Supabase
IdentifiedPossible issues
Upstream Provider has reported an outage
Started · 2026-08-14 02:35 UTC
2026-08-14 02:35 UTCIdentified
Upstream Provider has reported an outage
Possibly — Bolt.new may have issues
bolt.new may be experiencing issues such as errors or slow responses. The latest automated check was run 2026-08-14 17:18 UTC from primary location. This is not a confirmed global outage.
Possible issues
- Current status
- Possible issues
- Last check
- Checked every minute
- Last 24 hours
- 50.000%
Current issue started 1h 25m ago
Latest 2026-08-14 17:18 UTC · Primary location
2 incidents, 15h 39m down
- Official status
- Possible issues
- Our check
- Operational
- Active incident
- [Dependency Check] Supabase
- Last outage
- 2026-08-14
- Response time
- 352 ms
- User reports
- Normal
None today
Bolt.new live status
8 of 9 operational · 1 with issues
- SupabasePossible issues
- AnthropicOperational
- BedrockOperational
- bolt.newOperational
- CloudflareOperational
- GitHubOperational
- Name.com Registry ConnectionsOperational
- NPMOperational
- StackBlitzOperational
Current incident
Response time
Latest 353 ms
Loading response-time chart…
Uptime
Availability from independent checks, with recorded incidents and downtime in each window.
Today
50.000%
2 incidents, 15h 39m down
Last 7 days
50.000%
2 incidents, 15h 39m down
Last 30 days
50.000%
2 incidents, 15h 39m down
Last 365 days
50.000%
2 incidents, 15h 39m down
Latest Bolt.new incidents
Recorded outages with duration and start time.
Last recorded 2026-08-14 15:39 UTC
| Incident | Duration | Started |
|---|---|---|
[Dependency Check] Cloudflare Resolved | 54 min | 2026-08-14 15:39 UTC |
[Dependency Check] Supabase Identified | Ongoing | 2026-08-14 02:35 UTC |
How this status checker works
Who's Down Today monitors Bolt.new independently of the company that runs it. We send reachability checks from our primary location every minute and record response time, HTTP errors, and timeouts.
When Bolt.new publishes a public status page or incident feed, that official signal is treated as a strong input and is shown separately from our probe. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.
This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.
Frequently asked questions
Is Bolt.new down right now?
- Possibly — Bolt.new may have issues. Who's Down Today currently shows Bolt.new as possible issues. Check the live status, recent incidents, and response-time chart on this page. If the site works for you, the issue may be regional or limited to some features.
Is Bolt.new down for everyone or just me?
- A confirmed issue on this page means our sources detected a problem, but that does not always mean every user is affected. Some incidents are regional, affect only some features, or appear as slow loading instead of a full outage.
What should I do if bolt.new is up but I still cannot access it?
- Try opening bolt.new from another browser, device, or network (for example a mobile hotspot). You can also disable a VPN, flush local DNS, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed Bolt.new outage.
How does Who's Down Today check if Bolt.new is down?
- We combine independent HTTP reachability checks with public status information where it exists. When Bolt.new publishes a public status page or incident feed, that official signal is treated as a strong input. A single failed probe is treated as a possible transient or regional failure, not an automatic global outage. Bot protection, geo restrictions, and HTTP 403 responses are not automatically classified as downtime.
What does a Bolt.new outage mean?
- An outage on this page means recorded incidents or failed checks indicated that Bolt.new was not responding normally. That does not always mean every user was affected. Some outages are regional, some affect only certain features, and some appear as errors or slow responses instead of a full failure.
Can this page tell me the root cause of a Bolt.new outage?
- Not exactly. We can show when an issue started, how long it lasted, the public incident title, and symptoms such as timeouts or slow response times. We do not have access to Bolt.new's internal systems, so we cannot identify a private root cause such as a failed deploy or database incident unless the provider publishes it.
How do I report an issue with Bolt.new?
- Use the report form on this page if Bolt.new looks down for you. Reports are anonymous, rate-limited, and used only as supporting evidence alongside official sources and independent checks.