Uptime (Last 90 Days)
✓
Analytics Endpoint
96.53% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 78 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 71.0%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Core API - Live Location (vts/v1)
99.79% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 88 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 80.6%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Core API - URL Validation (v4)
99.79% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 97 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 80.6%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Core API - White Label (v3)
99.79% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 84 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 80.6%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Main Page
99.79% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 98 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 80.6%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
Past Incidents
Apr 2026
01 Apr - 30 Apr 2026
Core API - White Label (v3)
RESOLVED
Identified: 2026-04-15 20:30
Resolved:
2026-04-15 21:00
Note: cURL: Failed to connect to ecocosmogps.in port 443 after 1 ms: Couldn't connect to server
Resolved: Issue detected via automated monitoring and resolve…
Core API - Live Location (vts/v1)
RESOLVED
Identified: 2026-04-15 20:30
Resolved:
2026-04-15 21:00
Note: cURL: Failed to connect to ecocosmogps.in port 443 after 1 ms: Couldn't connect to server
Resolved: Issue detected via automated monitoring and resolve…
Mar 2026
01 Mar - 31 Mar 2026
Analytics Endpoint
RESOLVED
Identified: 2026-03-25 11:00
Resolved:
2026-03-27 12:17
Note: Unexpected HTTP 201
Resolved: Issue detected via automated monitoring and resolved by our developers team.
Analytics Endpoint
RESOLVED
Identified: 2026-03-07 18:50
Resolved:
2026-03-08 09:55
Note: Unexpected HTTP 404
Resolved: Auto-resolved on healthy check