DropstoneDropstone Status
All operational

All systems operational

All Dropstone and Blankline Research services are running normally.

Last checked 23 Nov 2026, 2:53 am IST·every 5 minutes

Components

6 operational

Dropstone

Consumer-facing AI coding products.

Dropstone Dashboard

dropstone.io

Public website, sign-in, and user dashboard.

Operational
99.98 % uptimeAug 25 – Today

Dropstone API

api.dropstone.io

Backend API, authentication, billing, and model routing.

Operational
99.93 % uptimeAug 25 – Today

Dropstone CLI

Chat completions, model routing, and CLI backend.

Operational
99.98 % uptimeAug 25 – Today

Dropstone Chat

chat.dropstone.io

Web chat client, sharing the same account and credit pool.

Operational
100.00 % uptime57 days of history

Billing & Payments

Stripe billing, webhooks, and subscription management.

Operational
99.93 % uptimeAug 25 – Today

Blankline Research

Engineering infrastructure for AI.

Dropstone for Blankline Research

blankline.org

Internal research infrastructure and shared services.

Operational
99.81 % uptimeAug 25 – Today

Uptime over the past 90 days

Incident history

55 incidents on record

30 May 20262 incidents
17:07
31 May, 19:06
Resolved

Billing webhooks processing normally. No subscription impact.

31 May, 10:26
Monitoring

Webhook queue drained. Subscription state consistent.

31 May, 01:47
Identified

Webhook endpoint experienced intermittent timeouts during deploy.

17:07
Investigating

Stripe webhook delivery delays. Subscription updates briefly delayed.

16:21
31 May, 20:05
Resolved

Blankline Research infrastructure fully operational.

31 May, 10:50
Monitoring

Node recovered. All internal services responding normally.

31 May, 01:36
Identified

Shared infrastructure node experienced CPU throttle under load.

16:21
Investigating

Internal research API returning intermittent 504 errors.

29 May 20262 incidents
11:05
31 May, 18:31
Resolved

CLI chat services fully operational. All models routing normally.

31 May, 00:02
Monitoring

Upstream provider stabilized. Chat success rate recovering.

30 May, 05:33
Identified

Upstream model provider degraded performance affecting chat routing.

11:05
Investigating

Chat completion requests intermittently failing with upstream errors.

09:59
31 May, 19:02
Resolved

API services fully operational. No further errors.

31 May, 00:01
Monitoring

Connection pool recovered. API latency back within normal thresholds.

30 May, 05:00
Identified

Backend connection pool exhaustion from upstream latency spike.

09:59
Investigating

Elevated error rates on API health checks. Some endpoints returning 502.

28 May 20261 incident
08:30
31 May, 15:47
Resolved

Dashboard fully operational. All routes stable.

30 May, 13:21
Monitoring

Network routes re-converged. Dashboard response times normalizing.

29 May, 10:55
Identified

Network partition between edge monitoring nodes and primary Railway infrastructure.

08:30
Investigating

Users reporting slow page loads and intermittent 503 errors on the dashboard.