User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
timerex.net · Cloud & developer
Is TimeRex down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Outlook予定表をはじめMicrosoft 365において障害が発生しています
Source: the vendor's status page · We are not affiliated with TimeRex.
What to try while TimeRex is having problems
Estimated fix: Not enough TimeRex history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–11 h; 80 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
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 → timerex.net—
Your browser → us—
Our checksReaching it
Official · ReportsMajor incident · 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 24 min ago. Last stored result reached it in 548 ms.
Official status
Major incident
Outlook予定表をはじめMicrosoft 365において障害が発生しています Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 501 ms | 0 |
| Mon 15 | 0 | 0.0 | 473 ms | 0 |
| Mon 17 | 0 | 0.0 | 672 ms | 0 |
| Mon 19 | 0 | 0.0 | 537 ms | 0 |
| Mon 21 | 0 | 0.0 | 497 ms | 0 |
| Tue 00 | 0 | 0.0 | 612 ms | 0 |
| Tue 02 | 0 | 0.0 | 664 ms | 0 |
| Tue 04 | 0 | 0.0 | 572 ms | 0 |
| Tue 06 | 0 | 0.0 | 481 ms | 0 |
| Tue 08 | 0 | 0.0 | 599 ms | 0 |
| Tue 10 | 0 | 0.0 | 463 ms | 0 |
| Tue 12 | 0 | 0.0 | 551 ms | 0 |
| Tue 14 | 0 | 0.0 | 618 ms | 0 |
| Tue 17 | 0 | 0.0 | 509 ms | 0 |
| Tue 19 | 0 | 0.0 | 567 ms | 0 |
| Tue 21 | 0 | 0.0 | 642 ms | 0 |
| Tue 23 | 0 | 0.0 | 499 ms | 0 |
| Wed 02 | 0 | 0.0 | 407 ms | 0 |
| Wed 04 | 0 | 0.0 | 532 ms | 0 |
| Wed 06 | 0 | 0.0 | 558 ms | 0 |
| Wed 08 | 0 | 0.0 | 561 ms | 0 |
| Wed 11 | 0 | 0.0 | 677 ms | 0 |
| Wed 13 | 0 | 0.0 | 649 ms | 0 |
| Wed 15 | 0 | 0.0 | 428 ms | 0 |
| Wed 17 | 0 | 0.0 | 464 ms | 0 |
| Wed 19 | 0 | 0.0 | 625 ms | 0 |
| Wed 21 | 0 | 0.0 | 533 ms | 0 |
| Thu 00 | 0 | 0.0 | 458 ms | 0 |
| Thu 02 | 0 | 0.0 | 597 ms | 0 |
| Thu 04 | 0 | 0.0 | 513 ms | 0 |
| Thu 06 | 0 | 0.0 | 510 ms | 0 |
| Thu 08 | 0 | 0.0 | 612 ms | 0 |
| Thu 10 | 0 | 0.0 | 596 ms | 0 |
| Thu 12 | 0 | 0.0 | 620 ms | 0 |
| Thu 14 | 0 | 0.0 | 599 ms | 0 |
| Thu 16 | 0 | 0.0 | 633 ms | 0 |
| Thu 18 | 0 | 0.0 | 583 ms | 0 |
| Thu 20 | 0 | 0.0 | 377 ms | 0 |
| Thu 22 | 0 | 0.0 | 642 ms | 0 |
| Fri 00 | 0 | 0.0 | 527 ms | 0 |
| Fri 02 | 0 | 0.0 | 537 ms | 0 |
| Fri 04 | 0 | 0.0 | 552 ms | 0 |
| Fri 06 | 0 | 0.0 | 474 ms | 0 |
| Fri 08 | 0 | 0.0 | 466 ms | 0 |
| Fri 10 | 0 | 0.0 | 589 ms | 0 |
| Fri 11 | 0 | 0.0 | 589 ms | 0 |
| Fri 13 | 0 | 0.0 | 526 ms | 0 |
| Fri 15 | 0 | 0.0 | 548 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 TimeRex 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 TimeRex yet. Outages of 10 minutes or more get their own page here.
Having trouble with TimeRex?
One report per service every 10 minutes from this network. No account.
Follow TimeRex
Get an email when TimeRex goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TimeRex alerts to Slack, Discord or a webhook — free.
About TimeRex
We track TimeRex (timerex.net) as part of the Cloud & developer group. TimeRex（タイムレックス）は面倒な日程調整を自動化できるツールです。簡単な設定でGoogleカレンダーやOutlook予定表と連携でき、候補日程の抽出や予定の登録を自動化。無料で利用できます。
TimeRex publishes an official status page at status.timerex.net; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 542 ms average, 377–642 ms range across 13 successful checks.
Questions
Is TimeRex down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Outlook予定表をはじめMicrosoft 365において障害が発生しています
When was TimeRex last down?
We have not recorded a public TimeRex incident since monitoring began 8 days ago.
What is TimeRex's uptime?
From our own checks: 100% over 8 days of checks.
How fast does TimeRex respond?
542 ms on average over the last 24 hours (377–642 ms).
Does TimeRex have an official status page?
Yes, at https://status.timerex.net.
TimeRex 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 TimeRex here at once, the problem is on TimeRex'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 TimeRex. 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.