Uptime (Last 90 Days)
✓
Account Login
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 49 ms
Detail: Healthy response
MAY 2026 • 100.0%
JUN 2026 • 100.0%
JUL 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Get Connected Users
99.98% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 67 ms
Detail: Healthy response
MAY 2026 • 100.0%
JUN 2026 • 100.0%
JUL 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Get User Messages
99.98% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 114 ms
Detail: Healthy response
MAY 2026 • 100.0%
JUN 2026 • 100.0%
JUL 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Log SMS Message
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 56 ms
Detail: Healthy response
MAY 2026 • 100.0%
JUN 2026 • 100.0%
JUL 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Register FCM Token
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 312 ms
Detail: Healthy response
MAY 2026 • 100.0%
JUN 2026 • 100.0%
JUL 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Send Health Ping
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 56 ms
Detail: Healthy response
MAY 2026 • 100.0%
JUN 2026 • 100.0%
JUL 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Send SMS Command
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 414 ms
Detail: Healthy response
MAY 2026 • 100.0%
JUN 2026 • 100.0%
JUL 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
✓
Update SMS Status
100.00% uptime
Current: OPERATIONAL
HTTP: 200
Latency: 61 ms
Detail: Healthy response
MAY 2026 • 100.0%
JUN 2026 • 100.0%
JUL 2026 • 100.0%
‹ 90 DAYS AGO
TODAY
Past Incidents
Aug 2026
01 Aug - 31 Aug 2026
Get User Messages
RESOLVED
Identified: 2026-08-06 14:30
Resolved:
2026-08-06 15:00
Note: cURL: Resolving timed out after 5380 milliseconds
Resolved: Issue detected via automated monitoring and resolved by our developers team.
Jul 2026
01 Jul - 31 Jul 2026
Get Connected Users
RESOLVED
Identified: 2026-07-29 01:31
Resolved:
2026-07-29 02:00
Note: cURL: Operation timed out after 12002 milliseconds with 0 bytes received
Resolved: Issue detected via automated monitoring and resolved by our develope…
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…