●Incident

Varsom (Avalanches) outage.

ResolvedDEGRADATION · HIGH

Oct 28, 2026, 04:44 AM · 6 days ago · Duration: 23min

Detected by Probecast

Incident Summary

API Varsom (Avalanches) is currently DOWN in us-east.

Diagnostic Details

Error Type: network HTTP Status: N/A Error Message: fetch failed Retry Attempts: 3 (all failed)

Validation Results

Validation Reason: All 3 retry attempts failed Consecutive DOWN Checks: 2 Time Between Checks: 308s

Cross-Region Impact

Also DOWN in: asia, europe, us-west Total Affected Regions: 4

Severity Assessment

Level: HIGH Multiple regions affected or critical error type detected.

Detected by Probecast Health Monitor - 2026-10-28T04:44:42.709Z

Timeline

●Started

Oct 28, 2026, 04:44 AM

6 days ago

●Resolved

Oct 28, 2026, 05:07 AM

6 days ago

●Duration

23min

Total downtime

Evidence Logs5 checks

Time	Region	Status	Latency	Code
Oct 28, 04:44 AM	us-east	down	2480ms	—
Oct 28, 04:44 AM	asia	down	2479ms	—
Oct 28, 04:43 AM	us-west	down	2480ms	—

For the projects you ship

How many of your clients depend on Varsom (Avalanches)?

When Varsom (Avalanches) slows down, every project that depends on it feels it at once — and the first call goes to whoever shipped it. Probecast watches the sites you ship and the providers underneath them, shows which clients an outage touches and turns each month into a report your client can trust.

One provider breaks. See every client it touches.

Ordered by how many clients it hits, so you message the right people first.

Each client's site and store, checked from up to four regions.

US West & East, Europe and Asia — a regional outage never hides.

A monthly report under your brand, reviewed by your team before it goes out.

Uptime, incidents, traffic, revenue and support — signed off by a person.

Your team scoped per client. Every change on the record.

Freelancers see only their clients; every change lands in an append-only audit log.

Start free Book 15 minutes →View Varsom (Avalanches) full status →

Alerts land on email, Slack, push or webhooks — with the client's name on them.