This dashboard fans out to eleven applications written in six languages
— PHP (twice), Ruby, Go, Python, Java and JavaScript (five times,
across two runtimes) — all running together in one Laravel Cloud
environment, all sharing one managed Postgres database, and all
implementing the exact same HTTP contract.
Click a chip to fire one real request between two live services —
no arming, no modes. The result lands right on the card. “Run the
mesh” fires the same real requests, one at a time, between the peer
services so you can watch the path move without clicking anything.
service-php
healthy
language
PHP
runtime
8.5.10
framework
none
region
eu-west-2
uptime
71690s
memory (rss)
26 MB
memory (own)
2 MB
boot
no process boot — per-request runtime
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (3 samples in 15m)
fan-out
2083ms
message
Hello from PHP on Laravel Cloud
△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.
unreachable — cURL error 28: Operation timed out after 2000 milliseconds with 0 bytes received (see https://curl.se/libcurl/c/libcurl-errors.html) for https://polyglot-ruby-main-rhf0mh.laravel.cloud/info
△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.
△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.
△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.
△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.
⚠ can serve requests but cannot reach the database
△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.
⚠ can serve requests but cannot reach the database
△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.
⚠ can serve requests but cannot reach the database
△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.
⚠ can serve requests but cannot reach the database
△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.
⚠ can serve requests but cannot reach the database
△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.
Laravel Cloud's own end-to-end build-and-deploy duration for each
app — compile, image build, push and rollout, not just a
compile step. Polled from the Cloud API every few minutes by a
scheduled job and cached here; this page never calls that API
itself.
Build times unavailable — no Cloud API token is configured yet.
Live activity
Live — updates every few seconds
just nowdashboard (PHP) fanned out to every peer · 2083 ms
0 seconds agoservice-ruby (Ruby) reported its status · under 1 ms
0 seconds agoservice-go (Go) reported its status · 5 ms
0 seconds agoservice-python (Python) reported its status · under 1 ms
0 seconds agoservice-java (Java) reported its status · under 1 ms
0 seconds agoservice-rust (Rust) reported its status · under 1 ms
0 seconds agoservice-php (PHP) reported its status · under 1 ms
14 minutes agoservice-php (PHP) reported its status · under 1 ms
14 minutes agoservice-rust (Rust) asked service-php for /info · 91 ms
14 minutes agoservice-rust (Rust) reported its status · under 1 ms
14 minutes agoservice-java (Java) asked service-javascript for /info · 155 ms
14 minutes agoservice-python (Python) asked service-java for /info · 109 ms
14 minutes agoservice-java (Java) reported its status · under 1 ms
14 minutes agoservice-go (Go) asked service-python for /info · 64 ms
14 minutes agoservice-python (Python) reported its status · under 1 ms
14 minutes agoservice-go (Go) reported its status · under 1 ms
14 minutes agoservice-ruby (Ruby) asked service-go for /info · 70 ms
14 minutes agoservice-php (PHP) asked service-ruby for /info · 161 ms
14 minutes agoservice-ruby (Ruby) reported its status · under 1 ms
15 minutes agodashboard (PHP) fanned out to every peer · 526 ms
15 minutes agoservice-php (PHP) reported its status · under 1 ms
15 minutes agoservice-go (Go) reported its status · under 1 ms
15 minutes agoservice-ruby (Ruby) reported its status · under 1 ms
15 minutes agoservice-python (Python) reported its status · under 1 ms
15 minutes agoservice-rust (Rust) reported its status · under 1 ms
15 minutes agoservice-java (Java) reported its status · under 1 ms
15 minutes agoservice-php (PHP) reported its status · under 1 ms
15 minutes agoservice-rust (Rust) asked service-php for /info · 74 ms
15 minutes agoservice-rust (Rust) reported its status · under 1 ms
15 minutes agoservice-java (Java) asked service-javascript for /info · 95 ms
15 minutes agoservice-python (Python) asked service-java for /info · 93 ms
15 minutes agoservice-java (Java) reported its status · under 1 ms
15 minutes agoservice-go (Go) asked service-python for /info · 79 ms
15 minutes agoservice-python (Python) reported its status · under 1 ms
15 minutes agoservice-go (Go) reported its status · under 1 ms
15 minutes agoservice-ruby (Ruby) asked service-go for /info · 81 ms
15 minutes agoservice-php (PHP) asked service-ruby for /info · 141 ms
15 minutes agoservice-ruby (Ruby) reported its status · under 1 ms
16 minutes agodashboard (PHP) fanned out to every peer · 513 ms
16 minutes agoservice-rust (Rust) reported its status · under 1 ms
16 minutes agoservice-php (PHP) reported its status · under 1 ms
16 minutes agoservice-go (Go) reported its status · under 1 ms
16 minutes agoservice-ruby (Ruby) reported its status · under 1 ms
16 minutes agoservice-python (Python) reported its status · under 1 ms
16 minutes agoservice-java (Java) reported its status · under 1 ms
18 minutes agodashboard (PHP) fanned out to every peer · 553 ms
18 minutes agoservice-php (PHP) reported its status · under 1 ms
18 minutes agoservice-go (Go) reported its status · under 1 ms
18 minutes agoservice-ruby (Ruby) reported its status · under 1 ms
18 minutes agoservice-python (Python) reported its status · under 1 ms