Reputation.com Outage History

12 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.

Live Reputation.com status100.00% uptime history

Every Recorded Reputation.com Incident

Reputation.com incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 20262026-10-28 Scheduled MaintenanceScheduled maintenance is currently in progress. We will provide updates as necessary.4h 0mScheduled
Sep 24, 20262026-09-23 Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Aug 27, 20262026-08-26 Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jul 23, 20262026-07-22 Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jun 25, 20262026-06-24 Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
May 21, 20262025-05-20 Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Apr 23, 20262026-04-22 Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Mar 26, 20262026-03-25 Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Mar 7, 2026Scheduled Infrastructure Maintenance NoticeThe scheduled maintenance has been completed.12h 0mScheduled
Feb 26, 20262026-02-25 Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jan 22, 20262026-01-21 Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Dec 12, 20252025-12-11 Scheduled MaintenanceThe scheduled maintenance has been completed.4h 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 Reputation.com 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 Reputation.com 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 Reputation.com 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 Reputation.com outage in this window ran 12h, against a mean recovery of 4h 40m. If you depend on Reputation.com 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.