User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
equinixmetal.com · AI
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
Live diagnosis
Tests equinixmetal.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Not enough checks
Last check reached it in 364 ms · 5 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 545 ms | 0 |
| 03:15 | 0 | 0.0 | 488 ms | 0 |
| 03:30 | 0 | 0.0 | 779 ms | 0 |
| 03:45 | 0 | 0.0 | 444 ms | 0 |
| 04:00 | 0 | 0.0 | 283 ms | 0 |
| 04:15 | 0 | 0.0 | 335 ms | 0 |
| 04:30 | 0 | 0.0 | 337 ms | 0 |
| 04:45 | 0 | 0.0 | 822 ms | 0 |
| 05:00 | 0 | 0.0 | 451 ms | 0 |
| 05:15 | 0 | 0.0 | 418 ms | 0 |
| 05:30 | 0 | 0.0 | 300 ms | 0 |
| 05:45 | 0 | 0.0 | 773 ms | 0 |
| 06:00 | 0 | 0.0 | 503 ms | 0 |
| 06:15 | 0 | 0.0 | 811 ms | 0 |
| 06:30 | 0 | 0.0 | 379 ms | 0 |
| 06:45 | 0 | 0.0 | 423 ms | 0 |
| 07:00 | 0 | 0.0 | 342 ms | 0 |
| 07:15 | 0 | 0.0 | 259 ms | 0 |
| 07:30 | 0 | 0.0 | 512 ms | 0 |
| 07:45 | 0 | 0.0 | 176 ms | 0 |
| 08:00 | 0 | 0.0 | 469 ms | 0 |
| 08:15 | 0 | 0.0 | 689 ms | 0 |
| 08:30 | 0 | 0.0 | 645 ms | 0 |
| 08:45 | 0 | 0.0 | 585 ms | 0 |
| 09:00 | 0 | 0.0 | 308 ms | 0 |
| 09:15 | 0 | 0.0 | 494 ms | 0 |
| 09:30 | 0 | 0.0 | 507 ms | 0 |
| 09:45 | 0 | 0.0 | 610 ms | 0 |
| 10:00 | 0 | 0.0 | 341 ms | 0 |
| 10:15 | 0 | 0.0 | 603 ms | 0 |
| 10:30 | 0 | 0.0 | 726 ms | 0 |
| 10:45 | 0 | 0.0 | 577 ms | 0 |
| 11:00 | 0 | 0.0 | 514 ms | 0 |
| 11:15 | 0 | 0.0 | 662 ms | 0 |
| 11:30 | 0 | 0.0 | 232 ms | 0 |
| 11:45 | 0 | 0.0 | 808 ms | 0 |
| 12:00 | 0 | 0.0 | 929 ms | 0 |
| 12:15 | 0 | 0.0 | 897 ms | 0 |
| 12:30 | 0 | 0.0 | 494 ms | 0 |
| 12:45 | 0 | 0.0 | 419 ms | 0 |
| 13:00 | 0 | 0.0 | 377 ms | 0 |
| 13:15 | 0 | 0.0 | 416 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Packet yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Packet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Packet alerts to Slack, Discord or a webhook — free.
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
If Packet is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Packet's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.