User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is MyTime 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 → get.mytime.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 22 min ago. Last stored result reached it in 480 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 |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 515 ms | 0 |
| Mon 19 | 0 | 0.0 | 218 ms | 0 |
| Mon 21 | 0 | 0.0 | 417 ms | 0 |
| Mon 22 | 0 | 0.0 | 285 ms | 0 |
| Tue 00 | 0 | 0.0 | 508 ms | 0 |
| Tue 02 | 0 | 0.0 | 519 ms | 0 |
| Tue 04 | 0 | 0.0 | 502 ms | 0 |
| Tue 06 | 0 | 0.0 | 304 ms | 0 |
| Tue 08 | 0 | 0.0 | 350 ms | 0 |
| Tue 10 | 0 | 0.0 | 433 ms | 0 |
| Tue 12 | 0 | 0.0 | 456 ms | 0 |
| Tue 14 | 0 | 0.0 | 428 ms | 0 |
| Tue 17 | 0 | 0.0 | 519 ms | 0 |
| Tue 19 | 0 | 0.0 | 236 ms | 0 |
| Tue 21 | 0 | 0.0 | 502 ms | 0 |
| Wed 00 | 0 | 0.0 | 563 ms | 0 |
| Wed 02 | 0 | 0.0 | 285 ms | 0 |
| Wed 04 | 0 | 0.0 | 432 ms | 0 |
| Wed 06 | 0 | 0.0 | 214 ms | 0 |
| Wed 08 | 0 | 0.0 | 440 ms | 0 |
| Wed 11 | 0 | 0.0 | 436 ms | 0 |
| Wed 13 | 0 | 0.0 | 288 ms | 0 |
| Wed 15 | 0 | 0.0 | 467 ms | 0 |
| Wed 17 | 0 | 0.0 | 422 ms | 0 |
| Wed 20 | 0 | 0.0 | 245 ms | 0 |
| Wed 22 | 0 | 0.0 | 508 ms | 0 |
| Thu 00 | 0 | 0.0 | 405 ms | 0 |
| Thu 02 | 0 | 0.0 | 649 ms | 0 |
| Thu 04 | 0 | 0.0 | 447 ms | 0 |
| Thu 06 | 0 | 0.0 | 476 ms | 0 |
| Thu 08 | 0 | 0.0 | 330 ms | 0 |
| Thu 10 | 0 | 0.0 | 453 ms | 0 |
| Thu 13 | 0 | 0.0 | 435 ms | 0 |
| Thu 15 | 0 | 0.0 | 551 ms | 0 |
| Thu 17 | 0 | 0.0 | 453 ms | 0 |
| Thu 19 | 0 | 0.0 | 366 ms | 0 |
| Thu 21 | 0 | 0.0 | 548 ms | 0 |
| Thu 23 | 0 | 0.0 | 417 ms | 0 |
| Fri 01 | 0 | 0.0 | 345 ms | 0 |
| Fri 03 | 0 | 0.0 | 503 ms | 0 |
| Fri 05 | 0 | 0.0 | 435 ms | 0 |
| Fri 07 | 0 | 0.0 | 455 ms | 0 |
| Fri 10 | 0 | 0.0 | 477 ms | 0 |
| Fri 12 | 0 | 0.0 | 472 ms | 0 |
| Fri 14 | 0 | 0.0 | 504 ms | 0 |
| Fri 16 | 0 | 0.0 | 483 ms | 0 |
| Fri 18 | 0 | 0.0 | 502 ms | 0 |
| Fri 20 | 0 | 0.0 | 480 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live MyTime 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 MyTime yet. Outages of 10 minutes or more get their own page here.
Having trouble with MyTime?
One report per service every 10 minutes from this network. No account.
Follow MyTime
Get an email when MyTime goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send MyTime alerts to Slack, Discord or a webhook — free.
About MyTime
MyTime, at get.mytime.com, is one of the AI services we monitor. MyTime is the leading franchise POS and Scheduling software built for multi-location service brands. Manage bookings, payments, marketing, memberships, payroll, and reporting across every location with one AI enabled platform.
MyTime publishes an official status page at status.mytime.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 466 ms average, 309–560 ms range across 13 successful checks.
Questions
Is MyTime down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was MyTime last down?
We have not recorded a public MyTime incident since monitoring began 8 days ago.
What is MyTime's uptime?
From our own checks: 100% over 8 days of checks.
How fast does MyTime respond?
466 ms on average over the last 24 hours (309–560 ms).
Does MyTime have an official status page?
Yes, at https://status.mytime.com.
MyTime 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 MyTime here at once, the problem is on MyTime'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 MyTime. 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.