Rossum Outage History

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

Every Recorded Rossum Incident

Rossum incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Some services are beeing interruptedThe issue was identified and fixed. All should work as normal. The impact on customers should be minimal. (Failed jobs were re-tried)12 minResolved
Oct 12, 2026API slow-downThis incident has been resolved.9h 10mResolved
Oct 7, 2026Application slow-downThe issue was mitigated. We are working on a long-term solution for this.56 minResolved
Sep 26, 2026Database maitenance - RIRThe scheduled maintenance has been completed.10 minScheduled
Aug 6, 2026Application slowdownThis incident has been resolved.44 minResolved
Aug 4, 2026Application slowdownThis incident has been resolved.27 minResolved
Aug 1, 2026Database maitenanceThe scheduled maintenance has been completed.5 minScheduled
Jul 17, 2026Application slowdownThis incident has been resolved.1h 48mResolved
Jul 8, 2026Application slowdownThis incident has been resolved.1h 32mResolved
Jul 5, 2026Network updateThe scheduled maintenance has been completed.1h 0mScheduled
Jun 14, 2026Network updateThe scheduled maintenance has been completed.30 minScheduled
Jun 10, 2026System outageThis incident has been resolved.19h 22mResolved
Jun 4, 2026System outageThis incident has been resolved.18 minResolved
Jun 3, 2026prod-us2 partial outageServices on the prod-us2 cluster were partially unavailable due to a failure during infrastructure migration.-6850 minResolved
Jun 3, 2026Application slowdownThis incident has been resolved.1h 8mResolved
May 30, 2026Network updateThe scheduled maintenance has been completed.30 minScheduled
May 23, 2026Network updateThe scheduled maintenance has been completed.30 minScheduled
Apr 24, 2026Aurora CLI is unavailblefeature restored.42 minResolved
Apr 20, 2026Component outageThis incident has been resolved.22h 38mResolved
Apr 9, 2026System outageThis incident has been resolved.16h 43mResolved
Apr 7, 2026System outageThis incident has been resolved.6 minResolved
Apr 3, 2026Application slowdown & intermittent unavailabilityThis incident has been resolved.8h 7mResolved
Apr 3, 2026Application slowdownThis incident has been resolved.17 minResolved
Apr 3, 2026Database upgradeThe scheduled maintenance has been completed.15 minScheduled
Apr 2, 2026System outageThis incident has been resolved.3h 26mResolved
Mar 31, 2026Application slowdownThis incident has been resolved.50 minResolved
Mar 30, 2026System outageThis incident has been resolved.10 minResolved
Mar 3, 2026Application slowdownA period of high traffic caused minor overload. Response times were longer than expected.-7186 minResolved
Mar 2, 2026Application SlowdownThis incident has been resolved.2h 29mResolved
Feb 27, 2026Application slowdown (inftrastructure overload)This incident has been resolved.17 minResolved
Feb 27, 2026Infrastructure overloaded - Service partially unavailableInfrastructure overloaded causing the service being partially unavailable.5 minResolved
Feb 12, 2026Application slowdownThis incident has been resolved.39 minResolved
Feb 10, 2026Mastar Data Hub errorsThis incident has been resolved.59 minResolved
Feb 9, 2026Webhooks outageThis incident has been resolved.53 minResolved
Feb 3, 2026Application slowdownThis incident has been resolved.1h 8mResolved
Jan 30, 2026Application slowdownThis incident has been resolved.40 minResolved
Jan 28, 2026Application slowdownThe situation has been resolved.2h 6mResolved
Jan 10, 2026Database upgradeThe scheduled maintenance has been completed.15 minScheduled
Nov 16, 2025Database maintenanceThe scheduled maintenance has been completed.30 minScheduled

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 Rossum 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 Rossum 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 Rossum 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 Rossum outage in this window ran 22h 38m, against a mean recovery of 2h 45m. If you depend on Rossum 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.