Is BidScript down?
Last checked 8m agoNo incidents right now.
BidScript is operational right now. Last checked 8m ago; the most recent incident resolved 76d ago.
Real-time BidScript status, recent outages, and incident history: pulled directly from BidScript's official status page at status.bidscript.co.uk every 5 minutes. Pingoru tracks 2 BidScript services and has captured 2 incidents in the last 90 days (98.89% uptime). Get email, Slack, Discord, or webhook alerts the moment BidScript reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- App
Timeline · 2 updates
- investigating · Aug 06, 2026, 08:53 AM UTC
Status: Investigating We're investigating an issue where BidBot's assistant tool actions (including connected app integrations) can fail to complete or require confirmation that isn't currently displaying. Some users may see a request "hang" with no response. We're actively working on identifying the fix. Affected components App (Degraded performance)
- resolved · Aug 06, 2026, 02:40 PM UTC
Status: Resolved BidBot conversations that needed your approval to run a connected tool stopped mid-response: no approval prompt appeared, and there was no error or way to continue. Every connected tool that asks before it acts was affected, on web and desktop. No data was lost or changed, the affected actions never ran, and nothing else in the app was impacted. Affected components App (Operational)
Latest: Status: Resolved BidBot conversations that needed your approval to run a connected tool stopped mid-response: no approval prompt appeared, and there was no error or way to continue…
-
- App
Timeline · 2 updates
- investigating · Jul 30, 2026, 09:11 AM UTC
Status: Investigating Between 08:49–08:54 UTC, requests to bid/tender analysis features experienced elevated response times, with some requests taking up to ~3 minutes to complete. Confirmed affected: evaluation criteria, qualification requirements, commercial terms, submission requirements, and related extraction endpoints although surface is likely wider, as these were only the endpoints observed in sampled traces during the window. All requests ultimately completed successfully and no data was lost or corrupted. The root cause was a temporary latency spike in an upstream AI processing service we depend on for document analysis. Response times returned to normal by ~09:02 UTC and have been stable since. We're monitoring for recurrence. Affected components App (Degraded performance)
- resolved · Jul 30, 2026, 09:21 AM UTC
Status: Resolved Resolved - Between 08:49 and 09:02 UTC, some AI-powered analysis features experienced slower than usual response times, with a small number of requests taking a few minutes to complete. All requests completed successfully and no data was affected. Response times have returned to normal and we're continuing to monitor. Affected components App (Operational)
Latest: Status: Resolved Resolved - Between 08:49 and 09:02 UTC, some AI-powered analysis features experienced slower than usual response times, with a small number of requests taking a fe…
-
- Started Aug 06, 2026, 08:53 AM UTC · Resolved Aug 06, 2026, 02:40 PM UTC · 5h 47m
- Started Jul 30, 2026, 09:11 AM UTC · Resolved Jul 30, 2026, 09:21 AM UTC · 9m