User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is timr Zeiterfassung 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 → timr.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 2 hr ago. Last stored result reached it in 726 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 |
|---|---|---|---|---|
| Tue 23 | 0 | 0.0 | 963 ms | 0 |
| Wed 02 | 0 | 0.0 | 552 ms | 0 |
| Wed 04 | 0 | 0.0 | 610 ms | 0 |
| Wed 06 | 0 | 0.0 | 1072 ms | 0 |
| Wed 08 | 0 | 0.0 | 966 ms | 0 |
| Wed 11 | 0 | 0.0 | 361 ms | 0 |
| Wed 13 | 0 | 0.0 | 582 ms | 0 |
| Wed 15 | 0 | 0.0 | 555 ms | 0 |
| Wed 17 | 0 | 0.0 | 1105 ms | 0 |
| Wed 19 | 0 | 0.0 | 363 ms | 0 |
| Wed 21 | 0 | 0.0 | 1268 ms | 0 |
| Thu 00 | 0 | 0.0 | 512 ms | 0 |
| Thu 02 | 0 | 0.0 | 678 ms | 0 |
| Thu 04 | 0 | 0.0 | 916 ms | 0 |
| Thu 06 | 0 | 0.0 | 1020 ms | 0 |
| Thu 08 | 0 | 0.0 | 969 ms | 0 |
| Thu 10 | 0 | 0.0 | 1264 ms | 0 |
| Thu 12 | 0 | 0.0 | 558 ms | 0 |
| Thu 14 | 0 | 0.0 | 979 ms | 0 |
| Thu 16 | 0 | 0.0 | 508 ms | 0 |
| Thu 18 | 0 | 0.0 | 520 ms | 0 |
| Thu 21 | 0 | 0.0 | 1209 ms | 0 |
| Thu 23 | 0 | 0.0 | 684 ms | 0 |
| Fri 01 | 0 | 0.0 | 686 ms | 0 |
| Fri 03 | 0 | 0.0 | 282 ms | 0 |
| Fri 05 | 0 | 0.0 | 654 ms | 0 |
| Fri 07 | 0 | 0.0 | 1121 ms | 0 |
| Fri 09 | 0 | 0.0 | 1145 ms | 0 |
| Fri 11 | 0 | 0.0 | 1024 ms | 0 |
| Fri 13 | 0 | 0.0 | 1219 ms | 0 |
| Fri 15 | 0 | 0.0 | 901 ms | 0 |
| Fri 17 | 0 | 0.0 | 924 ms | 0 |
| Fri 18 | 0 | 0.0 | 733 ms | 0 |
| Fri 19 | 0 | 0.0 | 3490 ms | 0 |
| Fri 21 | 0 | 0.0 | 1307 ms | 0 |
| Fri 23 | 0 | 0.0 | 795 ms | 0 |
| Sat 01 | 0 | 0.0 | 531 ms | 0 |
| Sat 03 | 0 | 0.0 | 815 ms | 0 |
| Sat 05 | 0 | 0.0 | 484 ms | 0 |
| Sat 07 | 0 | 0.0 | 927 ms | 0 |
| Sat 09 | 0 | 0.0 | 1094 ms | 0 |
| Sat 11 | 0 | 0.0 | 980 ms | 0 |
| Sat 14 | 0 | 0.0 | 636 ms | 0 |
| Sat 16 | 0 | 0.0 | 1224 ms | 0 |
| Sat 18 | 0 | 0.0 | 509 ms | 0 |
| Sat 21 | 0 | 0.0 | 541 ms | 0 |
| Sat 23 | 0 | 0.0 | 659 ms | 0 |
| Sun 01 | 0 | 0.0 | 726 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 10 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live timr Zeiterfassung 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 timr Zeiterfassung yet. Outages of 10 minutes or more get their own page here.
Having trouble with timr Zeiterfassung?
One report per service every 10 minutes from this network. No account.
Follow timr Zeiterfassung
Get an email when timr Zeiterfassung 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 timr Zeiterfassung
timr Zeiterfassung is listed in our Cloud & developer category and checked at timr.com. Rechtsichere & einfache digitale Zeiterfassung für Mitarbeiter ✓ Arbeitszeiten, Projekte & Abwesenheiten ✓ Web, App & Terminal ➤ Jetzt kostenlos testen
timr Zeiterfassung publishes an official status page at status.timr.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 793 ms average, 471–1300 ms range across 12 successful checks.
Questions
Is timr Zeiterfassung down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was timr Zeiterfassung last down?
We have not recorded a public timr Zeiterfassung incident since monitoring began 10 days ago.
What is timr Zeiterfassung's uptime?
From our own checks: 100% over 10 days of checks.
How fast does timr Zeiterfassung respond?
793 ms on average over the last 24 hours (471–1300 ms).
Does timr Zeiterfassung have an official status page?
Yes, at https://status.timr.com.
timr Zeiterfassung 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 timr Zeiterfassung here at once, the problem is on timr Zeiterfassung'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 timr Zeiterfassung. 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.