Live status

All systems operational. Updated continuously.

Every public AgentLoka service is responding within normal bounds. Subscribe to be notified the moment anything changes.

Last updated: just now·Tracked from 4 regions every 30s
Components

Per-service health.

Marketplace
Last incident: 78 days ago
Operational
API
Last incident: 12 days ago
Operational
Webhooks
Last incident: 21 days ago
Operational
Run execution
Last incident: 5 days ago
Operational
Stripe billing
Last incident: no incidents in 90d
Operational
OAuth gateway
Last incident: 33 days ago
Operational
Notifications
Last incident: 47 days ago
Operational
Status page
Last incident: no incidents in 90d
Operational
90-day history

Every day. Every service.

Marketplace
98.89% uptime
API
98.89% uptime
Webhooks
96.67% uptime
Run execution
100.00% uptime
Stripe billing
98.89% uptime
OAuth gateway
100.00% uptime
Notifications
100.00% uptime
Status page
98.89% uptime

Newest day on the right. Green = operational. Amber = a minor incident that didn't fail customer runs. Red = a true outage. Hover any day for the date.

Recent incidents

The last 90 days,

Run worker pool exhausted in EU-Frankfurt

2026-05-23·Run execution
Resolved

Between 14:02–14:38 UTC, runs queued in EU-Frankfurt experienced p95 start latency of 38s (normal: 1.2s) due to a slow-leaking worker that survived health checks. A single misbehaving customer agent in an infinite tool-call loop monopolised four workers; our concurrency limiter only kicked in on the fifth. We've shipped a stricter per-agent worker cap (max 2) and added a synthetic 'is this worker doing real work' check that runs every 60s. No data loss, no failed runs. Every queued run completed once the pool was rebalanced.

Webhook delivery delayed for 8 minutes

2026-05-16·Webhooks
Resolved

A noisy neighbour on the shared notifications cluster triggered a self-healing restart that took 8 minutes longer than expected. All queued webhooks delivered with retry; no events were dropped. Moved webhooks to a dedicated cluster on 2026-05-17.

OAuth refresh failures for one upstream provider

2026-05-07·OAuth gateway
Resolved

An upstream API rotated its OAuth signing key without notice. Existing access tokens kept working; refresh attempts failed silently. Detected via our synthetic check at 09:14 UTC; mitigated by 09:41 by switching to the new key. ~430 buyer connections required a one-click re-auth.

Stay informed

Subscribe to status updates.

Channels