User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Imply Polaris down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → imply.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 min ago. Last stored result reached it in 485 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 08 | 0 | 0.0 | 450 ms | 0 |
| Wed 10 | 0 | 0.0 | 459 ms | 0 |
| Wed 12 | 0 | 0.0 | 390 ms | 0 |
| Wed 14 | 0 | 0.0 | 1224 ms | 0 |
| Wed 16 | 0 | 0.0 | 504 ms | 0 |
| Wed 18 | 0 | 0.0 | 405 ms | 0 |
| Wed 21 | 0 | 0.0 | 454 ms | 0 |
| Wed 23 | 0 | 0.0 | 334 ms | 0 |
| Thu 01 | 0 | 0.0 | 730 ms | 0 |
| Thu 03 | 0 | 0.0 | 462 ms | 0 |
| Thu 05 | 0 | 0.0 | 477 ms | 0 |
| Thu 07 | 0 | 0.0 | 769 ms | 0 |
| Thu 09 | 0 | 0.0 | 573 ms | 0 |
| Thu 11 | 0 | 0.0 | 374 ms | 0 |
| Thu 13 | 0 | 0.0 | 470 ms | 0 |
| Thu 15 | 0 | 0.0 | 435 ms | 0 |
| Thu 18 | 0 | 0.0 | 514 ms | 0 |
| Thu 20 | 0 | 0.0 | 1100 ms | 0 |
| Thu 22 | 0 | 0.0 | 568 ms | 0 |
| Fri 00 | 0 | 0.0 | 628 ms | 0 |
| Fri 02 | 0 | 0.0 | 325 ms | 0 |
| Fri 04 | 0 | 0.0 | 443 ms | 0 |
| Fri 06 | 0 | 0.0 | 393 ms | 0 |
| Fri 08 | 0 | 0.0 | 482 ms | 0 |
| Fri 10 | 0 | 0.0 | 554 ms | 0 |
| Fri 11 | 0 | 0.0 | 470 ms | 0 |
| Fri 13 | 0 | 0.0 | 415 ms | 0 |
| Fri 15 | 0 | 0.0 | 490 ms | 0 |
| Fri 17 | 0 | 0.0 | 575 ms | 0 |
| Fri 19 | 0 | 0.0 | 679 ms | 0 |
| Fri 21 | 0 | 0.0 | 474 ms | 0 |
| Fri 23 | 0 | 0.0 | 549 ms | 0 |
| Sat 01 | 0 | 0.0 | 567 ms | 0 |
| Sat 03 | 0 | 0.0 | 408 ms | 0 |
| Sat 05 | 0 | 0.0 | 478 ms | 0 |
| Sat 07 | 0 | 0.0 | 544 ms | 0 |
| Sat 09 | 0 | 0.0 | 458 ms | 0 |
| Sat 12 | 0 | 0.0 | 515 ms | 0 |
| Sat 13 | 0 | 0.0 | 855 ms | 0 |
| Sat 16 | 0 | 0.0 | 685 ms | 0 |
| Sat 18 | 0 | 0.0 | 462 ms | 0 |
| Sat 20 | 0 | 0.0 | 572 ms | 0 |
| Sat 23 | 0 | 0.0 | 439 ms | 0 |
| Sun 01 | 0 | 0.0 | 628 ms | 0 |
| Sun 03 | 0 | 0.0 | 442 ms | 0 |
| Sun 06 | 0 | 0.0 | 1141 ms | 0 |
| Sun 08 | 0 | 0.0 | 485 ms | 0 |
| Sun 10 | 0 | 0.0 | 518 ms | 0 |
Reliability
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.
Embed this status: free live Imply Polaris badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Imply Polaris yet. Outages of 10 minutes or more get their own page here.
Having trouble with Imply Polaris?
One report per service every 10 minutes from this network. No account.
Follow Imply Polaris
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.
About Imply Polaris
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: 588 ms average, 439–1141 ms range across 14 successful checks.
Questions
Is Imply Polaris down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Imply Polaris last down?
We have not recorded a public Imply Polaris incident since monitoring began 9 days ago.
What is Imply Polaris's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Imply Polaris respond?
588 ms on average over the last 24 hours (439–1141 ms).
Does Imply Polaris have an official status page?
Yes, at https://status.imply.io.
Imply Polaris not working for me but the status is fine. What now?
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.