Back

Member App

Event Detail

Fetches one known event detail endpoint used by the event detail screen.

Operational
Status
Operational
Latest result
Latency
511ms
Endpoint response
Pass rate
100%
Across recent checks
Frequency
5m
Configured cadence
Endpoint
GET https://api.livingroom.com/v1/events/184317

Recent results

Latest check ran 4m ago

Checked at
Apr 28, 17:43:58 UTC
Status
Operational
Latency
511ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 17:38:59 UTC
Status
Operational
Latency
640ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 17:33:58 UTC
Status
Operational
Latency
468ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 17:28:58 UTC
Status
Operational
Latency
322ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 17:23:58 UTC
Status
Operational
Latency
480ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 17:18:59 UTC
Status
Operational
Latency
576ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 17:13:58 UTC
Status
Operational
Latency
434ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 17:08:58 UTC
Status
Operational
Latency
311ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 17:03:58 UTC
Status
Operational
Latency
452ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:58:58 UTC
Status
Operational
Latency
388ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:53:58 UTC
Status
Operational
Latency
417ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:48:58 UTC
Status
Operational
Latency
359ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:43:58 UTC
Status
Operational
Latency
417ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:38:58 UTC
Status
Operational
Latency
356ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:33:58 UTC
Status
Operational
Latency
423ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:28:58 UTC
Status
Operational
Latency
310ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:23:58 UTC
Status
Operational
Latency
422ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:18:58 UTC
Status
Operational
Latency
345ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:13:58 UTC
Status
Operational
Latency
375ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:08:59 UTC
Status
Operational
Latency
1.2s
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:03:59 UTC
Status
Operational
Latency
832ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 16:01:10 UTC
Status
Operational
Latency
372ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:56:10 UTC
Status
Operational
Latency
1.2s
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:51:10 UTC
Status
Operational
Latency
386ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:46:09 UTC
Status
Operational
Latency
322ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:42:48 UTC
Status
Operational
Latency
481ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:37:48 UTC
Status
Operational
Latency
450ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:32:48 UTC
Status
Operational
Latency
468ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:27:49 UTC
Status
Operational
Latency
1.2s
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:22:48 UTC
Status
Operational
Latency
512ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:17:48 UTC
Status
Operational
Latency
586ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:12:48 UTC
Status
Operational
Latency
471ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:07:48 UTC
Status
Operational
Latency
455ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 15:02:48 UTC
Status
Operational
Latency
460ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:57:48 UTC
Status
Operational
Latency
388ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:52:48 UTC
Status
Operational
Latency
689ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:47:48 UTC
Status
Operational
Latency
525ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:42:48 UTC
Status
Operational
Latency
521ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:37:48 UTC
Status
Operational
Latency
448ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:32:48 UTC
Status
Operational
Latency
480ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:27:48 UTC
Status
Operational
Latency
481ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:22:48 UTC
Status
Operational
Latency
536ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:17:48 UTC
Status
Operational
Latency
486ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:12:48 UTC
Status
Operational
Latency
523ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:07:48 UTC
Status
Operational
Latency
648ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 14:02:48 UTC
Status
Operational
Latency
440ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 13:57:48 UTC
Status
Operational
Latency
536ms
HTTP
200
Message

Event detail responded

Checked at
Apr 28, 13:52:48 UTC
Status
Operational
Latency
429ms
HTTP
200
Message

Event detail responded