User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 6 min ago. Last stored result reached it in 465 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 455 ms | 0 |
| Nov 7 | 0 | 0.0 | 523 ms | 0 |
| Nov 7 | 0 | 0.0 | 530 ms | 0 |
| Nov 7 | 0 | 0.0 | 507 ms | 0 |
| Nov 8 | 0 | 0.0 | 464 ms | 0 |
| Nov 8 | 0 | 0.0 | 468 ms | 0 |
| Nov 8 | 0 | 0.0 | 610 ms | 0 |
| Nov 8 | 0 | 0.0 | 496 ms | 0 |
| Nov 9 | 0 | 0.0 | 1023 ms | 0 |
| Nov 9 | 0 | 0.0 | 432 ms | 0 |
| Nov 9 | 0 | 0.0 | 479 ms | 0 |
| Nov 9 | 0 | 0.0 | 591 ms | 0 |
| Nov 10 | 0 | 0.0 | 445 ms | 0 |
| Nov 10 | 0 | 0.0 | 425 ms | 0 |
| Nov 10 | 0 | 0.0 | 481 ms | 0 |
| Nov 10 | 0 | 0.0 | 558 ms | 0 |
| Nov 11 | 0 | 0.0 | 609 ms | 0 |
| Nov 11 | 0 | 0.0 | 455 ms | 0 |
| Nov 11 | 0 | 0.0 | 504 ms | 0 |
| Nov 11 | 0 | 0.0 | 401 ms | 0 |
| Nov 12 | 0 | 0.0 | 477 ms | 0 |
| Nov 12 | 0 | 0.0 | 573 ms | 0 |
| Nov 12 | 0 | 0.0 | 453 ms | 0 |
| Nov 12 | 0 | 0.0 | 568 ms | 0 |
| Nov 13 | 0 | 0.0 | 449 ms | 0 |
| Nov 13 | 0 | 0.0 | 476 ms | 0 |
| Nov 13 | 0 | 0.0 | 490 ms | 0 |
| Nov 13 | 0 | 0.0 | 549 ms | 0 |
| Nov 14 | 0 | 0.0 | 480 ms | 0 |
| Nov 14 | 0 | 0.0 | 501 ms | 0 |
| Nov 14 | 0 | 0.0 | 635 ms | 0 |
| Nov 14 | 0 | 0.0 | 462 ms | 0 |
| Nov 15 | 0 | 0.0 | 535 ms | 0 |
| Nov 15 | 0 | 0.0 | 531 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Imply Polaris 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 Imply Polaris goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track Imply Polaris (imply.io) as part of the Cloud & developer group. Lumi Loglake is now generally available in Imply Lumi. Learn more. The data platform for the agentic SIEM Immediate access to all your security data, wherever it lives. Contact Us Request a Demo Imply Lumi Works with existing SIEM frontends and modern agents. Search logs where they already live. Search hot and historical security data […]
Imply Polaris publishes an official status page at status.imply.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 584 ms average, 439–1141 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Imply Polaris incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
584 ms on average over the last 24 hours (439–1141 ms).
Yes, at https://status.imply.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Imply Polaris here at once, the problem is on Imply Polaris's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Imply Polaris. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.