Your provider's outage shouldn't wake your on-call.
Most monitors page you the moment your site looks down — even when the real cause is your host, CDN, or payments provider having a bad day. Merlonix knows the difference between your outage and theirs, and holds the page when it's not yours to fix.
How it works
01
Tag what each site depends on
On every asset you monitor, note the providers it relies on — its host, CDN, payments, DNS. It takes seconds and it’s the only setup vendor-aware alerting needs.
02
We watch the providers, continuously
Merlonix polls the official status pages of 11 major providers around the clock and records when any of them enters a degraded, partial, or major outage.
03
When it’s theirs, we hold the page
If a site’s check fails while one of its tagged providers is in a live incident, we don’t page your on-call. The alert is still created and shown in your dashboard — attributed to the provider and its status — so you have the full picture without the false fire drill.
Providers we watch
11 major providers, watched around the clock.
Tag a site with the ones it depends on and we correlate every failure against their live incident state.
For agencies
One Cloudflare incident shouldn't trigger 40 client pages.
If you run 40 client sites on shared infrastructure, a single upstream incident normally means 40 alerts and 40 awkward “is it us?” client emails. Merlonix correlates every affected site to the one provider incident and holds the pages — so you get a single, accurate story to tell the client: “This was Cloudflare; your site was never misconfigured.” The individual alerts still sit in your dashboard if you want the detail.
Common questions
Does this hide outages from me?
No. Nothing is hidden. When a failure is correlated to a provider incident, the alert is still created and visible in your dashboard — it is just attributed to the provider and does not page your on-call. You see everything; you simply stop getting woken up for outages you cannot fix.
Which providers does Merlonix watch?
Today Merlonix monitors the official status pages of 11 major providers: AWS, Cloudflare, Google Cloud, Azure, Vercel, GitHub, Shopify, Stripe, Slack, OpenAI, and Anthropic. You tag each monitored site with the ones it depends on, and suppression only applies to those providers.
What about planned maintenance?
Planned maintenance does not suppress the page. A maintenance window you were not expecting can still take a site down, so it is still worth telling you about — only live degraded/partial/major incidents hold the page.
What if a site depends on several providers at once?
If more than one of a site’s tagged providers is having an incident at the same time, Merlonix attributes the suppression to the most severe one, so the alert tells you the worst thing happening upstream.
How do I turn it on?
Start a free 14-day trial, add the sites you monitor, and tag each one with the providers it relies on. Vendor-aware alerting is built in — there is nothing extra to configure beyond the dependency tags.