Uptime (Last 90 Days)
✓
Account Login
99.68% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 70 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 16.1%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Get Connected Users
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 60 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 16.1%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Get User Messages
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 379 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 16.1%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Log SMS Message
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 57 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 16.1%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Register FCM Token
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 68 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 16.1%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Send Health Ping
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 58 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 16.1%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Send SMS Command
99.96% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 409 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 16.1%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Update SMS Status
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 60 ms
Detail: Healthy response
FEB 2026 • 0.0%
MAR 2026 • 16.1%
APR 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
Past Incidents
Apr 2026
01 Apr - 30 Apr 2026
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…
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…
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…
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…
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…
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.
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…
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…
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.