Repurpose.io Inc. Uptime History

Measured by PulsAPI's own checks, not reported by Repurpose.io Inc.. Every figure below is computed over the 90 days in the last 365 that PulsAPI actually observed, from 2026-08-08 to 2026-11-05. Days nobody watched are left out rather than counted as perfect.

Repurpose.io Inc. Uptime at a Glance

Measured uptime
85.25%

across 90 observed days

Days with an issue
33

days were not fully operational

Longest outage
91d 18h

single longest resolved incident

Mean recovery
51d 21h

average time to resolve

Monthly Repurpose.io Inc. Uptime

Each month is the mean of its observed days. The strongest month was November 2026 at 100.00%, the weakest August 2026 at 66.43%. Months with few observed days are marked, because a short month is not evidence of a good one.

Monthly uptime, newest first, with the number of days observed in each month.
MonthUptimeUptime barDays observed
November 2026100.00%5partial
October 202695.59%31
September 202687.17%30
August 202666.43%24

Get an email when Repurpose.io Inc. moves

Every figure on this page came from a check we ran. Those same checks can reach your inbox the moment Repurpose.io Inc. stops being operational, so the next dip arrives as a notification rather than a row you find later.

Free, no password, no card. Unsubscribe in one click.

How This Repurpose.io Inc. Uptime Figure Is Measured

PulsAPI checks Repurpose.io Inc. continuously (every 60 seconds) and records the result. A day's uptime is the share of that day's checks that came back fully operational, so a 20-minute outage shows up as a dip rather than being rounded away. The window figure is the mean of those daily values.

Two things this deliberately is not. It is not Repurpose.io Inc.'s own published uptime, because vendors generally measure against their own SLA definitions, which usually exclude scheduled maintenance and often exclude partial degradation. And it is not a promise about the future: 90 days of history describes what happened, and the useful way to read it is alongside the incidents behind the dips.

Uptime measured this way is a mean of component uptimes where a vendor publishes components, so coverage matters as much as the percentage. That is why the observed-day count sits beside every figure on this page rather than in a footnote.

These measurements are published under CC BY 4.0. Quote or republish them freely, with attribution to PulsAPI.