Status Dashboard
System health and availability monitoring
Apps 3
Healthy 3
Last Check 20:00
GPS India OPERATIONAL
100.0% healthy 43/43 operational
Degraded: 0 • Outage: 0
Updated: 2026-06-16 20:00:07
Live Tracking URL OPERATIONAL
100.0% healthy 5/5 operational
Degraded: 0 • Outage: 0
Updated: 2026-06-16 20:00:08
SMS Gateway OPERATIONAL
100.0% healthy 8/8 operational
Degraded: 0 • Outage: 0
Updated: 2026-06-16 20:00:10
Uptime (Last 90 Days)
✓ Account Login
99.77% uptime
Current: OPERATIONAL HTTP: 200 Latency: 70 ms Detail: Healthy response
MAR 2026 • 38.5% APR 2026 • 100.0% MAY 2026 • 100.0%
‹ 90 DAYS AGO TODAY
‹ ›
No downtime reported
✓ Get Connected Users
100.00% uptime
Current: OPERATIONAL HTTP: 200 Latency: 71 ms Detail: Healthy response
MAR 2026 • 38.5% APR 2026 • 100.0% MAY 2026 • 100.0%
‹ 90 DAYS AGO TODAY
‹ ›
No downtime reported
✓ Get User Messages
100.00% uptime
Current: OPERATIONAL HTTP: 200 Latency: 108 ms Detail: Healthy response
MAR 2026 • 38.5% APR 2026 • 100.0% MAY 2026 • 100.0%
‹ 90 DAYS AGO TODAY
‹ ›
No downtime reported
✓ Log SMS Message
100.00% uptime
Current: OPERATIONAL HTTP: 200 Latency: 125 ms Detail: Healthy response
MAR 2026 • 38.5% APR 2026 • 100.0% MAY 2026 • 100.0%
‹ 90 DAYS AGO TODAY
‹ ›
No downtime reported
✓ Register FCM Token
100.00% uptime
Current: OPERATIONAL HTTP: 200 Latency: 482 ms Detail: Healthy response
MAR 2026 • 38.5% APR 2026 • 100.0% MAY 2026 • 100.0%
‹ 90 DAYS AGO TODAY
‹ ›
No downtime reported
✓ Send Health Ping
100.00% uptime
Current: OPERATIONAL HTTP: 200 Latency: 67 ms Detail: Healthy response
MAR 2026 • 38.5% APR 2026 • 100.0% MAY 2026 • 100.0%
‹ 90 DAYS AGO TODAY
‹ ›
No downtime reported
✓ Send SMS Command
99.97% uptime
Current: OPERATIONAL HTTP: 200 Latency: 369 ms Detail: Healthy response
MAR 2026 • 38.5% APR 2026 • 100.0% MAY 2026 • 100.0%
‹ 90 DAYS AGO TODAY
‹ ›
No downtime reported
✓ Update SMS Status
100.00% uptime
Current: OPERATIONAL HTTP: 200 Latency: 105 ms Detail: Healthy response
MAR 2026 • 38.5% APR 2026 • 100.0% MAY 2026 • 100.0%
‹ 90 DAYS AGO TODAY
‹ ›
No downtime reported
Past Incidents
Apr 2026 01 Apr - 30 Apr 2026
Account Login
RESOLVED
Identified: 2026-04-16 09:30 Resolved: 2026-04-16 10: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…
Account Login
RESOLVED
Identified: 2026-04-16 08:30 Resolved: 2026-04-16 09: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…
Account Login
RESOLVED
Identified: 2026-04-16 06:30 Resolved: 2026-04-16 07: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…
Account Login
RESOLVED
Identified: 2026-04-16 05:30 Resolved: 2026-04-16 06: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…
Account Login
RESOLVED
Identified: 2026-04-16 04:30 Resolved: 2026-04-16 05: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…
Account Login
RESOLVED
Identified: 2026-04-16 03:30 Resolved: 2026-04-16 04:00
Note: Invalid JSON response Resolved: Issue detected via automated monitoring and resolved by our developers team.
Account Login
RESOLVED
Identified: 2026-04-16 02:30 Resolved: 2026-04-16 03:00
Note: cURL: Failed to connect to ecocosmogps.in port 443 after 3 ms: Couldn't connect to server Resolved: Issue detected via automated monitoring and resolve…
Account Login
RESOLVED
Identified: 2026-04-15 21:30 Resolved: 2026-04-15 22: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…
Account Login
RESOLVED
Identified: 2026-04-15 20:30 Resolved: 2026-04-15 21:00
Note: cURL: Failed to connect to ecocosmogps.in port 443 after 2 ms: Couldn't connect to server Resolved: Issue detected via automated monitoring and resolve…
Mar 2026 01 Mar - 31 Mar 2026
Send SMS Command
RESOLVED
Identified: 2026-03-27 13:31 Resolved: 2026-03-27 13:33
Note: Unexpected HTTP 200 Resolved: Issue detected via automated monitoring and resolved by our developers team.