DEMOThis is a demo with sample data

Watch my own site
All sites

site

Bookings

Bolt

https://bookings.bolt.host/

Last check · failed: Server not responding (502) · Every minute while it's down

Status

Down

Down for , since

Uptime · 30d

99.96%

1 incident, 8 min

Avg response · 24h

482 ms

Successful checks only

Downtime · 30d

8 min

Confirmed outages

ssl certificate

SSL valid · 61 days left

Runs out on , issued by Let's Encrypt.

domain

Domain managed by bolt.host

Nothing to renew on your side.

Last 24 hours

99.44%

1 incident, 8 min

uptime · 7d

99.92%

1 incident, 8 min

uptime · 30d

99.96%

1 incident, 8 min

uptime · 90d

99.96%

1 incident, 8 min

Watching since . Uptime counts confirmed outages (two failed checks in a row) and leaves out time when checks were paused.

How fast it opens

Average time to open your site, per hour.

Average
482 ms
Fastest
264 ms
Slowest
1.40 s

outage going on now ·

What visitors of Bookings saw

502Bad Gateway
screenshot taken when it went down · sample

what happened

The server behind it isn't responding properly. It may be overloaded, paused or restarting.

explained by AI

Likely cause: The server behind the app isn't answering, so the host shows "502 Bad Gateway".

Confidence: medium

Fix it with your AI builder

The alert comes with a prompt like this, ready to paste:

My Bolt app at bookings.bolt.host shows "502 Bad Gateway". First check in Bolt that the app is deployed and running. If it is, look at the server logs from the last few minutes for a crash on start-up and fix only that. Don't rewrite code that works.

AI explanations can be wrong. Look over the fix before you publish it.

Past incidents

whendown forwhat happenedstatus
8 min so farServer not responding (502)Ongoing