OfficeRnD Outage History
8 incidents recorded over the last 365 days, 8 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 OfficeRnD Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 23, 2026 | APIv2 downtime in Singapore and Australia regionsBetween October 22 and October 23, we experienced an incident that caused our APIv2 service to be temporarily unavailable for customers hosted in our Singapore and Australia regions. This interruption was strictly… | -1417 min | Resolved |
| Oct 23, 2026 | APIv2 downtime in Singapore and Australia regionsBetween October 22 and October 23, we experienced an incident that caused our APIv2 service to be temporarily unavailable for customers hosted in our Singapore and Australia regions. This interruption was strictly… | -1248 min | Resolved |
| Jun 23, 2026 | Partial Outage of Email Activity LogThis incident has been resolved. | 1h 22m | Resolved |
| May 18, 2026 | Partial Outage for DataHubDataHub report fails to load without proper initialization | -164 min | Resolved |
| Jan 6, 2026 | We are seeing performance degradation in the systemThe system is currently experiencing a degradation in performance, resulting in slower response times | -7441 min | Resolved |
| Dec 10, 2025 | Degraded PerformanceWe've experienced Degraded performance in our Flex product (Admin Portal and Members Portal) for four (4) minutes in total. We are investigating! | 0 min | Resolved |
| Nov 18, 2025 | CouldFlare incidentCloudflare has confirmed the issue is resolved, and custom domains are now functioning normally again. | 7h 23m | Resolved |
| Nov 14, 2025 | Flex Admin portal DowntimeWe identified a platform outage that lasted approximately two minutes, affecting mainly the Flex Admin portal. The platform's performance recovered fully within 20 minutes. | -3067 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 OfficeRnD 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 OfficeRnD 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 OfficeRnD 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 OfficeRnD outage in this window ran 7h 23m, against a mean recovery of 2h 55m. If you depend on OfficeRnD 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.