Rejoiner, Inc. Outage History

14 incidents recorded over the last 365 days, 4 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.

Live Rejoiner, Inc. status100.00% uptime history

Every Recorded Rejoiner, Inc. Incident

Rejoiner, Inc. incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jun 24, 2026scheduled maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Apr 24, 2026scheduled maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Mar 10, 2026unscheduled outageThe incident has been resolved.6h 58mResolved
Mar 6, 2026scheduled maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Mar 4, 2026scheduled maintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Feb 11, 2026scheduled maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Feb 10, 2026unexpected service disruptionthe incident has been resolved and systems are operating normally25h 29mResolved
Feb 9, 2026degraded servicesAll services have been restored.2h 43mResolved
Feb 6, 2026scheduled maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Feb 4, 2026scheduled maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Jan 24, 2026scheduled maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Jan 23, 2026unexpected service disruptionWe have identified and resolved the issue and services are operating normally.1h 5mResolved
Jan 23, 2026scheduled maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Jan 5, 2026scheduled maintenanceThe scheduled maintenance has been completed.3h 0mScheduled

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 Rejoiner, Inc. 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 Rejoiner, Inc. 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 Rejoiner, Inc. 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 Rejoiner, Inc. outage in this window ran 1d 1h, against a mean recovery of 4h 40m. If you depend on Rejoiner, Inc. 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.