
checked Nov 4, 2026 9:07 AM UTC · TimeRex's official status page
Is TimeRex Having an Outage?
No. TimeRex is up and running.
TimeRex is currently operational with all systems functioning normally.
All components operational
- Last broke
- Oct 22
- Uptime
- 99.85%
- Most impacted
- TimeRex Website
History · 30 day period
Service health
Service health, last 30 days
How to read this
The record
30 day period · not affected by the range aboveAvailability counts operational or degraded time as available, averaged equally across all monitored components. Partial outages count as half downtime and major outages count in full, scheduled maintenance is excluded from the calculation, and periods with no recorded status are counted as available rather than assumed down. Each component is tracked independently to give you a clear picture of overall service reliability.
Get updates without checking back
Get email updates for the reported TimeRex status changes you choose. Follow your other dependencies in the same workspace.
30-day free trial, no card needed. First-time customers; continued monitoring requires a paid subscription.
Recent TimeRex outages & status updates
Status changes and service events for TimeRex over the last 30 days
| S | M | T | W | T | F | S | |
|---|---|---|---|---|---|---|---|
| Oct 4 | |||||||
| Oct 11 | |||||||
| Oct 18 | 1 | 1 | |||||
| Oct 25 | |||||||
| Nov 1 |
External Services experienced degraded performance
Oct 22 · resolved after 1h 4m
TimeRex Website experienced a major outage
Oct 21 · resolved after 10h 42m
PHPの脆弱性対応に伴う緊急メンテナンス実施およびサービス一時停止のお知らせ
Oct 21 · reported by TimeRex · resolved
Scheduled maintenance on External Services
Oct 12 · resolved after 3h 8m
TimeRex component status
Check current status by component. Open one for regions, incident details, and alerts.
2 components tracked
Incidents · 30dStatusWhat is TimeRex?
More Other services
Frequently asked questions about TimeRex
Common questions about monitoring TimeRex and understanding service status
Is TimeRex down right now?
TimeRex's status source currently reports Operational. Last checked Nov 4, 2026 9:07 AM UTC. Statusfield tracks 2 components. A reported operational state does not rule out a local problem or an incident the provider has not yet reported.
How do I get notified when TimeRex goes down?
Create a Statusfield account, select the TimeRex components you depend on, and configure notification channels and status filters. Alerts follow detected changes that match your monitoring settings. Available channels and limits depend on your plan; delivery timing also depends on the source update and successful checks.
Why monitor TimeRex alongside my other vendors?
Statusfield brings TimeRex's reported component status together with your other vendors in one dashboard. You can choose the components you depend on and configure notification channels and status filters. The available channels and limits depend on your plan. Vendor status pages differ in their own subscription options.
What do TimeRex status levels mean?
TimeRex status levels indicate service health: Operational (all systems working normally), Degraded Performance (reduced functionality), Partial Outage (some components affected), Major Outage (significant service disruption), and Under Maintenance (scheduled maintenance). Statusfield tracks these statuses across 2 components to provide granular monitoring.
What should I do when TimeRex is down?
When TimeRex is down: 1) Check the affected components and any available incident updates, 2) Review your application's TimeRex integration for fallback mechanisms, 3) Check the provider's support channels for recovery information, 4) Configure Statusfield alerts for detected status changes. Recovery times depend on the incident; Statusfield does not predict when the provider will restore service.
Has TimeRex been down today?
The status timeline above is the record: it shows every incident, outage and maintenance window Statusfield has seen for TimeRex over the last 30 days, with the times each began and ended. TimeRex is not reporting a disruption right now; check the timeline for anything earlier today.
Why is TimeRex not working for me?
If TimeRex isn't working: 1) Check Statusfield to confirm if there's a service-wide outage, 2) Verify your internet connection, 3) Clear your browser cache and cookies, 4) Try accessing TimeRex from a different network or device, 5) Check TimeRex's official status page for regional issues. If TimeRex shows operational but you're still experiencing issues, the problem may be local to your account or network.
Is TimeRex down for everyone or just me?
Statusfield displays the status reported for 2 TimeRex components. Compare the affected components with your own errors and the provider's latest updates. An operational status does not rule out a regional, account-specific, or unreported problem.
How can I reduce alert fatigue from TimeRex status emails?
Use Statusfield to consolidate your dependencies into one dashboard. Choose which TimeRex components to monitor, select the notification channels included in your plan, and configure status filters so routine updates do not go to the same destination as major outages.
How do I set up TimeRex monitoring in 3 steps?
1) Create a Statusfield account — eligible new accounts can choose a free trial, no card required. 2) Search for "TimeRex" in the service catalog and click "Monitor" to add it to your dashboard. 3) Configure the notification channels included in your plan and choose which severities should trigger alerts.
What notification channels does Statusfield support for TimeRex alerts?
Route TimeRex status changes to email, Slack, Microsoft Teams, PagerDuty, Discord or HTTP webhooks, depending on your plan. Choose the supported components and events that matter to your team, then test the destination and confirm your routing rules. Delivery depends on detected changes, source availability and the destination.

TimeRex isn't the only vendor you depend on — and an outage at any of them looks the same to your customers.
Get alerted when any vendor in your stack has an incident
Free, no signup. Public DNS signals only.