Questions, answered

Teams whose services run on someone else’s infrastructure and who explain their providers’ incidents to their own customers: hosting companies, network operators and SaaS teams. It’s a status page with monitoring that reads your providers’ notices for you.

Yes. The status page, monitoring and notifications work wherever your servers are. Provider notices are matched for OVHcloud and Hetzner; tell us which provider you’d like next.

No. Matched notices arrive in your admin and stay off your status page; nobody is notified. To tell your customers, you post your own update.

Every hour. We relay what your providers publish; if a provider doesn’t publish an outage, we can’t see it. Your own monitors cover those.

No. Hetzner publishes its notices per datacenter building, such as FSN1-DC14, so that’s how precisely we match them. OVHcloud notices are matched down to the rack or room.

OVHcloud (19 sites) and Hetzner (6 sites): 25 locations. The full list, with how precisely each provider is matched, is on the Providers page.

No. Provider notices come from the datacenter and cloud providers you rent from, not from transit carriers. To watch your own links, run probe agents inside your network.

Your status page doesn’t run on your servers. It runs on Cloudflare’s network, apart from your servers at OVHcloud or Hetzner. So Cloudflare is a dependency you share with us: if Cloudflare has an outage, Upstreamr can be affected too.

Upstreamr can be affected: your status page and the checks from the Cloudflare edge both run on Cloudflare’s network. If your own product also runs on Cloudflare, your status page is not independent of it. Cloudflare publishes its own status at cloudflarestatus.com. Your admin runs there too, so you may not be able to post an update until it’s back.

We’ll link Upstreamr’s own status page here once it’s live.

Yes: 1 status page on a free subdomain, 10 monitors checked every 3 minutes, 100 email subscribers, 2,000 notification emails a month, 1 provider location and 2 members, with a “Powered by Upstreamr” badge. No card needed. The paid plan starts at €9 a month excl. VAT. Paid plans go on sale at the public launch on 17 November.

The paid plan is €9 a month excl. VAT and includes 1 page, 20 monitors, 1 probe agent, 1,000 subscribers, 10,000 notification emails, 3 provider locations and 5 members. Above that, each item is billed on its highest count during the month; notification emails on the month’s total. Example: 40 monitors, 2,500 subscribers and 4 provider locations cost €22 a month (€9 + €4 + €6 + €3).

Yes. Billed yearly, the paid plan is €91.80 a year excl. VAT instead of €9 a month: 15% off. Usage above the included amounts is 15% off too, and it’s still billed monthly. A yearly plan keeps its prices for the term you’ve paid for. Paid plans, monthly or yearly, go on sale at the public launch on 17 November.

Email pauses; nothing else does. On the free plan, after 2,000 notification emails in a month, updates aren’t emailed to subscribers until the next month. On the paid plan, 10,000 a month are included, then €0.50 per 1,000. Email pauses only if sending an update would take your estimate past your spend limit, and resumes with the next update once you raise or remove the limit. Your status page, webhooks, RSS/Atom feeds and Discord and Slack channels (paid plan) keep updating, and your organization’s owners get one email saying so.

Yes. Set a monthly spend limit; changes that would take your estimate above it are blocked. Safety caps also stop a mistake from running up a bill.

Not by itself. We never raise the price of your subscription automatically, at renewal or at any other time. If we raise a price you pay, we tell you at least 60 days before it applies, and a yearly plan keeps its price until its next renewal. The policy is on the Price changes page under Legal; it’s a draft pending legal review.

Free pages show a small “Powered by Upstreamr” badge. On the paid plan, white-label removes it for €29 a month.

Upstreamr runs on Cloudflare. The Privacy Policy and the Data Processing Agreement list who processes your data and your subscribers’ data, and why.

On the paid plan your page runs on your own domain, so the address your customers know is yours. There’s also a public read API and a management API with scoped keys, documented in OpenAPI 3.1.