Rublon Outage History

12 incidents recorded over the last 365 days, 12 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 Rublon status100.00% uptime history

Every Recorded Rublon Incident

Rublon incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 2, 2026Rublon Support Portal is degraded71h 12mResolved
Oct 20, 2026Rublon Support Portal is degraded388h 57mResolved
Sep 28, 2026Email Delivery (Global) is degraded903h 36mResolved
Sep 24, 2026Rublon Websockets is degraded992h 23mResolved
Sep 1, 2026Rublon Support Portal is degraded1554h 30mResolved
Aug 14, 2026Email Delivery (Global) is degraded1875h 22mResolved
Aug 11, 2026Rublon Support Portal is degraded1959h 10mResolved
Aug 6, 2026Rublon Website is degraded2067h 38mResolved
Aug 3, 2026Rublon Support Portal is degraded2147h 46mResolved
Jul 29, 2026Rublon Website is degraded1513h 50mResolved
Jun 28, 2026Rublon Website is down1548h 34mResolved
Jun 4, 2026Email Delivery (Global) is down2113h 16mResolved

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 Rublon 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 Rublon 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 Rublon 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 Rublon outage in this window ran 89d 11h, against a mean recovery of 59d 12h. If you depend on Rublon 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.