OTOY Outage History
3 incidents recorded over the last 365 days. 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 OTOY Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 12, 2026 | OTOY Forums Scheduled MaintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Apr 27, 2026 | Static IP change for OTOY SSOThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 26, 2026 | Scheduled maintenance on OTOY SSOThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
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 OTOY 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 OTOY 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 OTOY 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 OTOY outage in this window ran 4h, against a mean recovery of 1h 50m. If you depend on OTOY 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.