User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
viktor.com · AI
Is Viktor 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 → viktor.com—
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 1 hr ago. Last stored result reached it in 393 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 478 ms | 0 |
| Mon 14 | 0 | 0.0 | 530 ms | 0 |
| Mon 16 | 0 | 0.0 | 361 ms | 0 |
| Mon 18 | 0 | 0.0 | 572 ms | 0 |
| Mon 20 | 0 | 0.0 | 493 ms | 0 |
| Mon 22 | 0 | 0.0 | 540 ms | 0 |
| Tue 00 | 0 | 0.0 | 414 ms | 0 |
| Tue 03 | 0 | 0.0 | 865 ms | 0 |
| Tue 05 | 0 | 0.0 | 821 ms | 0 |
| Tue 07 | 0 | 0.0 | 548 ms | 0 |
| Tue 09 | 0 | 0.0 | 493 ms | 0 |
| Tue 11 | 0 | 0.0 | 338 ms | 0 |
| Tue 13 | 0 | 0.0 | 520 ms | 0 |
| Tue 15 | 0 | 0.0 | 418 ms | 0 |
| Tue 18 | 0 | 0.0 | 337 ms | 0 |
| Tue 20 | 0 | 0.0 | 437 ms | 0 |
| Tue 22 | 0 | 0.0 | 669 ms | 0 |
| Wed 00 | 0 | 0.0 | 333 ms | 0 |
| Wed 03 | 0 | 0.0 | 346 ms | 0 |
| Wed 05 | 0 | 0.0 | 463 ms | 0 |
| Wed 07 | 0 | 0.0 | 585 ms | 0 |
| Wed 10 | 0 | 0.0 | 308 ms | 0 |
| Wed 12 | 0 | 0.0 | 1034 ms | 0 |
| Wed 14 | 0 | 0.0 | 545 ms | 0 |
| Wed 16 | 0 | 0.0 | 578 ms | 0 |
| Wed 18 | 0 | 0.0 | 534 ms | 0 |
| Wed 20 | 0 | 0.0 | 500 ms | 0 |
| Wed 23 | 0 | 0.0 | 364 ms | 0 |
| Thu 01 | 0 | 0.0 | 425 ms | 0 |
| Thu 03 | 0 | 0.0 | 450 ms | 0 |
| Thu 05 | 0 | 0.0 | 402 ms | 0 |
| Thu 07 | 0 | 0.0 | 506 ms | 0 |
| Thu 09 | 0 | 0.0 | 429 ms | 0 |
| Thu 11 | 0 | 0.0 | 611 ms | 0 |
| Thu 13 | 0 | 0.0 | 424 ms | 0 |
| Thu 16 | 0 | 0.0 | 412 ms | 0 |
| Thu 18 | 0 | 0.0 | 504 ms | 0 |
| Thu 20 | 0 | 0.0 | 437 ms | 0 |
| Thu 22 | 0 | 0.0 | 544 ms | 0 |
| Fri 00 | 0 | 0.0 | 576 ms | 0 |
| Fri 02 | 0 | 0.0 | 381 ms | 0 |
| Fri 04 | 0 | 0.0 | 641 ms | 0 |
| Fri 06 | 0 | 0.0 | 594 ms | 0 |
| Fri 08 | 0 | 0.0 | 403 ms | 0 |
| Fri 10 | 0 | 0.0 | 408 ms | 0 |
| Fri 11 | 0 | 0.0 | 495 ms | 0 |
| Fri 13 | 0 | 0.0 | 792 ms | 0 |
| Fri 15 | 0 | 0.0 | 393 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Viktor 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 Viktor yet. Outages of 10 minutes or more get their own page here.
Having trouble with Viktor?
One report per service every 10 minutes from this network. No account.
Follow Viktor
Get an email when Viktor goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Viktor alerts to Slack, Discord or a webhook — free.
About Viktor
We track Viktor (viktor.com) as part of the AI group. Viktor is the AI employee that lives in Slack and Microsoft Teams, connects to 9,800+ tools, and does the work. Reports, dashboards, code, campaigns. Start free.
Viktor publishes an official status page at status.viktor.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 514 ms average, 344–792 ms range across 14 successful checks.
Questions
Is Viktor down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Viktor last down?
We have not recorded a public Viktor incident since monitoring began 8 days ago.
What is Viktor's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Viktor respond?
514 ms on average over the last 24 hours (344–792 ms).
Does Viktor have an official status page?
Yes, at https://status.viktor.com.
Viktor 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Viktor here at once, the problem is on Viktor'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 Viktor. 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.