Operations

Service Status

Real-time operational status for all Crawlo services

✓ All Systems Operational

Last checked: 2 minutes ago · All services running normally

99.97%
Uptime (30 days)
1.8s
Avg. Response Time
0
Active Incidents

Services

  • API v3 — Extraction
    99.98% uptimeOperational
  • API v3 — Batch Jobs
    99.95% uptimeOperational
  • Webhooks
    99.99% uptimeOperational
  • S3 / GCS Delivery
    99.97% uptimeOperational
  • SFTP Delivery
    99.96% uptimeOperational
  • Control Panel
    99.99% uptimeOperational
  • Proxy Network — Americas
    99.94% uptimeOperational
  • Proxy Network — Europe
    99.96% uptimeOperational
  • Proxy Network — Asia Pacific
    99.91% uptimeOperational

90-Day Uptime

Visual representation of daily service availability over the last 90 days. Green indicates full availability, yellow indicates partial degradation.

30 days agoToday

Recent Incidents

3 February 2025 Resolved

Elevated Latency on Asia-Pacific Proxy Pool

Latency increase (~2x normal) detected on residential proxies routed through Asia-Pacific nodes. Extraction jobs in affected regions experienced response times of 5-8s instead of the normal 2-3s.

14:45 UTC — Resolved

Node rebalancing completed. All proxy pools operating within normal parameters. No data loss.

14:12 UTC — Identified

Root cause identified: capacity imbalance on Singapore and Tokyo nodes following traffic spike. Initiating rebalancing.

14:00 UTC — Investigating

Monitoring alerts triggered for elevated P95 latency on APAC proxy pool. Investigating.

18 January 2025 Resolved

Scheduled Maintenance — API v3 Infrastructure

Planned 15-minute maintenance window for infrastructure upgrade and security patching.

04:15 UTC — Completed

Maintenance completed successfully. All services restored. No data loss or affected jobs. Queued requests processed automatically.

04:00 UTC — Started

Maintenance window started. API returning 503 with Retry-After header as expected.

29 December 2024 Resolved

Intermittent Webhook Delivery Failures

A subset of webhook deliveries (~3%) experienced timeouts due to a DNS resolution issue in our delivery pipeline.

11:30 UTC — Resolved

DNS resolver configuration updated. All pending webhooks redelivered successfully. Automatic retry mechanism caught all affected deliveries.

10:50 UTC — Identified

DNS resolver failover triggered but not routing correctly. Applying fix.

For real-time notifications, subscribe to status updates via email at [email protected] or follow our Changelog for platform updates.