TimeRex Outage History
2 incidents recorded over the last 365 days, 2 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded TimeRex Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | PHPの脆弱性対応に伴う緊急メンテナンス実施およびサービス一時停止のお知らせ緊急メンテナンスが終了し、すべての機能をご利用いただける状態になりました。 | 10h 22m | Resolved |
| Apr 1, 2026 | ダッシュボード内の一部表示の乱れ、日程調整完了メール・キャンセルメール・日程変更メール・リマインドメールが送信されないケースがあるなどの不具合が発生しておりました。ダッシュボード内の一部表示の乱れ、日程調整完了メール・キャンセルメール・日程変更メール・リマインドメールが送信されないケースがあるなどの不具合が発生しておりました。 現在は復旧し、通常通りにご利用いただける状況です。 | 0 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next TimeRex incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This TimeRex Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before TimeRex acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single TimeRex outage in this window ran 10h 22m, against a mean recovery of 5h 11m. If you depend on TimeRex in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.